Connectors

Connectors are pre-built integrations that let your workflows send messages, notifications, and data to external services without writing integration code.

Available Connectors

Messaging

Google Suite (OAuth, one-click setup)

Google connectors use one-click OAuth: just click "Connect Google Account" and authorize. No API keys needed. Your workflows reference connectors by name, and the platform handles authentication, token refresh, and API protocol details automatically.

Email

Productivity

Data & Operations

Setting Up a Connector

1. Go to Integrations in the sidebar
2. Click the Connectors tab
3. Find the connector you want in the Available Connectors grid
4. Click Add Connector on the card
5. In the install panel, click "How to get these credentials" to see step-by-step instructions
6. Fill in the required configuration fields
7. Click Test to verify the connection works
8. Click Install Connector

Getting Credentials (Per-Connector Guides)

Each connector requires different credentials. Here's where to find them:

Slack Webhook

1. Go to api.slack.com/apps and sign in
2. Click Create New App > From scratch, name it, and pick your workspace
3. In the left sidebar, click Incoming Webhooks and toggle it ON
4. Scroll down and click Add New Webhook to Workspace
5. Choose the channel to post to and click Allow
6. Copy the Webhook URL (starts with https://hooks.slack.com/services/...)

Discord Webhook

1. Open Discord and go to the channel you want to post to
2. Click the gear icon (Edit Channel) next to the channel name
3. Go to Integrations > Webhooks
4. Click New Webhook, give it a name, then click Copy Webhook URL

Telegram Bot

1. Open Telegram and search for @BotFather
2. Send /newbot and follow the prompts to name your bot
3. BotFather will reply with a bot token — copy it
4. To get a Chat ID: add your bot to a group, send a message, then visit api.telegram.org/bot<YOUR_TOKEN>/getUpdates
5. Find the chat > id value in the response — this is your Chat ID

SendGrid Email

1. Sign up or log in at app.sendgrid.com
2. Go to Settings > API Keys > Create API Key
3. Choose Restricted Access, enable Mail Send permissions, and create
4. Copy the API key (starts with SG.) — you won't see it again
5. Go to Settings > Sender Authentication and verify your sender email

Resend Email

1. Sign up or log in at resend.com
2. Go to API Keys in the sidebar and click Create API Key
3. Copy the key (starts with re_) — you won't see it again
4. Go to Domains and add + verify your sending domain

GitHub Issues

1. Go to github.com/settings/tokens and click Generate new token
2. For classic tokens: select the repo scope. For fine-grained tokens: select the repository and enable Issues: Write
3. Copy the token (starts with ghp_ or github_pat_)

Linear Issue

1. Go to linear.app/settings/api and click Create key
2. Copy the API key (starts with lin_api_)
3. To find your Team ID: go to your team settings page — the UUID is in the URL

Notion Page

1. Go to notion.so/my-integrations and click New integration
2. Name it, select the workspace, and click Submit
3. Copy the Internal Integration Token (starts with ntn_)
4. Open the Notion database you want to use, click ... > Add connections and add your integration
5. Copy the Database ID from the URL: notion.so/<workspace>/<DATABASE_ID>?v=...

Supabase Insert

1. Log in to app.supabase.com and open your project
2. Go to Settings > API in the sidebar
3. Copy the Project URL (e.g. https://xxxx.supabase.co)
4. Under Project API keys, copy the service_role key (bypasses RLS — keep it secret)

PagerDuty Incident

1. Log in to your PagerDuty account
2. Go to Services > Service Directory and select (or create) a service
3. Click the Integrations tab > Add Integration
4. Select Events API v2 and click Add
5. Copy the Integration Key (also called Routing Key)

Generic Webhook

No specific credentials required — just your target URL and any authentication tokens your API needs.

Custom Headers (Generic Webhook)

The Generic Webhook connector supports custom HTTP headers via a key-value editor:

• Click + Add to add a header row
• Enter the header name and value
• Click the circle icon to toggle sensitive masking (hides the value)
• Custom headers are merged into the request alongside the Authorization header

This is useful for APIs that require custom headers like X-API-Key, X-Webhook-Signature, or vendor-specific headers.

Using Connectors in Workflows

Once configured, reference connectors in your workflow markdown:

### 4. Notify team on Slack
Send the analysis summary from step 3 to the #engineering channel
using the Slack connector.

The AI compiler sees your installed connectors (including their API schemas) and generates the correct HTTP request configuration automatically. You don't need to specify URLs, headers, or body formats.

How AI Uses Connector Schemas

When you compile a workflow, the AI sees:

• The connector's HTTP method and URL pattern
• Required headers (authentication, content type)
• Body template with placeholder fields
• Runtime input descriptions (what each field means and expects)

This means the AI generates correct API calls matching the connector's schema, instead of guessing.

Connectors vs. MCP Servers

Rule of thumb: Use connectors for simple "send a message" actions. Use MCP servers when you need bidirectional communication or complex tool interactions.

Testing Connectors

Each connector has a Test button that sends a sample request to verify your configuration. Test before using in a workflow to catch issues early (wrong webhook URL, expired API key, etc.).

Self-Healing Connector Steps

When a connector step fails at runtime (e.g., malformed datetime for Google Calendar, missing spreadsheet ID for Sheets), CFFBRW's AI recovery automatically diagnoses the issue. The recovery AI sees the connector's expected parameters, your workflow input values, and exactly what request was sent, so it can fix the problem and retry the API call without recompiling.

You'll see a blue "Adapted" badge on steps that were recovered. No action needed on your part.

Important: Recompile After Changes

When you install, update, or remove a connector, recompile any workflows that use it. The compiled plan caches the connector configuration at compile time. Changing a connector doesn't automatically update existing plans.