Spam and integrations
Spam protection
Every submission goes through several checks: the honeypot field, a list of spam phrases, the number of links, HTML or BBCode links, submissions sent too quickly after the page loaded, repeated submissions within 10 minutes, and gibberish. Set the sensitivity per form.
You can also add reCAPTCHA, hCaptcha or Cloudflare Turnstile.
Bots get a normal "success" response so they don't adapt. Their submissions go to Spam, trigger nothing, and don't count towards your plan.
Integrations
Integrations run in the order you set, each with optional conditions (for example "only when
budget is greater than 5000"). Failed deliveries are retried after 1, 5 and 30 minutes, every run is
logged, and Test sends a sample.
| Integration | What it does |
|---|---|
| Send to CRM | Creates or updates a contact (and optionally a deal and consent) in the TraffikCo CRM, HubSpot, Salesforce or Dynamics, with field mapping |
| Sends the submission to extra addresses | |
| Slack, Discord, Telegram | Posts a message to a channel |
| Airtable, Notion | Adds a row or page |
| Mailchimp | Adds the email to an audience |
| Webhook | POSTs JSON to any URL; works with Zapier, Make and n8n |
Webhooks can be signed: set a secret and each request includes
X-TraffikCo-Signature: t=<unix time>,v1=<HMAC-SHA256 of "t.body">. Verify it the same way as
CRM webhooks.
For automations that go beyond a single delivery, use the Form submitted trigger in Automations.