Form connectors: send every submission where you already work
Connectors pass each form submission from your published sites to the tools you already use: Slack, Discord, any webhook, Telegram, Google Sheets, Airtable, Notion, HubSpot, Mailchimp and Kit. You set them up once on your account, the details are checked against each provider's format and sealed, and a test button shows they work before a real visitor relies on them.
Why built-in connectors instead of an automation tool
The usual way to get a website form into Slack or a spreadsheet is a chain: form service, then an automation tool, then the destination. Each link is another account, another set of credentials and another place for a message to vanish. Anticode's website form integrations skip the middle. The site saves the submission, and Anticode's own server sends it straight to the destination's official API. If you need branching logic, you can still point the generic webhook at an automation tool.
The ten destinations and what each receives
| Connector | You provide | What arrives |
|---|---|---|
| Slack | An incoming-webhook URL from hooks.slack.com | A message with the form name and each field |
| Discord | A channel webhook URL | A message with mentions switched off, so @everyone in a visitor's text stays plain |
| Webhook | Any https:// URL | JSON with the event, site, form, fields and time |
| Telegram | A bot token from BotFather and a chat id or @channel | A plain-text message, with link previews off |
| Google Sheets | An Apps Script web app URL (the script is provided to copy) | The site, form, time and fields, for the script to add as a row |
| Airtable | A personal access token, base id and table name | A record with Site, Form, Submitted and Details |
| Notion | An integration secret, database id and title property | A page titled with the submission, one paragraph per field |
| HubSpot | A private app token | A contact with email, first and last name and phone, for forms that include an email |
| Mailchimp | An API key and audience id | Newsletter sign-ups only, added as pending so Mailchimp sends its own confirmation (double opt-in) |
| Kit | An API key and form number | Newsletter sign-ups only, subscribed to that form |
Checked before saving, sealed after
Each credential is checked against the shape that provider issues before it's accepted. A Slack connector only takes a hooks.slack.com address, an Airtable token has to start with pat and a base id with app, a Mailchimp key must end in its data-centre suffix. Mistakes get a message that says what the right value looks like and where to find it, rather than a silent failure on the first real submission.
Once saved, URLs and credentials are encrypted with AES-256-GCM and bound to your account and that connector, so a copied row can't be decrypted elsewhere. They are write-only: the dashboard never shows them again, and they never reach the builder or your published pages. To change one, enter the details again. Each destination is reached only at its own fixed API address.
Testing a connector
After saving, press Send a test. For Slack, Discord, the webhook, Telegram, Sheets, Airtable and Notion this sends a sample contact message right away, so you see exactly how a real one will look. For Mailchimp, Kit and HubSpot the button reads Check the connection instead: it confirms the key and list are valid without adding a fake subscriber or contact. If anything fails, the message names the service and the status it answered with.
How delivery works
- Account-wide. Connectors are saved to your account, so they apply to every site you publish.
- Within a minute. Submissions are saved first, then a scheduled job on the server sends them on, along with your email alert if you have one.
- Once each. Every submission is sent once to every enabled connector. There are no automatic retries, so a destination that's down at that moment misses it; the submission itself stays in your dashboard.
- Free plan allowance. Submissions past a free site's monthly allowance are held and never sent to connectors, even after an upgrade, which only makes them visible in the inbox; see form submissions.
Where connectors stop
- No field mapping. Each connector sends a fixed shape. For custom columns, use the Sheets script, the webhook, or a site function.
- Per account, not per site. You can't send one site's forms to one Slack channel and another's elsewhere with two Slack connectors. Each submission is tagged with the site's name, so a webhook can route by site.
- No email to visitors. Mailchimp's confirmation is Mailchimp's; Anticode itself doesn't write to the people on your list.
- Payment links are different. The payment-link connector stores a public checkout URL for your buttons and sends nothing; see payment links.
Questions people ask
Do I need Zapier or Make?
Not for these ten destinations. If you want multi-step automations, point the generic webhook connector at Zapier, Make, n8n or Pipedream.
What if Slack is down when a form arrives?
That delivery isn't retried, but the submission is still saved in your dashboard, where you can read or export it.
Why don't contact messages go to Mailchimp?
Mailchimp and Kit only receive newsletter sign-ups, so people who sent a message or booking aren't added to your mailing list without asking.
Can I see my saved API key later?
No. Credentials are write-only once saved. Enter them again to replace them.