How to connect
Autotask uses API user credentials plus an API tracking identifier. Rallied detects your datacenter zone from the username.1
Create an API user in Autotask
In Autotask, go to Admin → Resources/Users → API Users → New. Set Security Level to API User (system), generate a Secret, and assign an API Tracking Identifier (a 26-character code). Note the username, secret and tracking identifier. Autotask shows the secret only once.
2
Open the Autotask card
In Rallied, go to Settings → Integrations, find the Autotask card, and click Connect.
3
Enter your credentials
Click Connect. Rallied finds your Autotask zone and validates the credentials.
4
Select company types to import
The Select company types to import step opens. Pick the Autotask company types, such as Customer or Lead, to import as Rallied clients. Each new client gets an agent automatically.
5
Copy the webhook details
Autotask doesn’t support webhook registration through its API for every entity. Rallied generates a webhook URL and shared secret on the Autotask integration detail page. Copy both.
6
Add the webhook in Autotask
In Autotask, go to Admin → Extensions & Integrations → Outbound Integrations. Add the webhook URL and secret for the Ticket and TicketNote entities.
7
Confirm the connection
Autotask sends a readiness GET ping. The card shows Connected once Rallied receives it.
What happens when a ticket comes in
When a new ticket or note lands in Autotask, the agent picks it up right away, matches it to the right client, and starts working. 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.Approving an action without leaving Autotask
When the agent’s plan needs a technician’s sign-off, it posts an internal note on the ticket with approve and deny links. Your team approves or denies from Autotask. Only the ticket’s assigned resource can approve. Rallied treats replies from anyone else as normal messages, so they don’t affect the approval.What the agent can do in Autotask
Each action below appears by name on the Autotask Policies tab, where you can change its default.
No Autotask action sets a ticket’s resolution field.
When the built-in actions don’t cover something, the agent can reach any Autotask endpoint through fallback API requests. GET requests run automatically. POST and PATCH requests, including POST searches, need approval.
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
- Integrations to update credentials or disconnect Autotask