Monday, Slack and MySQL: New-Lead Logging Template

When a web-form lead posts to a webhook, this Spojit template creates a Monday item, writes the lead to MySQL, and notifies your sales team in Slack.

What It Builds

This template starts from a Webhook trigger that receives the JSON your lead form posts. From there it fans out across three systems: it creates a new item on a Monday.com board so sales has a card to work, inserts a row into a MySQL table so you keep a durable record, and sends a message to a Slack channel so the team sees the lead in real time. Each lead lands in your pipeline tool, your database, and your team chat in a single run.

The three writes run in parallel so the Slack alert is not held up by the database insert. Because every step keys off the same incoming payload, the same lead details appear consistently in Monday, MySQL, and Slack.

The Prompt

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

Build a workflow with a Webhook trigger that receives a web-form lead with name, email, company, and message. In parallel, create a Monday.com item on my "Leads" board named after the lead, insert a row into the "leads" table in MySQL with the name, email, company, message, and received timestamp, and send a Slack message to #sales saying a new lead came in with the name, company, and email.

Connectors Used

  • Webhook trigger - receives the lead form POST and exposes the parsed JSON body as {{ input }}.
  • Monday.com - the create-item tool adds a card to your leads board for sales to follow up.
  • MySQL - the insert-rows tool writes the lead to your database table.
  • Slack - the send-message tool posts the new-lead alert to your chosen channel.

Customize It

Change the board name (Leads), the table name (leads), and the channel (#sales) in the prompt to match your own setup. Adjust which fields flow through by naming them in the prompt: for example add {{ input.source }} or {{ input.budget }} so they appear in the Monday item, the MySQL row, and the Slack message. If you want sales notified only for high-value leads, ask Miraxa to add a Condition node before the Slack step.

Tips

  • Each connector needs a saved connection first. Add your Monday.com, MySQL, and Slack connections under Connections before you run the workflow.
  • These are predictable single-tool writes, so keep each Connector node in Direct mode to avoid AI credit cost and keep the field mapping deterministic.
  • Secure the webhook with a signing connection (the Custom scheme works well for a form backend) so only your form can trigger the workflow.

Common Pitfalls

  • The MySQL table must already exist with columns that match the fields you insert; insert-rows writes data, it does not create the schema.
  • The Monday board and column ids in your connection must point at the board you mean, or items land on the wrong board.
  • If a field is missing from the incoming payload, the matching {{ input.field }} resolves empty; validate your form sends every field you reference.

Related Articles

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