Integrations

Integrations let a form deliver its submissions to other systems as they arrive. Add and manage them from a form's Integrations tab.

Available integrations

• Webhooks — POST each submission to an HTTPS endpoint you control, signed so you can verify it came from Formiary.
• Slack — post each submission as a message in a Slack channel, via the Formiary Slack app.
• Zapier — trigger a Zap with each submission.
• Microsoft Teams — post each submission as a card in a Teams channel.
• Discord — post each submission as an embed in a Discord channel.
• Make — trigger a Make (ex-Integromat) scenario with each submission.
• n8n — trigger an n8n workflow with each submission, including self-hosted instances.
• Airtable — create an Airtable record for each submission in a base and table you pick.
• Pipedrive — create a Pipedrive person for each submission, with the fields you map.
• Attio — create or update an Attio record for each submission, matched on an attribute you choose.

Most integrations take a minute to set up: create a webhook on the other service, paste its URL into Formiary, done. Slack is even simpler — a team admin connects your workspace once, then any form can post to any channel.

How delivery works

When a submission is created, Formiary sends it to each active integration on the form. Deliveries are attempted asynchronously and retried on failure, so a slow or briefly unavailable endpoint won't block or lose submissions. Each attempt is recorded in a delivery log you can inspect from the integration.

Every integration also supports:

• Send test event — fire a synthetic submission through the real delivery pipeline to confirm your setup, even before the integration is active.
• Active toggle — pause deliveries without deleting the configuration.
• Delivery log — each attempt's request, response, and status (pending, in flight, success, failed, or dead-lettered), with manual retry for failures.