Questions arrive in the support mailbox, need to land in Jira or Asana
Mail-to-ticket is a classic automation. Watchouts: dedup (one ticket per thread, not per reply), correct field mapping, and feedback to the sender.
Try this first
- 1Trigger on new mail in the support inbox. Read sender, subject, body, attachments.
- 2Dedup check: does a ticket already exist for this mail thread id (Message-ID or References header)? If yes, append as comment instead of new ticket.
- 3Create the ticket in Jira or Asana with fields: title = subject, description = body, reporter = sender (or placeholder if unknown), labels based on content.
- 4Send sender a confirmation mail with the ticket number. Prevent auto-response loops by including the ticket id in subject and configuring your auto-mailer well.
- 5On status change: send an update to the sender. Two-way sync (mail reply as comment) is a follow-up step, not always needed in v1.
When to bring us in
Want real two-way sync with mail replies coming back as comments, a tool like HelpScout or Front is worthwhile. We can look.
See also
- n8n: self-host or cloud?Self-hosted is cheaper at volume and keeps data local. Cloud removes ops burden.
- Zapier or Make: which fits better?Zapier is straight-line; Make handles complex flows with routers and iterators for less money.
- Power Automate Cloud or Desktop: which to use?Cloud for SaaS integrations and triggers. Desktop for RPA against legacy Windows apps without APIs.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.