Autotask Trigger

Handle Autotask Webhook events

Overview

The Autotask Trigger node listens for webhook events from the Autotask platform, allowing n8n workflows to be triggered by changes in Autotask entities such as Companies, Contacts, Tickets, Configuration Items, and Ticket Notes. It supports granular event filtering (create, update, delete), field-level subscriptions, and resource exclusions. This node is ideal for automating processes based on real-time updates in your Autotask account, such as syncing contacts, updating tickets, or reacting to configuration item changes.

Practical examples:

Start a workflow when a new ticket is created in Autotask.
Update a CRM record when a company is updated in Autotask.
Send notifications when specific fields of a contact are changed.
Exclude certain resources from triggering workflows.

Properties

Name	Type	Meaning
Entity Type	options	The type of Autotask entity to trigger on (e.g., Companies, Contacts, Tickets, etc.). Determines which entity's events will be monitored.
Event Types	multiOptions	The event types to trigger on. Options: Create, Update, Delete. At least one must be selected.
Send Threshold Notifications	boolean	Whether to receive notifications if webhook requests exceed the hourly threshold and when they return to normal.
Notification Email Address	string	Email address to receive notifications about webhook delivery failures and threshold alerts. Required if "Send Threshold Notifications" is enabled.
Subscribed Field Names or IDs	multiOptions	Fields to subscribe to for receiving updates. Only changes to these fields will trigger the workflow. Required.
Always Display Field Names or IDs	multiOptions	Fields to always include in webhook payloads, regardless of whether they changed. Required.
Excluded Resources Names or IDs	multiOptions	List of resources (by name or ID) to exclude from triggering the workflow.

Output

The node outputs a single JSON object per webhook event with the following structure:

{
  "headers": { /* HTTP headers received from Autotask */ },
  "body": { /* Raw webhook body from Autotask */ },
  "mappedBody": {
    "eventType": "Create|Update|Delete|Deactivated",
    "entityType": "Companies|Contacts|Tickets|ConfigurationItems|TicketNotes",
    "entityId": "string|number",
    "entityData": { /* Changed fields and their values */ },
    "timestamp": "ISO8601 string",
    "webhookId": 0
  },
  "entityType": "Companies|Contacts|Tickets|ConfigurationItems|TicketNotes",
  "normalizedEntityType": "companies|contacts|tickets|configurationitems|ticketnotes",
  "originalEntityType": "Account|Contact|Ticket|ConfigurationItem|TicketNote",
  "eventType": "Create|Update|Delete|Deactivated",
  "entityId": "string|number",
  "entityData": { /* Changed fields and their values */ },
  "timestamp": "ISO8601 string",
  "webhookId": 0,
  "guid": "string",                // Unique identifier for the event
  "sequenceNumber": "number",      // Sequence number of the event (if provided)
  "personId": "string|number"      // Person ID related to the event (if provided)
}

For deactivation events, the output includes deactivated: true and omits most other fields.

Dependencies

External Service: Requires an active Autotask account with API access.
API Credentials: You must configure the autotaskApi credential in n8n.
Environment: No special environment variables required beyond standard n8n setup.

Troubleshooting

Common Issues:

Invalid Content Type:
- Error: "Invalid content type. Expected application/json."
  Resolution: Ensure that Autotask is sending webhooks with the correct content type.
Entity Type Mismatch:
- Error: "Invalid entity type. Received X, expected Y."
  Resolution: Double-check that the node's "Entity Type" matches the entity configured in Autotask.
Event Type Mismatch:
- Error: "Invalid event type. Received X, expected one of: ..."
  Resolution: Make sure the "Event Types" property includes all relevant event types.
Missing or Invalid Webhook Signature:
- Error: "Invalid webhook signature" or "Missing webhook signature"
  Resolution: Ensure the secret key is correctly set up and that Autotask is signing webhook requests.
No Fields Selected:
- Error: "At least one field must be selected in Subscribed Field Names or IDs."
  Resolution: Select at least one field in the "Subscribed Field Names or IDs" property.
Webhook Creation/Deletion Fails:
- Errors during webhook creation or deletion may indicate permission issues or misconfiguration in Autotask.