FormsFortIntegrations
FormsFort integration guide for webhooks, Slack, Discord, Telegram, and Google Sheets.
Integrations
Send accepted submissions beyond email. Integrations are feature-gated by manual entitlements, queued by workers, and redacted after successful delivery.
Supported integrations
Webhook
Queue a JSON POST to an HTTPS endpoint after an accepted paid/manual submission.
Zapier
Use Webhooks by Zapier with Catch Hook to fan submissions into downstream apps.
Make
Start a scenario from a custom webhook and map fields into actions or routers.
n8n
Pipedream
Receive submissions in an HTTP/Webhook source for debugging or code-first actions.
Airtable
Create records through a webhook automation platform or custom endpoint.
Notion
Create database pages through Zapier, Make, n8n, Pipedream, or your own handler.
CRM and databases
Route leads into HubSpot, Salesforce, PostgreSQL, MongoDB, or internal systems.
Slack
Send native notifications through a validated Slack incoming webhook URL.
Discord
Telegram
Send native notifications to a configured chat ID using the server bot token.
Google Sheets
Connect Google, choose a spreadsheet and sheet tab, then append accepted paid submissions.
Webhook field
<input type="hidden" name="webhook" value="https://example.com/formsfort" />Webhook payload
Generic webhooks receive a flat JSON body with submitted fields plus allowed metadata. Access keys, routing controls, attachment content, honeypots, and captcha tokens are excluded.
{
"name": "Ada Lovelace",
"email": "ada@example.com",
"message": "Hello",
"subject": "Website lead",
"from_name": "Example Site",
"submittedAt": "2026-05-19T12:00:00.000Z"
}Automation platforms
Use the generic webhook integration for no-code or low-code workflows. These are recipes over the same FormsFort webhook delivery path, not separate native apps.
Zapier: Webhooks by Zapier -> Catch Hook
Make: Webhooks -> Custom webhook
n8n: Webhook trigger -> workflow
Pipedream: HTTP/Webhook source -> actionCRM and data workflows
Automation platforms can map the webhook payload into Airtable records, Notion database pages, CRM leads, email marketing contacts, project-management tasks, or database writes.
Common mappings:
name-> lead/contact nameemail-> lead/contact emailmessage-> note/body fieldsubmittedAt-> received timestampsubject-> source or pipeline label
Testing and debugging
Send test submissions to Webhook.site, RequestBin, Pipedream RequestBin, or the target platform's execution log before switching to production endpoints.
Security and delivery rules
Webhook endpoints must use HTTPS, respond within the configured timeout, and treat incoming field values as untrusted user input. Successful delivery payloads are redacted after the worker records the result.
Headers:
Content-Type: application/json
User-Agent: FormsFort-Webhook/1.0
X-FormsFort-Request-Id: request idExcluded fields:
access_key, apikey, webhook, redirect, ccemail, replyto
attachment content, botcheck, recaptcha_response
h-captcha-response, cf-turnstile-response