Zapier Integration

    Zapier is a destination in Formboost, alongside Slack, Discord and Telegram. Point it at a Zap and every submission starts that Zap automatically.

    Formboost does not publish an app in Zapier's catalogue. The connection is made with Zapier's Webhooks by Zapier trigger, which takes about two minutes to set up.

    Zapier is available on the Starter plan and above.

    Setup

    1. In Zapier, click Create and choose Webhooks by Zapier as the trigger app
    2. For the event, choose Catch Hook, then click Continue
    3. Leave the optional child key field blank and click Continue
    4. Zapier shows a URL beginning https://hooks.zapier.com/hooks/catch/ — copy it
    5. In Formboost, open your form → Integrations tab → Zapier → Connect
    6. Paste the catch-hook URL, optionally give it a name, and save
    7. Click Send test — Formboost delivers a sample payload immediately
    8. Back in Zapier, click Test trigger. It will find the sample Formboost just sent
    9. Add your action steps and turn the Zap on

    What Zapier Receives

    Every delivery is a POST with a JSON body in this shape:

    1{
2  "event": "form.submission",
3  "eventId": "sub_3b241101-e2bb-4255-8caf-4136c566a962",
4  "sentAt": "2026-08-24T12:00:00.120Z",
5  "form": {
6    "name": "Contact Form",
7    "alias": "contact"
8  },
9  "submission": {
10    "name": "John Doe",
11    "email": "[email protected]",
12    "message": "Hello",
13    "submittedAt": "2026-08-24T12:00:00.000Z"
14  }
15}

    The same envelope goes to the n8n and HTTP Webhook destinations, so a Zap built against it keeps working if you move to another one.

    FieldMeaning
    eventform.submission, or form.submission.test for a test delivery
    eventIdsub_<submission id>, stable across retries — filter on it to avoid running a Zap twice for the same submission. Tests get a test_<uuid> id
    sentAtWhen this attempt left Formboost. Changes on every retry
    form.name / form.aliasThe form's display name and endpoint alias
    submission.submittedAtWhen the form was filled in — unchanged by retries
    submission.*Your own form fields, exactly as submitted

    Your fields sit alongside submittedAt inside submission, so in the Zap editor they appear as submission__email, submission__name, and so on. Formboost's own metadata stays at the top level, so a field of your own called event or name cannot shadow it.

    Only submittedAt is reserved: a form field of that name is dropped in favour of the real timestamp.

    To ignore test deliveries, add a Filter step on event.

    Example Workflows

    ZapWhat it does
    Formboost → Google SheetsAppend every submission as a new row
    Formboost → HubSpotCreate or update a contact from the email field
    Formboost → NotionAdd a page to a database for each enquiry
    Formboost → AirtableLog submissions into a base for triage
    Formboost → GmailSend a tailored follow-up email

    Delivery and Retries

    Deliveries are asynchronous. Formboost accepts the submission first and delivers to Zapier in the background, so a slow or unavailable Zap never delays or fails the form submission itself.

    Every attempt is recorded in the delivery log for that destination, with the response status, how long it took, and the error if it failed. Failed deliveries are not retried automatically — open the delivery log and click Retry to resend one from its stored submission.

    Troubleshooting

    ProblemFix
    404 or 410 in the delivery logThe Zap was deleted or turned off, or the URL is wrong. Check the Zap is on, and re-copy the catch-hook URL
    URL rejected when savingIt must start https://hooks.zapier.com/hooks/catch/. Other Zapier webhook URLs are not Catch Hook triggers and will never fire
    429 in the delivery logZapier rate-limited the request. Retry from the delivery log
    Zapier's Test trigger finds nothingPress Send test in Formboost first — Zapier can only find a payload it has already received
    Zap runs but fields are emptyYour action steps are probably mapped to the wrong level. Form fields are under submission__, not at the top level

    Notes

    • One Zapier destination per form. To drive several Zaps from one form, use a single Zap with multiple actions, or Zapier's own Paths.
    • The catch-hook URL is treated as a credential: anyone holding it can write into your Zap. Formboost masks it after saving and never logs it in full.
    • Only https:// URLs are accepted, and only public addresses.
    PreviousHTTP WebhookNextn8n Integration