HTTP and Monday: Demo Request Lead Routing Template

This Spojit template catches demo-request form posts over a webhook, routes each lead to the right region or rep, and drops an assigned item onto your Monday CRM board.

What It Builds

A Webhook trigger receives each demo-request submission from your marketing form. A Connector node in Agent mode reads the lead details and decides the right region or rep, then a Monday Connector node in Direct mode creates a new item on your CRM board with the owner already assigned. The http connector receives the raw post, so any form tool that can send an HTTP request works.

The Prompt

Paste this into Miraxa and it builds the workflow, connecting the tools for you:

Build a workflow that triggers on a webhook when a demo-request form is submitted with the name, email, company, country, and message. Have an agent decide the right sales region and rep based on the country and company size, then create a new item on my Monday CRM board with the lead's name as the title, the email, company, and message in columns, and the chosen rep set as the item owner.

Connectors Used

  • Webhook trigger - starts a run on each incoming demo-request form post.
  • http - receives the raw form payload; works with any form tool that can post JSON.
  • monday - creates the assigned item on your CRM board.

Customize It

Change the routing rules in the prompt (region by country, company size, or product interest), swap the board name, and edit which fields land in which Monday columns. You can also tell the agent to add a priority or tag, or to skip routing and assign every lead to one rep.

Tips

  • Give the agent clear rules (for example "EMEA goes to Priya, North America to Sam") so routing stays predictable.
  • Use the Monday node in Direct mode for the item creation so it always calls the exact create-item action with no AI cost.
  • Enable HMAC signing on the Webhook trigger if your form tool supports it to reject spoofed posts.

Related

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