Skip to main content

Actions

Actions are the building blocks of automations in MSPintegrations. Every automation contains one or more actions in sequence, each receiving inputs from the automation's data and producing outputs that later actions can use.

What Is an Action?​

An action is an operation from the action library: creating a ticket, sending an email, querying an API, transforming a string, or controlling the automation's flow. An action step is one configured use of an action. When an automation runs, its steps execute in order, passing data forward through variables.

Actions work across the modules that start automations in MSPintegrations:

  • Email Processing: Process incoming emails with rules for responses, ticket creation, and routing
  • Scheduled Tasks: Run recurring automation on a schedule
  • Forms: Start automation when customers or staff submit structured input
  • PSA Workflows: Start automation when records change inside your PSA

Developer Toolkit extends these automations with macros, custom scripts, key/value storage, and outbound HTTP requests. AI Toolkit adds AI extraction and prompting, including the Autotask AI Picklist Chooser for Autotask users.

Inputs and Outputs​

Each action has:

  • Inputs (parameters): Fields you configure when building the automation. These can reference static values, text replacement variables, or the outputs of earlier actions.
  • Outputs (returned variables): Values produced by the action after it runs. The action stores them as variables that any later action can reference.

For example, a "Create Autotask Ticket" action returns the ID of the created ticket and the Account and Contact it was associated with. A later action can use those values to send a confirmation email, create a time entry, or update a related record.

How Actions Are Strung Together​

When you build an automation, you add actions in sequence. As each action runs, it reads from and writes to the automation's shared set of variables. This lets you:

  • Pass data from one step to the next using {{variable}} syntax
  • Branch or stop based on the results of earlier steps
  • Loop over collections to process multiple items in a single run

Choosing an Action​

Actions are grouped by category: PSA integrations, AI and LLM inference, string functions, control structures, notifications, and more. Each category contains actions suited to a particular type of task.

Browse the sidebar to find the action you need, or start with these common starting points:

  • PSA Integrations: Create and update tickets in Autotask, ConnectWise Manage, and Halo PSA
  • Control Structures: Loop over arrays, branch on conditions, and control execution flow
  • String Functions: Manipulate and transform text values
  • AI and LLM Inference: Prompt AI models and invoke Agentic Actions within your automations
  • Utilities: Send emails, set expiry dates, and perform general-purpose tasks