Send Slack or Teams Alerts on a monday.com Form Submission
Published on October 8, 2026
A form submission lands on your board, and nobody on the team notices until someone happens to open it. For anything time-sensitive — a support ticket, an approval request, a new lead — that lag costs you. Posting the submission straight into Slack or Microsoft Teams closes the gap: the alert shows up where your team is already looking.
Neither WorkForms nor FormFlow sends that alert by itself. Both hand off to monday.com’s own Slack and Microsoft Teams integrations, so the setup is the same recipe whichever app wrote the item.
Quick answer
- Neither WorkForms nor FormFlow has a built-in Slack or Teams notification setting. Both create or update a board item on submission, and the alert comes from a board automation layered on top.
- monday.com’s native Slack and Microsoft Teams integrations post a channel message on triggers like item creation, status change, or a column update — available on the Standard plan and above.
- Route different submissions to different channels by pairing the automation with a Request Type dropdown and visibility rules.
- Install FormFlow and pair it with the automation recipe below.
Why Neither Form Builder Notifies Chat Apps Natively
FormFlow’s form settings cover the post-submission experience for the respondent — a Thank You page, an external redirect — but there is no Slack or Teams setting among them, and no chat integration is listed in FormFlow’s feature checklist. WorkForms is the same: the form itself only controls what the submitter sees.
What both share is the item that lands on the board. A WorkForms submission creates or updates an item the same way a FormFlow submission does — insert forms create it, update forms write to an existing one, as 5 Ways to Automate Your Forms with monday.com Automations covers for the “When a form is submitted” trigger. Once that item exists, monday.com’s own Slack integration and Microsoft Teams integration take it from there — the same architecture-independent pattern confirmation emails and multi-board delivery use.
Setting Up a Slack Alert
- Open the Integrations center on your board and connect the Slack integration if it is not already connected (available on the Standard plan and above).
- Open the Automations center and create a custom automation, or start from a Slack template such as “notify a channel when an item is created.”
- Set the trigger to “When an item is created” for insert forms, or “When a form is submitted” so update-form submissions fire it too.
- Set the action to post to Slack, choose the destination channel, and build the message from column-value placeholders so it includes what was actually submitted rather than a generic line.
- Save, then submit a real test through the form to confirm the message posts with the right values.
Setting Up a Microsoft Teams Alert
The Teams integration follows the same shape. Connect it from the board’s Integrations center, then build an automation on the same triggers — item created or form submitted. The message can include the submitter’s name, the board name, the item name, and a custom line you write, and you choose which channel in which team receives it.
Routing Alerts by Request Type
A single “new submission” channel gets noisy fast once a form covers more than one kind of request. If the form uses a Request Type dropdown — the pattern an internal request system uses to route IT, HR, and facilities requests to different teams — add a matching condition to the automation:
- When Request Type is “IT Support” → post to the #it-support channel
- When Request Type is “New Lead” → post to the #sales channel
- When Request Type is “Urgent” → post to a channel your team actually watches in real time
This is the same visibility rules pattern that shows or hides form fields by request type, applied to routing the resulting alert instead of the form’s own questions.
What to Put in the Message
Keep the alert specific enough to act on without opening the board:
- The fields that decide urgency or ownership — request type, priority, assignee.
- A direct link back to the item, so clicking through does not mean searching the board.
- Enough context that someone can triage from the channel alone, without every field on the form.
Skip anything that changes after submission (a status the team will update later) since the alert is a snapshot at submission time, not a live view of the item.
Frequently Asked Questions
Does FormFlow have a built-in Slack or Teams notification setting?
No. FormFlow’s settings cover the Thank You page and external redirects; posting to Slack or Teams is handled by a monday.com board automation, the same as WorkForms.
What plan do I need for the Slack or Teams integration?
monday.com’s native Slack and Microsoft Teams integrations require the Standard plan or above, the same tier where board automations become available.
Will this fire for update-form submissions, not just new items?
Yes. Trigger the automation on “When a form is submitted” rather than “When an item is created,” since update-form submissions modify an existing item instead of creating one.
Can I send the same submission to Slack and Teams at once?
Yes. Add a second automation on the same trigger with the other app’s action — both fire independently off the same form-submitted event.
Next Steps
- Automate FormFlow forms with monday.com automations →
- Send confirmation emails after a form submits →
- Send a webhook to your own backend on submission →
- Build an internal request system with routing →
- Install FormFlow and connect an automation to your next form.
Last reviewed: 2026-10-08. monday.com’s Slack and Microsoft Teams notification behavior and Standard-plan-and-above gating verified against monday.com’s Slack integration and Notifications via automations and integrations support articles. Features may change.