blink-connectors

name: blink-connectors description: OAuth connector system for 38+ third-party services. Execute API calls to Google, Notion, Slack, Discord, GitHub, Stripe, Jira, HubSpot, Salesforce, LinkedIn, and more.

Getting Started

# List available providers
blink connector providers

# Check connection status
blink connector status slack

# Execute an API call
blink connector exec slack /conversations GET

MCP Tools

Prerequisites

Initial OAuth connection must be done in the browser at blink.new/settings?tab=connectors. Users authorize each provider once, then CLI/MCP/SDK can make API calls.

SDK Usage

// Check status
const status = await blink.connectors.status('slack')

// GET request
const channels = await blink.connectors.execute('slack', {
  method: '/conversations',
  http_method: 'GET',
  params: { types: 'public_channel,private_channel' }
})

// POST request
await blink.connectors.execute('slack', {
  method: '/chat/postMessage',
  http_method: 'POST',
  params: { channel: 'C1234', text: 'Hello from Blink!' }
})

Available Providers

Plus 20+ more — run blink connector providers for the full list.

CLI Examples

# Slack: list channels
blink connector exec slack /conversations GET

# Notion: search pages
blink connector exec notion /search POST '{"query":"meeting notes"}'

# Google Sheets: read data
blink connector exec google_sheets "/spreadsheets/SHEET_ID/values/Sheet1!A1:D10" GET

# HubSpot: list contacts
blink connector exec hubspot /contacts GET '{"limit":50}'

# Salesforce: SOQL query
blink connector exec salesforce /query GET '{"q":"SELECT Id,Name FROM Account LIMIT 10"}'

CLI syntax: blink connector exec <provider> <endpoint> [method] [params]

Method Path Rules

1. Paths start with / — /conversations not conversations
2. Dynamic IDs go in the path — /channels/${channelId}/messages
3. Provider IDs use underscores — google_drive, google_calendar, google_sheets
4. GET params become query parameters; POST params become JSON body
5. Invalid JSON in CLI params hard-fails (exit 1) — bad JSON used to silently send {}. If you see Invalid JSON for params: ..., fix the quoting (shell-escape inner double quotes or use --input @file.json).

Google Ads (composio_googleads) — known upstream bug

Composio's server strips false, 0, {}, [] from POST bodies before forwarding to Google Ads. This breaks any call that requires explicit booleans, empty proto messages, or 0 enum values. Tracked at ComposioHQ/composio#3324. Until fixed upstream, follow these patterns:

Required workarounds

1. Always set partialFailure: true and validateOnly: true first. This converts 400 errors into 200-OK responses with a partialFailureError field that ISN'T truncated by Composio's error wrapper — you'll see Google's full fieldPathElements and learn which fields were stripped. Switch to validateOnly: false only after the dry-run succeeds.

2. Use portfolio bidding strategies, not inline {} markers.

   • ❌ { campaign: { manualCpc: {} } } — {} is stripped, Google returns REQUIRED.
   • ✅ Create a portfolio first via biddingStrategies:mutate with type: "TARGET_SPEND", then reference the resource name as a string: { campaign: { biddingStrategy: "customers/123/biddingStrategies/456" } }. Strings are never stripped.

3. Place finalUrls at the Asset top level, NOT inside sitelinkAsset. Composio's schema validation drops it from inside the sub-object. Top-level survives.

4. Include all v23 required enum fields explicitly:

   • containsEuPoliticalAdvertising: 2 (NOT_EU_POLITICAL_ADVERTISING) — newly required.
   • networkSettings.targetGoogleSearch, targetSearchNetwork, targetContentNetwork, targetPartnerSearchNetwork — set to true for Search campaigns. NEVER pass false — Composio strips it. If you need to exclude a network, omit the field (Google defaults to your account preferences).

Debugging recipe

When a Google Ads call fails with cryptic REQUIRED errors:

# 1. Add partialFailure + validateOnly to dry-run with full errors
blink connector exec composio_googleads /v23/customers/CUSTOMER_ID/campaigns:mutate POST \
  '{"operations":[...],"partialFailure":true,"validateOnly":true}'

# 2. Read the partialFailureError.details for fieldPathElements
# 3. Replace any { manualCpc: {} } with portfolio bidding string references
# 4. Re-run with validateOnly: false

Error Codes

Token refresh is handled automatically by Blink backend.