Create the API agent in HaloPSA
1
Sign in to HaloPSA as an administrator
Use an account with Administrator rights.
2
Open the Agents list
Go to Configuration → Teams & Agents → Agents and click New.
3
Configure the new agent
Fill in these fields and leave the rest at their defaults.
4
Save the agent
Click Save.
Register the Application
Rallied calls the HaloPSA API through the Application.1
Open the Applications list
Go to Configuration → Integrations → HaloPSA API → Applications → View Applications and click New.
2
Configure the application
HaloPSA generates a Client ID and Client Secret. Copy both for the Rallied connect form. The secret is shown only once.

3
Set the application permissions
On the Permissions tab, enable the three scopes Rallied needs:
Leave
all and admin unchecked. all:standard, all:teams and admin:webhooks are the least-privileged set that lets the integration work.
4
Save the application
Click Save. Leave the page open. You still need the Client ID and Client Secret.
Connect HaloPSA in Rallied
1
Open the HaloPSA card
In Rallied, go to Settings → Integrations, find the HaloPSA card, and click Connect.
2
Enter your HaloPSA details
Click Connect. Rallied validates the connection. If the credentials are wrong, an inline error appears. Check the values and try again.

3
Select clients to import
The Select clients to import step opens. Pick the HaloPSA clients you want to manage with Rallied. Rallied imports each one with its own agent.
What happens when a ticket comes in
When a new or updated ticket lands in HaloPSA, the agent picks it up right away and matches it to the right client. It starts with the full ticket context, including subject, requester, priority, prior notes and attached files. If a workflow matches the ticket, the agent follows it. For sensitive requests such as password or MFA resets, the agent can verify the requester’s identity first. It posts the outcome as an internal note.Attachments
The agent can read ticket attachments, including files in S3-linked storage. It reads plain text, PDFs with a text layer, Word documents and email messages. The agent never pastes a signed storage link as text.Approving an action without leaving HaloPSA
When the agent’s plan needs a technician’s sign-off, it creates a HaloPSA action on the ticket describing what it wants to do. Your team approves or denies from HaloPSA. You choose which actions need approval on the HaloPSA Policies tab under Settings → Integrations. Only the ticket’s assigned agent can approve. Rallied treats replies from anyone else as normal messages. They don’t affect the approval.Mapping agent events to Halo actions and statuses
By default, the agent posts its notes with no specific Halo Action outcome and leaves the ticket status alone. Many MSPs drive Halo automations, SLA timers and reports from specific Actions and statuses. Use the Halo actions & statuses table to post each agent event as the Action your workflow expects. You can also move the ticket to a status at the same time. Open the HaloPSA integration page under Settings → Integrations. The table has one row per agent event and two columns:- Logged as (action): the Halo Action outcome the agent posts the note as.
- Moves ticket to (status): the status the same Action moves the ticket to.
1
Pick an action and status for each event
Leave a cell on Default (none) or Don’t change to keep the default behavior for that event. Rows that inherit from the internal note show Same as internal note instead.
2
Create a missing status if needed
Select + Create a new status in Halo… in a status cell, enter a name, and select Create. If a saved status no longer exists in HaloPSA, the table shows a warning with a Create it in Halo button.
3
Save the mapping
Select Save. Rallied applies the mapping to the next event on any ticket.
Rallied Agent account. Steps that run after an approval include “Approved by” and the technician’s name in the Action.
If your HaloPSA instance or its API agent can’t create statuses over the API, add the status in HaloPSA under Configuration → Tickets → Statuses, then select it in the table.
Replying to the agent on a ticket
Once the agent has started a ticket, Rallied forwards each new note on it to the same session. That includes internal notes from technicians and customer replies from end users. A tech can add a hint mid-investigation, or an end user can answer a question, and the agent continues where it left off. You don’t need to re-trigger it. If notes arrive while the agent is still working on its current turn, Rallied holds them. When the turn ends, Rallied sends them to the agent together as one message. Rallied labels each forwarded note as an internal note or a customer reply. Rallied never forwards these:- The agent’s own notes. Only notes from an identified human author reach the agent.
- Replies on tickets the agent never worked. A comment on an old ticket doesn’t wake an agent.
Testing the end-to-end setup
1
Create a test ticket in HaloPSA
Click New Ticket at the top of any HaloPSA page. Pick any ticket type, assign it to an imported client, and fill in a short subject and description.
2
Confirm the webhook fired
Go to Configuration → Integrations → Webhooks, open the
Rallied (...) webhook, and check the Deliveries tab. It shows a successful delivery for the new ticket.3
Confirm the agent picked it up
In Rallied, open Settings → Activity or the client’s Activity tab. The new ticket appears with the agent’s diagnosis in progress. In Plan mode, the agent posts an internal note with its plan. In Execute mode, it runs the actions set to Auto and requests approval for the rest.
- The Instance URL has no trailing slash and uses HTTPS.
- The Client Secret hasn’t been regenerated since you saved it in Rallied.
- The client on the test ticket was imported when you connected.
Related
- Approval settings for how Auto, Approval needed and Disabled work
- Identity verification for the MFA check before sensitive actions
- Workflows to tell the agent how to handle common tickets
- Activity to follow what the agent did on each ticket