Send a Webhook When a monday.com Form Is Submitted
Published on October 18, 2026
Your form data needs to reach something that is not monday.com: a CRM, a serverless function, an internal API, a data warehouse. A Slack message or an email will not do. You need an HTTP request carrying the submission, sent the moment it lands.
Neither WorkForms nor FormFlow has a “send to webhook” setting on the form itself. The webhook comes from the board. This post shows where to set it up and where the pattern stops working.
Quick answer
- The form does not send the webhook. monday.com’s board-level Webhook integration does, when an item is created or a column changes.
- Because the trigger watches the board, it fires the same way whether a WorkForms or a FormFlow submission created the item.
- Your endpoint must pass monday.com’s challenge handshake before the webhook is saved.
- Install FormFlow if you want update forms that also fire the webhook when an existing item changes.
Why the Form Has No Webhook Setting
FormFlow’s form settings control what the respondent sees after submitting: a Thank You page or an external redirect. No outbound webhook appears in the feature checklist. WorkForms is the same: the form controls the submitter’s experience, and the item on the board is the output.
That item is the hook. An insert form creates a board item. An update form writes to an existing one, as covered in how to update existing monday.com items with a form. Either way, something changes on the board, and monday.com can send an HTTP POST for board events.
Setting Up the Webhook
monday.com documents the board-level Webhook integration in its Integrations center. The steps:
- Open the board that receives the form submissions and click Integrate.
- Search for Webhooks and pick the recipe that matches your event, such as the one that sends a webhook when an item is created.
- Enter the HTTPS URL of your endpoint.
- Complete the challenge handshake (next section).
- Submit a real test through the form and confirm your endpoint receives the request.
The Challenge Handshake
When you create a webhook, monday.com sends a POST to your URL with a JSON body containing a random challenge token. Your endpoint must return that same JSON body in its response. Until it does, monday.com does not save the webhook.
This is the step that trips people up. If your endpoint only expects the real event payload, it will reject or mishandle the first request and the setup fails. Handle the challenge case first, then the normal event.
monday.com’s Webhooks API reference describes the same handshake for webhooks created through the API.
Insert Forms vs Update Forms
Pick the event to match the form type:
| Form type | What happens on the board | Event to listen for |
|---|---|---|
| Insert form | A new item is created | Item created |
| Update form (FormFlow) | Columns on an item change | Column value changed, or the columns used |
For update forms, a column-change event fires once per changed column rather than once per submission. If your backend needs one call per submission, the item-created pattern is the cleaner fit, or you can write a “processed” marker column and filter on it.
Webhook vs Other Ways to Get Data Out
- Webhook: push. Your endpoint is called when the event happens. Good for real-time sync into your own systems.
- API query: pull. You ask monday.com for items on a schedule. 5 Ways to Get Form Data Into monday.com covers the GraphQL API in the other direction.
- Chat alert: for people, not systems. See Slack or Teams alerts on a form submission.
What to Check Before Relying on It
- The payload describes the board event. Confirm in a test which fields it carries, and fetch full item details by API if you need more.
- Your endpoint needs to respond over HTTPS and handle repeated or out-of-order calls safely.
- Respondents who submit files or signatures create items with those values in Files columns; your endpoint will need the API to retrieve them.
Frequently Asked Questions
Does FormFlow have a built-in webhook setting?
No. FormFlow’s settings cover the Thank You page and external redirects. Sending a webhook is done by a monday.com board integration that reacts to the item the form creates or updates.
Does the webhook fire for WorkForms submissions too?
Yes. The webhook watches the board, not the form builder, so any submission that creates or changes an item can trigger it.
Why does my webhook fail when I save it?
Most often the endpoint did not return the challenge token monday.com sends during setup. Return the same JSON body you receive, over HTTPS.
Can an update form trigger a webhook?
Yes, through a column-change event, since an update form changes columns on an existing item instead of creating one.
Next Steps
- Automate FormFlow forms with monday.com automations →
- Update existing items with a form →
- Review FormFlow form settings →
- Install FormFlow and build your first form.
Last reviewed: 2026-10-03. monday.com webhook setup and challenge handshake verified against monday.com’s Webhook integration support article and Webhooks API reference , via search summaries. Features may change.