Skip to main content
How to write a one-line trigger and numbered steps, and choose which tools a workflow pre-approves. A workflow has a trigger (one line describing which tickets it applies to) and a list of numbered steps. Each step has a short title, instructions, and the tools the agent can use for it. When a ticket matches an active workflow’s trigger, the agent follows those steps.

How workflows apply to tickets

Every time a new ticket comes in, the agent looks at your active workflows and picks the ones whose triggers describe the ticket. It follows those steps as its plan. If nothing matches, the agent works the ticket the way it normally would. A few things to keep in mind:
  • More than one workflow can apply to the same ticket. The agent considers every workflow that matches, whether it’s shared or client-specific.
  • The agent follows matched steps as written. If a step is wrong, edit the workflow.
  • The agent matches on the trigger, not the steps. A vague trigger means missed matches, and a too-broad one means the workflow runs on tickets it wasn’t meant for.
  • Only active workflows are used. Drafts and archived workflows are ignored.

Workflows for all clients vs. a single client

You can create a workflow that applies to every client you support, or one that only applies to a single client. Start with shared workflows for anything that’s true across your clients, like onboarding, password resets, and ticket triage. Add a client-specific workflow only when one customer’s setup needs a different sequence, like an offboarding flow that reclaims a non-standard SaaS license. A pile of one-off client workflows is harder to maintain than one well-written shared one.

Promoting a client workflow to all clients

When a client workflow works well and fits your other clients too, promote it instead of rebuilding it. The workflow keeps its run history and its link. Every client’s agent picks it up as an MSP-wide workflow. You need permission to edit workflows. The workflow must be active.
  1. Open the client workflow and save or discard any unsaved edits.
  2. Click Promote to all clients. Rallied opens a preview of what changes.
  3. Review the preview, then click Promote to all clients to confirm.
The preview lists:
  • Runs without approval on every client: tools the workflow pre-approves once it applies to every client.
  • No longer pre-approved: tools that lose pre-approval under your MSP-wide approval settings. A technician approves these again.
  • Scripts that run on their own on every client: auto-run scripts that will run on every client without a technician.
  • Auto-run turns off: scripts that will wait for a technician again.
Rallied blocks the promotion if the workflow uses tools that aren’t connected for your whole MSP. It also blocks workflows that point to other workflows used by only one client. Connect those tools MSP-wide, or promote the other workflows first, then try again. If the workflow has scripts that run on their own, only an MSP admin can promote it. If something changes while the preview is open, Rallied shows an updated preview for you to confirm again. You can’t move an MSP-wide workflow back to a single client. Create a new client workflow instead.

Creating a workflow

You need permission to manage workflows. The built-in MSP Admin role has it. MSP Technicians can view workflows but not change them. From the Workflows page, click New workflow. You can describe the workflow in your own words or start from a template. Either way, Rallied creates a draft and opens it in the editor.
The New workflow dialog with a description box and starter templates

Describe it in your own words

Under What should this workflow do?, describe what kind of ticket it’s for and what the agent should do about it. Click Generate workflow. Rallied matches your description to the tools you’ve connected and builds a trigger and steps for you to review in the editor. Examples that work well:
  • “When a new hire starts, create their Microsoft 365 account, assign their license, and add them to the engineering distribution list.”
  • “When a ticket reports a stuck print job, restart the printer’s print spooler service and add an internal note with the result.”
  • “When a security alert ticket comes in about a suspicious sign-in, check the user’s recent sign-in activity, decide whether it’s benign, suspicious, or compromised, and post the verdict as an internal note.”
Press ⌘ / Ctrl + Enter in the description box to generate without clicking.

Start from a template

Under Or pick a template, click a template. Each one comes with a trigger and steps already written, so you get a working draft right away. Templates cover the most common kinds of tickets: Templates work across ConnectWise, HaloPSA, and Autotask. The agent uses whichever ticketing system you’ve connected. If a template needs an integration you haven’t connected yet, it shows a Requires hint, like Requires TimeZest. Connect that integration in Settings → Integrations so the workflow’s tools are available.

If you haven’t connected anything yet

You can’t create a workflow until you connect at least one integration, because the agent needs tools to work with. Click Go to integrations in the dialog. Connect Microsoft 365 to unlock the user-lifecycle templates, or ConnectWise, HaloPSA, or Autotask to unlock the ticket templates.

Editing a workflow

Click any workflow in the list to open the editor. The editor is a split view with chat on the left and the workflow document on the right. On narrow screens, use the Chat and Workflow buttons at the top to switch between the two panes. The chat is the primary way to build or change a workflow. Type what you want in Ask Rallied to change this workflow…, like “add a step that emails the requester when the reset is done.” Rallied updates the draft beside the conversation and marks changed cards as Updated. Review the changes, then save. The right pane shows a map of your workflow:
  • Title: click the Rename pencil next to the name to edit it. New workflows created from a prompt get a generated name based on the workflow’s content, not a copy of your prompt text.
  • Trigger: click the Trigger card and fill in Trigger conditions. Keep it to one line (280 characters at most).
  • Steps: click a step to edit it.

Adding and removing steps

Click Add next step at the bottom of a step list to add a new step. Use the arrows at the top of a step’s inspector panel to reorder it, or the trash icon to remove it.

Adding an If/Else

Click Add If/Else (the icon with a merge symbol) to add a decision point after any step. An If/Else has a plain-English Condition, a YES path, and a NO path. The agent evaluates the condition and follows only the matching path. Each path is its own list of steps that ends the workflow. If neither path matches, the workflow ends. A few things to keep in mind:
  • The condition is a single sentence, 500 characters at most, written the same way you write step instructions.
  • You can nest If/Else steps up to 3 levels deep.
  • Each path can hold up to 100 steps total across the whole workflow.
  • The agent decides which path fits the ticket. Nothing server-side enforces the choice.
  • The workflow grant covers every tool referenced in any path, whichever one runs.
To add a second condition, add another If/Else in the NO path of the first one. To remove an If/Else, select it and click Remove If/Else. Rallied asks whether to keep the YES steps or the NO steps in its place.

Editing a step

Each step has a title, instructions, and tools.
  • Title: a short label, 60 characters at most. Put the detail in the instructions.
  • Instructions: include the action, the evidence to collect, and when the agent should stop.
  • Tools: the actions this step can use from your connected systems.
To add a tool, click Add a tool and search by name or system. A tool marked Always requires approval needs a technician’s sign-off every time, even inside a workflow. A tool marked Disabled by policy is turned off in its approval settings.
The Add a tool search listing matching actions from ConnectWise Manage

Script auto-run

Some steps run a script the agent writes itself. For qualifying tools, you can turn on Run on its own when the script passes review in the step inspector. When it’s on, scripts that pass the safety checks run without waiting for a technician. Anything the checks don’t clear still goes to a technician for approval. Nothing is ever refused. This setting applies to every step in the workflow that uses the same tool. The switch shows an Applies to every step in this workflow that uses this tool note when the tool appears on more than one step. Qualifying tools are script runners where the agent writes the script itself:
  • ConnectWise RMM PowerShell script runner
  • ConnectWise RMM Bash script runner
  • NinjaOne Bash runner
CMD scripts and runners where the language is unknown never qualify for auto-run. Library-script runners (where an admin puts the script in the RMM first) are not affected. The checks run in this order:
  1. Device scope: exactly one target device.
  2. Language: PowerShell or Bash only. CMD escalates to a technician.
  3. Safety screening: the screening looks for credential access, account changes, security control changes, installers, and other high-risk operations. Anything flagged goes to a technician.
  4. Independent review: an isolated reviewer checks whether the script’s effects match what the workflow step describes. The reviewer only sees the workflow text, the effects list, and the script itself. No ticket data reaches it.
You set trusted download sources in Settings → IP restrictions, under Trusted download sources for scripts. Add URLs or UNC paths your scripts need to download from. Only an MSP admin can turn auto-run on or publish workflow text changes while auto-run is active. Anyone can turn it off. Auto-run activity shows in Run history and appears in Activity. For details on the script analysis shown on approvals, see Execute mode.

Saving and turning a workflow on

Edits aren’t saved automatically. Click Save when you’re done.
  • Draft workflow: Save keeps your changes as a draft. Turn on the Active switch to start using it on tickets.
  • Active workflow: Save publishes your changes right away. The agent uses them on the next matching ticket.
You can’t turn on a workflow until it has a trigger and every step has a title and instructions. Steps missing either show a Needs title or Needs instructions pill.
Turning on a workflow pre-approves the tools in its steps that are set to Approval needed. When the agent runs that workflow, those tools run without asking a technician first. Review every step’s tools before you turn a workflow on or save changes to an active one. Tools marked Always requires approval still need sign-off: scripts the agent writes, library script runners and raw GraphQL. See Script auto-run.
If another admin saves the same workflow while you’re editing, Rallied asks whether to load their version or reapply your changes on top of it. Chat is unavailable while you have unsaved inline edits. Save or discard your inline changes first.

Writing a good trigger

  • Start with “when”, and describe the situation, not the action. “When an offboarding request comes in for a departing employee” is better than “Offboard the user”.
  • Name the kind of ticket or signal you’re looking for, like a request, an alert, or a status change.
  • Stick to what kind of ticket this is. Leave the how for the steps.
If you can’t write a clean one-line trigger, the workflow is probably doing two things and should be split.

Workflows created before steps

Rallied converts a workflow written as a single block of instructions into steps the first time you open it. Each numbered line becomes a step. Nothing changes for the agent until you save. If a workflow can’t be converted, the editor shows the original text read-only with the reason, like an integration that isn’t connected or instructions with no numbered steps. To edit it, fix the reason given, like connecting the integration. You can still turn it on or off.

Portal tasks

Teach a task lets the agent do a workflow step in a vendor’s website, like adding a seat, assigning a license, or changing a DNS record in a console with no API. The agent learns the task on the first matching ticket. After that, it repeats the saved steps on later tickets. A step that uses the Do a portal task tool is a portal step. Add the tool with Add a tool, or ask the chat for a step done in the vendor’s portal.

Sign in to the portal

You need to be an MSP admin. Technicians can’t sign in to portals or teach portal steps.
  1. Open the workflow and select the portal step. Its inspector shows a Portal task section marked Not signed in.
  2. Click Sign in to portal.
  3. Enter the address you usually sign in at, starting with https://. Rallied may suggest one from the step’s text.
  4. Sign in through the secure browser. Your password goes to the secure browser, never to Rallied.
The step now shows Waiting for first ticket, and you can publish the workflow. Rallied won’t publish a workflow while a portal step is Not signed in. The Publish switch names the step and the site you still need to sign in to. A client workflow uses a sign-in for that client. A workflow for all clients uses your MSP’s own sign-in, like a partner login with a customer picker.

What happens on the first ticket

On the first matching ticket, the agent works out the steps in the portal itself. Moving around and filling in forms run right away. Each change, like the click that saves a form or removes a user, waits for one technician approval. The approval shows the values being saved. Approving it also lets later runs of this step make that kind of change without asking. When the run finishes, Rallied saves its steps, and the step shows Runs on its own with the ticket it was learned on.

Later tickets

On later matching tickets, the agent repeats the saved steps with no technician approval. A few things to keep in mind:
  • A new kind of change waits for one approval. For example, if the saved steps add a user and a ticket asks to remove one, the removal waits for a technician. Once approved, later runs make that kind of change on their own.
  • Approved kinds belong to one step. The same step in another client’s workflow asks again. So does a step after you edit its instructions: the next matching ticket learns it again.
  • The agent adapts when the page changes. If a saved step no longer matches the page, the agent finishes the task live and saves the adapted steps for later tickets.
  • Extra work follows the same rule. If a ticket asks for more than the saved steps do, the agent does the rest live. The saved steps stay the same.
  • Alert tickets need approval to start. A run on an automated ticket, like an RMM alert, waits for a technician to approve it before it opens.
If a technician denies a change, or nobody approves it within 72 hours, the run stops and leaves a note handing the task to a technician.

Choose where each input comes from

A step with saved steps lists its inputs, like the new hire’s email. Click an input to change its source:
  • From the ticket: the agent reads the value from the ticket. This is the default.
  • Always this value…: every run uses the value you enter.
  • Ask the technician: a technician provides the value.
The change takes effect the next time you save an active workflow.

Show the agent how

If the agent couldn’t finish the task on a ticket, the step says so and offers Show the agent how. Save your edits first.
  1. Click Show the agent how. The editor opens a live browser.
  2. Do the task once in the portal. If you reach a sign-in page, click Sign in securely.
  3. Click Finish teaching. Rallied saves what you did as the step’s saved steps.
Rallied masks password fields while you teach. Teaching ends after 10 minutes without activity, and nothing is kept.

Safeguards on every run

  • The agent stays on the portal’s site. It can’t open addresses outside it.
  • The agent never types into a password field.
  • On a workflow for all clients, the agent selects the ticket’s client by its exact name before it changes anything. If the portal has no exact match, the run stops.
  • A step that changes credentials needs a verified requester when you use identity verification.
  • In Plan Mode, no portal run starts. The agent’s internal note carries the plan.
  • A ticket that needs a portal task no workflow covers gets an internal note asking an admin to set it up.
If a portal sign-in expires, the run pauses. The workflow page shows A portal needs a sign-in. When an admin signs in again, the run continues on its own. A paused run that nobody signs in for ends after 72 hours with a note for the technician.

Following a run

Each ticket with a portal run shows it on the Tickets page. The run lists each step with a screenshot. Click Stop, then Stop the run, to stop it before its next step. Anything it already changed in the portal stays changed. On ConnectWise and HaloPSA tickets, Rallied posts a note when a run starts and when it ends. Each note links to the run’s page in Rallied, with its step log and a video replay. On ConnectWise, the replay is also attached to the ticket as a private document for client workflows, unless the step changes credentials.

Workflow status

Filter the list by status with the All statuses menu.

Seeing which tickets used a workflow

Open the workflow and click the Run history tab. It lists the tickets where the agent ran at least one step of that workflow.
The Run history tab listing tickets, clients, steps run, and outcomes
Each row shows the ticket, the client, how many steps ran, the outcome, and when the workflow last ran on it. The Outcome column counts actions the workflow pre-approved, changes the agent made, and actions that failed. Click a row to open the ticket.

Deleting a workflow

From the list, click the trash icon on the row and click Delete.
Deletion is permanent. If you might want the workflow back later, turn it off instead.

Tips

  • Turn workflows on one at a time. If the agent’s behavior changes, you know which workflow caused it.
  • Watch the first few tickets after activating. Check Run history, then open a few tickets in Activity and skim the agent’s plan. If the trigger caught the wrong tickets, tighten it. If a step got skipped, edit the instructions.
  • Prompts: standing instructions that apply to every ticket.
  • Memory: corrections the agent learned on its own, which often point to a missing workflow.
  • Activity: check what the agent did on the first tickets a workflow matched.
  • Approval settings: which tools need a technician’s sign-off outside a workflow.