Mailhook and Front: Forwarded Email to Conversation Template

This Spojit template catches email forwarded to a Mailhook address and opens a matching Front conversation so stray inbound mail lands in your support inbox.

What It Builds

A Mailhook trigger generates a unique Spojit address you point your forwarding rules at. When a forwarded message arrives, the workflow reads the original sender, subject, and body from {{ input }}, finds or creates the matching contact, and uses a Connector node on the Front connector to start a conversation in your chosen inbox. The result is one tidy Front conversation per forwarded email, with the original sender attached as the contact rather than the forwarding mailbox.

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 with a Mailhook trigger. When an email is forwarded to the Mailhook address, look up the original sender in Front and create the contact if it does not exist, then create a new Front conversation in my Support inbox using the email subject as the conversation subject and the email body as the first message, with the original sender as the conversation contact. Add a tag called "forwarded" to the conversation.

Connectors Used

Mailhook (trigger) - generates a unique @mailhook.spojit.com address; forwarded mail starts a run within seconds, no mailbox or OAuth needed.
Front - looks up or creates the contact and opens the conversation in your support inbox; Miraxa wires this with tools such as get-contact, create-contact, list-inboxes, send-message, and add-tag.

Customize It

Change the inbox name (for example to Sales or Billing), adjust the tag, or drop the tagging step entirely. To narrow what triggers a run, set a From allowlist or Subject regex on the Mailhook trigger so only mail from your forwarding address or matching subjects gets through. You can also have the prompt reply to the original sender from Spojit's built-in mail service by adding a Send Email node addressed to {{ input.replyTo }}.

Tips

Use Mailhook (not the Email trigger) here because you control where the mail is sent: your forwarding rule points straight at the generated address.
Keep the Front step in Direct mode for predictable, no-AI-cost contact and conversation creation; reach for Agent mode only if you want the workflow to decide an inbox or tag from the email content.
The original sender lives in {{ input.from }} and the reply address in {{ input.replyTo }}; map these so the forwarding mailbox never becomes the conversation contact.

Common Pitfalls

If you rotate the address with Regenerate address, the old address dies instantly, so update every forwarding rule that targets it.
Mailhook fires whether the address is in To, Cc, or Bcc, so an over-broad forwarding rule can open conversations you did not intend; tighten it with a From allowlist or Subject regex.
A missing Front contact will cause the conversation contact to fall back to the forwarding mailbox unless the workflow creates the contact first; keep the find-or-create step in the prompt.