Skip to main content
Studio has two built-in AI helpers for organisation admins: Aimbot in the top bar, for questions and actions across your organisation, and an Assistant tab in the workflow and form designers, for building what’s open.

AI in Studio: a question about a client, a run that waits for permission, an automation built in chat and edited with the Assistant tab (1:27).

​
Aimbot

Click Aimbot in the top bar, then type a question or pick a suggestion.
The Aimbot page with a New chat button, a Search chats box and a list of earlier chats, and a new chat reading What can I help with? with suggestions What integrations does a client have?, List my clients and Check agent status for a client, Ask and All clients pills, and a Message the assistant box.
Aimbot has the MCP server’s tools, apart from Triggr Core settings and PowerShell script editing, so it reads your clients, workflows, runs, forms, approvals and agent status, and fetches live data through your integrations. It can also:
  • Build automations. Describe one and Aimbot saves it as an Inactive workflow. Click Open in designer to check it, then Activate.
    An Automation card for Docs sample – Aimbot disk alert with Activate and Open in designer buttons.
  • Open a form for you. Ask for one of your forms and fill it in inside the chat; Aimbot never sees your answers. Forms that need a password, Microsoft or Google sign-in open in their own page.
  • Run things. Start workflows, approve your approvals and set client variables, once you allow it.

​
Choose what it may do without asking

The pill at the top right of a chat sets the permission mode.
The Permission mode menu with Ask everything ticked, Auto-approve fetches and Allow all, each with a description, next to an All clients pill.
Anything else shows a Permission needed card: click Allow once, Allow all in this chat (which switches the chat to Allow all) or Deny. Aimbot doesn’t retry a denied action another way.
A chat asking Aimbot to run the Docs sample – compliance log workflow with three parameters, and a Permission needed card for Trigger workflow · Docs sample – compliance log with Allow once, Allow all in this chat and Deny buttons.
To keep a chat to one client, click All clients and pick the client before you ask. Chats are private to you.

​
Prompts that work well

Which integrations does Acme Corp have, and is its desktop agent online?
Which workflow runs failed in the last 7 days? Group them by workflow and show the failing step and error for the top three.
Build an automation called “Disk space alert”. A webhook receives an RMM alert with device, alertType and siteId. Email helpdesk@example.com with the device and alert type, then finish.
Open the leaver request form for Globex.

​
The Assistant tab in the workflow designer

Open a workflow, click Assistant next to Components and describe what it should do or what to change; it builds the trigger, branches and steps on the canvas.
The workflow designer with the Assistant tab open: a prompt describing a HaloPSA ticket workflow, a list of completed Reading the step actions, and the resulting canvas with Hawk Ticket Trigger, Find Client by haloId, Client Found?, Set Client, Finish – No Client Match and Email Helpdesk steps.
The Assistant saves the workflow at the end of each reply, including edits you hadn’t saved, and leaves it Active or Inactive as it was, so an Active workflow runs the new version on its next trigger. Work on an Inactive workflow or a duplicate.
Check each step it added, then test with Manual Trigger before you activate. Be specific about the trigger, the data and the outcome:
When the “New starter request” form is submitted, create a HaloPSA ticket for the client with the starter’s name and start date, then email helpdesk@example.com.

​
The Assistant tab in the form designer

Open a form and click Assistant next to Fields. Describe the sections and fields you need and it puts them on the canvas; nothing is saved until you click Save.
The form designer with the Assistant tab open, a prompt asking for a new starter request form, the Assistant's summary of the fields it built, the New Starter section on the canvas with First Name, Last Name, Start Date, Job Title and Department, and the Form Structure panel listing the New Starter and Access sections.

​
Aimbot or your own AI tool?

​
FAQ

Both are for organisation admins. In the workflow designer, the tab is also hidden when you can’t edit the workflow.
Refresh the page and try again. If it persists, contact Triggr support.
Inactive stops form and schedule triggers, but a Webhook trigger, a Hawk watcher or another workflow can still start it. See Triggers.
The Assistant has already saved it. Clicking Save saves the same version again.
Each Assistant tab conversation also appears in Aimbot’s chat list, named Workflow assistant, Form assistant or Deck assistant.
No. Integration tools return details about the connection, not its saved credentials.