Create a Ticket for the Account Named in the Email Subject
Some automated emails name the customer in the subject, but every message comes from the same sender. If you identify the customer from that sender address, every ticket can land on the same catch-all account.
Add Tag to Autotask Ticket
A ticket tag can help your team group, filter, or report on tickets, but an automation needs the ticket's ID before it can add one. This tutorial adds the Television tag to a ticket that an earlier action already found or created.
Create an Autotask Project with Tasks and Dependencies
This tutorial walks through building an automation that creates an Autotask Project, adds Tasks to it, and links those Tasks with a dependency so they appear correctly in the Gantt chart. This pattern is useful for automating onboarding projects, recurring maintenance, or any repeatable project structure.
Associate a Contract and Service to an Autotask Ticket
Tickets without the right contract and service can require billing cleanup or send time entries to the wrong place. If your Autotask process depends on those associations, Email2AT can find them before it creates the ticket.
Create Autotask Opportunity from Forwarded Email
A useful customer email does not have to become a support ticket. When a customer expresses interest in a project or service, a sales rep can turn that message into an Autotask Opportunity without copying its details by hand.
Migrating from Email2Ticket
Email2Ticket by RapidFire Tools is not affiliated with MSPintegrations or Email2AT, but many Email2AT users have requested help in converting their workflows from Email2Ticket and bring them into Email2AT.
Monitoring Alerts to the Right Autotask Account and Ticket
Monitoring tools such as Meraki, SentinelOne, Sophos, Webroot, PRTG, and Auvik send alerts from a no-reply address. When those emails reach Autotask's built-in email processor, it cannot tell which customer the alert is about, so the tickets land on a catch-all account. Every alert also becomes its own ticket, so one flapping device can bury your techs in tickets they have to move, merge, and close by hand.
Prevent Reopening Old Closed Tickets
When a customer replies to a ticket that was closed weeks or months ago, the Update Existing Autotask Ticket action finds the old ticket and adds a note to it. This reopens a stale ticket instead of creating a fresh one.
PRTG Alerts with Autotask CI Association
PRTG sends alerts from a shared system address, so the sender does not tell Autotask which customer owns the affected device. Without another way to identify the customer, tickets can land on the wrong account and require manual cleanup.
Route Direct Customer Emails to Autotask
Customers sometimes email a technician directly instead of sending to your shared support address. When that happens, you need those emails to become properly attributed Autotask tickets with the correct Account and Contact, without asking customers to change their habits.
Create Tickets from Hashtag Actions in Ticket Notes
This tutorial walks through building a scheduled task that monitors Autotask ticket notes for a hashtag syntax (for example, #action) and automatically creates new tickets from each tagged entry. This lets technicians create follow-up tickets by simply adding structured notes to an existing ticket.
Turn UniFi Offline and Reconnected Emails into One Autotask Ticket
UniFi sends one email when a device goes offline and a separate email when it reconnects. Autotask cannot tell that the two messages belong together. The sender also may not identify the customer, so each email can become a separate ticket on the wrong account.