Developers

Connections

Send form submissions to Discord, email, Zapier, and more — automatically, every time someone submits.

What are connections

A connection sends every new submission on one form to a third-party service — post to Discord, forward to Zapier, notify an inbox by email, or hand off to a webhook you control. Connections are configured per form, from that form's Connections tab in your dashboard, and are gated behind the Connections module (bundled into Modular and Ultimate).

A connection only fires for real submissions accepted after honeypot and validation checks pass. It never sees a spam-flagged or rejected submission.

Available connectors

The catalog covers 29 services across six categories, and every one of them is live: plain URL, customer-supplied API key, or a real OAuth Connect button that hands off to the provider's own consent screen and stores a token, never a manually-typed secret.

"Available (OAuth)" means the connector's Connect button only works once the embedio operator has registered a platform-level OAuth app for that service and entered its Client ID/Secret in the admin Extensions page — until then it shows as needing setup rather than a broken redirect.

Connectors in the CRM, Newsletters, and Support categories are premium: they additionally require the Ultimate plan, on top of the Connections module being enabled.

The 10 API-key connectors added in this batch (Telegram, Airtable, Trello, ActiveCampaign, Pipedrive, ConvertKit, Klaviyo, MailerLite, Freshdesk, Gladly) each take your own API key or token for that service, entered directly in the connection's config — the same as pasting a webhook URL. Gladly's integration is newer and less thoroughly verified than the rest of this batch; test it against your own org before relying on it.

Slack works the same way: it takes a bot token and channel id rather than the app-install flow you might expect. No OAuth app or workspace-wide install is needed — each connection uses its own bot token, scoped to whatever channel you invite it into.

Setting up a connection

• Open the form: go to the form's detail page and select the Connections tab.
• Pick a connector: available connectors show a Connect button; locked or coming-soon ones are shown but disabled.
• Fill in its config: a webhook URL for Discord/Webhook/Zapier, a recipient address for Email, or a reply message for Auto Response.
• Save: the connection is enabled immediately and fires on the next real submission.

curl -X POST https://api.tryembedio.com/v1/forms/frm_xxxxxxxxxx/connections \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{"connectorId": "discord", "config": {"webhookUrl": "https://discord.com/api/webhooks/..."}}'

Connector setup guides

Where to find each field for the API-key connectors — every other field in a connection's config is either the value itself (a webhook URL, an email address) or one of these.

Slack

• Bot Token: create an app at api.slack.com/apps → Create New App, add the chat:write Bot Token Scope under OAuth & Permissions, then Install to Workspace — it gives you a Bot User OAuth Token starting with xoxb-.
• Channel ID: invite the bot to the target channel (/invite @your-bot-name in Slack), then open the channel's details panel — the channel id is at the bottom (starts with C). A channel name like #general also works.

Telegram

• Bot Token: message @BotFather on Telegram, send /newbot, and follow the prompts — it replies with a token like 123456789:AA...
• Chat ID: add your bot to the target chat or channel, send it a message, then open https://api.telegram.org/bot<token>/getUpdates in a browser — the chat id is in the JSON response (a channel's id usually starts with -100).

Airtable

• API Key: create a Personal Access Token at airtable.com/create/tokens, scoped to data.records:write for the base you're connecting.
• Base ID: open your base in Airtable — it's the appXXXXXXXXXXXXXX segment in the URL.
• Table Name: the exact name of the table to create records in. Its columns need to match your form's field names — Airtable can't create a new column on the fly.
• Allowed submission fields: list the exact form field names that this connection may write, one per line. Other submitted fields are ignored, including any visitor-supplied status or internal columns.

Trello

• API Key: generate one at trello.com/power-ups/admin (or trello.com/app-key while logged in).
• Token: the same page links to a token-generation URL — authorize it to get your token.
• List ID: open the board in a browser and append .json to the URL, or call GET https://api.trello.com/1/boards/<boardId>/lists?key=...&token=... to list every list's id.

ActiveCampaign

• Account URL & API Key: in ActiveCampaign, go to Settings → Developer — both the API URL and API Key are shown there, ready to copy.

Pipedrive

• Domain: your Pipedrive company subdomain — the yourcompany in yourcompany.pipedrive.com.
• API Token: Settings → Personal preferences → API — copy your personal API token.

ConvertKit

• API Secret: Settings → Advanced → API — copy the API Secret (not the API Key).
• Form ID: Grow → Landing Pages & Forms, open the target form — its id is in the URL.
• Allowed submission fields: list the exact custom field names that this connection may update, one per line. The email address is sent separately; all other unlisted fields are ignored.

Klaviyo

• API Key: Settings → API Keys → Create Private API Key, granting it Profiles and Lists write access.
• List ID: Lists & Segments, open the target list — its id is in the URL.

MailerLite

• API Key: Integrations → API → Generate new token.
• Group ID (optional): Subscribers → Groups, open the target group — its id is in the URL. Leave blank to add subscribers without a group.

Freshdesk

• Domain: your Freshdesk subdomain — the yourcompany in yourcompany.freshdesk.com.
• API Key: click your profile picture → Profile Settings — your API key is shown on the right.

Gladly

• Organization URL: your Gladly org's URL, e.g. https://yourorg.gladly.com.
• Agent Email & API Key: generated from an agent account in Gladly's admin settings — the two together authenticate as that agent.

Gladly's integration is newer and less thoroughly verified than the rest of this batch — test it against your own org before relying on it in production.

Webhook connector signing

The Webhook connector signs every delivery with HMAC-SHA256, the same scheme documented under Webhooks in the API Reference. The signing secret is generated once, server-side, when the connection is created, and is never accepted from your request.

Testing a connection

Every connection has a Test button that sends a synthetic payload through the real delivery path and records the attempt in that form's delivery log — useful for checking a webhook URL or Discord channel before it goes live.

Connections and Form Rules

By default an enabled connection fires on every real submission. If you want a connection to fire only under certain conditions (a dropdown value, a field being non-empty), target it from a Form Rule instead — see Form Rules.