What is MSPintegrations

MSPintegrations is an automation platform for Managed Services Providers. It connects email, schedules, form submissions, and PSA events to your PSA (Autotask, ConnectWise, or HaloPSA) and other business systems.

Each module gives you the same building blocks instead of a fixed recipe. Across modules, the core pattern is to extract useful data from the trigger, look up the records you need, then create or update the right record. You can arrange those building blocks to match how your team already works.

The Six Modules

You purchase modules to match the work you want to automate. Four modules start automation; two toolkits add capabilities to that automation.

Module	What it provides
Email Processing	Automation triggered by incoming email, using Hosted Mailboxes or Remote Mailboxes. Also branded Email2AT, Email2CW, or Email2Halo for your PSA.
Scheduled Tasks	Automation triggered by a recurring schedule.
Forms	Structured input from customers or staff, with automation triggered by a form submission.
PSA Workflows	Automation triggered by changes inside your PSA.
Developer Toolkit	Macros, custom scripts, key/value storage, and outbound HTTP requests.
AI Toolkit	AI extraction and prompting, including the Autotask AI Picklist Chooser for Autotask users.

Automations share the same action library, variable model, and history and replay tools. You learn how to configure action steps once and apply that knowledge to every trigger type. Your subscription determines which modules and actions are available.

Email Processing uses the PSA API directly. For example, it can identify an Autotask account before creating a ticket, so the ticket starts on the right account instead of going through Autotask's email processor and getting moved afterward.

What Automations Have in Common

• Triggers: something kicks off a run: an inbound email, a scheduled occurrence, a form submission, or a PSA event. Toolkits extend what your actions can do; they do not add a separate trigger type.
• Action Steps: the ordered work you configure using the shared Actions library. Email Processing groups steps into rules; scheduled tasks, forms, and PSA event subscriptions have their own action lists.
• Variables: action steps store results in custom variables, and meta variables provide run details. Some automations add their own variables, such as email in Email Processing and input in macros and forms. See Variables.
• History and Replay: every run is recorded. You can open the full execution log and replay the same trigger against the latest configuration.

Who It Is For

• IT consultants automating email intake for their PSA.
• Network engineers turning alerts from RMM, backup, and monitoring tools into tickets with the right contact, account, and configuration item.
• Support teams routing inbound support email, public intake forms, and scheduled data syncs through one consistent automation engine.

Getting Started

Start with Core Concepts for the mental model that applies to every automation. Then follow Create Your First Mailbox to build an Email Processing setup end-to-end.

If you need a hand, our team is available at [email protected].