Send every submission onward to the tools you already use. Tiger Forms ships real, retrying integrations with signature-safe logging — each attempt is recorded, failures are retried on a backoff schedule, and secrets are masked before anything is written down.
Where: per-form mapping lives in the Form Builder under Settings → Integrations. Reusable credentials live under Tiger Forms → Settings → Integrations.
Available integrations
| Category | Connectors |
|---|---|
| Email marketing / CRM | Mailchimp, Brevo, Kit (ConvertKit), Klaviyo, GetResponse, ActiveCampaign, HubSpot |
| Productivity | Notion, Google Sheets |
| Automation | Slack, Zapier, generic Webhook |
The marketing and CRM connectors can store their API key once as a global credential and be reused across every form. The automation connectors — Webhook, Zapier, Slack, Notion and Google Sheets — are configured per form, since each one points at a different endpoint or workspace.
Set up an integration
- Store the provider’s API key under Tiger Forms → Settings → Integrations (for the marketing/CRM connectors), or have the endpoint URL ready for a webhook.
- In the Form Builder open Settings → Integrations and add the connector.
- Map form fields to the provider’s fields — for example email, first name and tags to a Mailchimp audience, or form fields to columns of a Notion database.
- Optionally gate the send with conditional logic so only some submissions sync (e.g. only when a “Newsletter” checkbox is ticked).
- Use the Test action to push a sample payload and confirm the connection end to end.
Webhooks
The generic Webhook connector POSTs the submission as JSON to any URL. You can add an HMAC secret; when set, Tiger Forms signs the exact request body with SHA-256 and sends it in a signature header (X-Tigform-Signature by default, or a header name you choose), so the receiving system can verify the payload really came from your site and was not altered.
Reliability
Integrations are not fire-and-forget. A failed send is retried on a backoff ladder rather than silently dropped, and every attempt is logged with the request payload, the provider’s response and any secrets redacted. Credentials are encrypted at rest. You can run integrations before payment where a form charges money, so a lead is captured even if checkout is abandoned.
Troubleshooting
The provider isn’t receiving anything.
Open Tiger Forms → Logs and find the submission. The recorded response usually names the exact problem — an invalid API key, a missing required field, or an unknown list/audience ID.
Some submissions sync and others don’t.
That is conditional logic doing its job. Re-check the condition on the integration; only submissions that satisfy it are sent.
My webhook receiver rejects the request.
If you enabled an HMAC secret, verify the receiver is computing sha256 over the raw body with the same secret and reading the correct signature header.