Mailhook, MongoDB and Monday: Inbound Form Routing Template

When an inbound request emails a mailhook address, store the raw submission in MongoDB and create a triaged Monday item for follow-up.

What It Builds

This template wires a Mailhook trigger to two connectors so every form submission that lands in your inbox becomes a durable record and an actionable task. The Mailhook trigger fires the moment mail arrives at your generated address, an Agent-mode Connector node reads the email and pulls out the key fields, the mongodb connector stores the raw submission with insert-documents, and the monday connector opens a triaged item with create-item so your team can pick it up.

The result is a single inbound pipe: point any contact form, support address, or vendor notification at the mailhook address and Spojit keeps the full submission in MongoDB for the record while surfacing a ready-to-action card in Monday.

The Prompt

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

Build a workflow with a Mailhook trigger. When an email arrives, use an Agent-mode Connector node to extract the sender name, email address, subject, and a short summary of the message from {{ input }}. Insert the full raw submission as one document into my MongoDB "submissions" collection, then create a Monday item on my intake board with the sender name as the item name and the summary, email address, and received date as column values. Set a priority of Normal.

Connectors Used

  • Mailhook trigger - generates a unique address that starts a run the moment mail arrives; no mailbox or OAuth needed.
  • mongodb - stores the raw submission with insert-documents so you keep a complete archive of every form.
  • monday - creates the triage card with create-item on your intake board.
  • An Agent-mode Connector node - the in-workflow agent that reads the email and extracts the fields to map across.

Customize It

Change the MongoDB collection name (submissions) to match your archive, swap the Monday board and column mapping for your own intake board, and adjust the priority value. To screen out noise before anything is stored, add a From allowlist or Subject regex filter on the Mailhook trigger. If a submission needs a quick reply, ask Miraxa to add a Send Email node addressed to {{ input.replyTo }} as a final step.

Tips

  • Use the Mailhook trigger only when you control where the mail is sent (a form action, a forwarding rule, or vendor notifications). If the mail already lands in a mailbox you own, an Email trigger fits better.
  • Keep the MongoDB insert-documents call in Direct mode so the write is deterministic and costs no AI credits; reserve Agent mode for the extraction step only.
  • Store the whole {{ input }} payload in MongoDB rather than only the extracted fields, so you always have the original message if the triage card needs to be rebuilt.

Common Pitfalls

  • The monday create-item call needs the correct board ID and column IDs. If the item appears without values, confirm the column mapping in the node's properties panel against your board.
  • Mailhook runs are always asynchronous, so there is no response to the sender. Reply with a Send Email node to {{ input.replyTo }} if the submitter expects acknowledgement.
  • Regenerating the mailhook address retires the old one instantly. Update your form action or forwarding rule before you rotate it, or inbound mail will bounce.

Related

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