Mailhook and Front: Inbound Ticket Triage and Tagging Template
Turn a forwarded support inbox into auto-triaged Front conversations, with each inbound email classified and tagged for instant routing.
What It Builds
A Mailhook trigger gives the workflow its own inbound address. When you forward your support inbox to it, every email starts a run. A Connector node creates or updates a matching Front conversation, then an Agent-mode Connector node reads the subject and body to classify topic and urgency. A final Connector node applies the matching Front tags so the conversation lands in the right queue the moment it arrives.
The Prompt
Paste this into Miraxa and it builds the workflow, connecting the tools for you:
Create a Mailhook that I forward my support inbox to. For every inbound email, create or update a Front conversation from the sender, subject, and body. Then classify the message by topic (billing, technical, sales, or general) and urgency (low, normal, high), and add the matching Front tags to that conversation so it is triaged automatically.Connectors Used
- Mailhook - the trigger; forward your support address to the workflow's inbound mailbox.
- Front - creates or updates the conversation and applies topic and urgency tags.
Customize It
Edit the prompt to change the topic and urgency labels, point the tags at your own Front tag names, or route high-urgency mail to a specific inbox. You can also have Spojit add a private comment summarizing the email without a second prompt.
Tips
- Use Direct mode for the create and tag steps (no AI cost) and Agent mode only for classification.
- Give a Response Schema for the classifier so topic and urgency come back as clean, predictable fields.
- Make sure your Front tags exist first so the workflow can match them by name.