Mailhook and Slack: Expense Claim Email Triage Template
When an employee emails an expense claim to a dedicated mailhook address, Spojit summarizes it and posts a clean approval card to your finance Slack channel.
What It Builds
A Mailhook trigger gives the workflow its own inbound address that staff send expense claims to. Each email starts a run: a Connector node in Agent mode reads the subject and body, pulls out the employee, amount, category, and purpose, then writes a short summary. A Slack Connector node posts that summary to your finance channel so a reviewer can approve at a glance.
The Prompt
Paste this into Miraxa and it builds the workflow, connecting the tools for you:
Build a workflow that triggers on a mailhook address when an employee emails an expense claim. Use an AI step to summarize the email into employee name, amount, expense category, and purpose, then post that summary to the #finance-approvals Slack channel with a clear heading and the original sender's email.Connectors Used
- Mailhook trigger - the inbound email address that starts each run.
- Slack - posts the summarized claim to your finance channel for approval.
Customize It
Change #finance-approvals to your real channel, and edit which fields the summary pulls out (add a cost center, project code, or receipt total). You can also tighten the summary tone or ask it to flag any claim over a threshold amount.
Tips
- Share the mailhook address only with staff who should submit claims, and add a subject filter to ignore replies and out-of-office mail.
- If claims arrive as PDF receipts, add an Attachment node to pull the file before summarizing.
- For a formal sign-off step, add a Human approval node before any downstream posting.