Monday and Slack: Form-Submission Acknowledgement Alert Template

A Spojit template that catches a website form submission over a Webhook, logs it as a monday.com item, and posts a Slack alert with the contact details so your team can respond to the new enquiry right away.

What It Builds

A Webhook trigger receives the form payload your website posts to Spojit. A Connector node on the monday connector creates a board item for the enquiry so nothing slips through the cracks, then a Connector node on the slack connector sends a message to your chosen channel with the contact's name, email, and message. The result is a tracked lead in monday.com and an instant heads-up in Slack, every time someone submits your form.

The Prompt

Paste this into Miraxa, the intelligent layer across your automation, and it builds the workflow, connecting the tools for you:

Build a workflow that triggers on a webhook when my website form is submitted, creates an item on my monday.com "Enquiries" board with the submitter's name and email, then sends a message to the #leads Slack channel with the name, email, and their message so the team can follow up.

Connectors Used

  • Webhook trigger - receives the form submission as a JSON body posted to the workflow's URL.
  • monday - logs the enquiry as a board item with create-item in a Direct-mode Connector node.
  • slack - posts the alert with send-message in a Direct-mode Connector node.

Customize It

Swap the channel name (#leads) and the monday.com board name in the prompt to match yours. If your form sends extra fields such as a phone number or company, name them in the prompt so they map into the item and the Slack message. You can also reference the parsed values directly with variables like {{ input.name }}, {{ input.email }}, and {{ input.message }} once the nodes are on the canvas.

Tips

  • The Webhook trigger verifies callers with a signing connection. Pick the Custom scheme if your form host signs requests, or Spojit if you control the sender, and point your form at the workflow's URL.
  • Keep both Connector nodes in Direct mode: each call is a single predictable action (create-item then send-message), so you avoid AI credit cost and get deterministic output.
  • Use lookup-user-by-email on the slack connector if you want to @-mention the right owner for the enquiry instead of posting to a shared channel.

Related

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.