Mailhook and Front: Attachment-Heavy Ticket Intake Template

A Spojit template that turns customer emails full of screenshots and logs into clean Front conversations, with the attached evidence ready for an agent to review.

What It Builds

A Mailhook trigger gives the workflow its own inbound address, so any customer email that lands there starts a run. An Attachment node fetches the attached screenshots or log files, an Agent-mode Connector node summarizes what the customer is reporting, and a Front Connector node opens a conversation with that summary plus a note listing the attached evidence for your support team.

The Prompt

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

Build a workflow triggered by a Mailhook. When a customer emails the address, fetch any attached files, summarize the reported issue from the subject and body, then open a Front conversation containing the summary and a note that lists each attachment by filename so an agent can review the evidence.

Connectors Used

  • Mailhook - the trigger; provides the inbound email address and the customer's message and attachments.
  • Attachment node - fetches the attached screenshot or log bytes from the inbound email.
  • Front - opens the support conversation with the summary and evidence note.

Customize It

Change which Front inbox the conversation lands in, add a tag like needs-evidence, or have the summary flag urgent keywords. You can also tell the prompt to set the conversation subject from the original email subject so threads stay recognizable.

Tips

  • The Attachment node only works in Mailhook workflows; set it to Multiple so every file from the email is captured.
  • Keep the Front node in Direct mode for a single, predictable create-conversation action, and reserve Agent mode for the summary step.
  • Confirm your Front connection has permission to create conversations in the target inbox.

Related

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