Autotask Trigger

Handle Autotask Webhook events

Overview

This node listens for webhook events from Autotask related to various entity types such as Companies, Contacts, Tickets, Ticket Notes, and Configuration Items. It triggers workflows when specified event types (create, update, delete) occur on the selected entity type. The node supports fine-grained control over which fields to subscribe to and always include in webhook payloads, and allows excluding certain resources from triggering. It also manages webhook lifecycle including creation, existence check, and deletion, and verifies webhook signatures for security. This node is useful for automating processes based on real-time changes in Autotask entities, such as syncing data, alerting, or updating other systems.

Properties

Name	Meaning
Entity Type	The type of Autotask entity to listen for webhook events on. Options include Companies, Configuration Items, Contacts, Ticket Notes, and Tickets.
Event Types	The types of events to trigger on for the selected entity type. Users must select at least one event type.
Send Threshold Notifications	Whether to receive email notifications if webhook requests exceed the hourly threshold or when they return to normal.
Notification Email Address	Email address to receive notifications about webhook delivery failures and threshold alerts. Required if threshold notifications are enabled.
Subscribed Field Names or IDs	Fields to subscribe to for receiving updates. At least one field must be selected. Fields can be chosen from a list or specified by IDs using expressions.
Always Display Field Names or IDs	Fields to always include in webhook payloads regardless of subscription. Can be selected from a list or specified by IDs using expressions.
Excluded Resources Names or IDs	Resources to exclude from triggering the webhook. Can be selected from a list or specified by IDs using expressions.

Output

JSON

headers - HTTP headers received with the webhook request.
body - Raw webhook payload body from Autotask.
mappedBody
- eventType - Type of event received (create, update, delete, deactivated).
- entityType - Entity type of the webhook event.
- entityId - ID of the entity involved in the event.
- entityData - Data fields of the entity included in the webhook payload.
- timestamp - Timestamp of when the event occurred.
webhookId - ID of the webhook in Autotask.
guid - Unique identifier for the webhook event.
sequenceNumber - Sequence number of the webhook event.
personId - ID of the person associated with the event, if applicable.
deactivated - Boolean indicating if the webhook event is a deactivation event.
entityType - Normalized entity type string (lowercase).
originalEntityType - Original entity type string as received.

Dependencies

Requires an Autotask API key credential for authentication.
Uses Autotask REST API endpoints to create, check, and delete webhooks.
Relies on cryptographic verification of webhook signatures using a secret key.

Troubleshooting

Error: 'At least one event type must be selected.' - Ensure you select one or more event types in the node settings.
Error: 'At least one field must be selected in Subscribed Field Names or IDs.' - Select at least one field to subscribe to for updates.
Error: 'Invalid content type. Expected application/json.' - The webhook request did not have the expected JSON content type header.
Error: 'Invalid webhook signature' or 'Missing webhook signature' - The webhook request signature verification failed or was missing. Check that the secret key matches and that Autotask is sending the signature header.
Webhook not found errors during deletion (404 or 500 with 'No matching records found') indicate the webhook may have been deleted already; these can be safely ignored.
High Autotask API usage warnings indicate nearing API rate limits; consider reducing webhook setup calls or adjusting usage.
If threshold notifications are enabled but no notification email is provided, notifications will be disabled and a warning logged.