Overview
This node acts as a trigger for Arivo CRM events, starting an n8n workflow whenever specific events occur in the Arivo CRM system. It listens to various entity lifecycle events such as creation, update, deletion, and status changes across multiple resource types like companies, deals, notes, persons, tasks, and custom records.
Common scenarios where this node is beneficial include:
- Automating follow-up actions when a new deal is won or lost.
- Syncing contact or company updates with other systems.
- Triggering notifications or logging when tasks are completed or updated.
- Reacting to changes in custom records defined within Arivo CRM.
For example, you could use this node to start a workflow that sends a welcome email when a new person (contact) is created, or to update an external database when a deal is marked as won.
Properties
| Name | Meaning |
|---|---|
| Event | The specific Arivo CRM event to listen for. Options include: - Company Created, Deleted, Updated - Custom Record Created, Deleted, Updated - Deal Created, Deleted, Lost, Reopened, Updated, Won - Note Created, Deleted, Updated - Person Created, Deleted, Updated - Task Created, Deleted, Done, Updated, Updated to Not Done |
| Custom Record Definition Name or ID | When listening to custom record events (created, updated, deleted), select the specific custom record definition by name or ID. This property appears only if a custom record event is selected. You can choose from a list loaded dynamically or specify an ID via expression. |
Output
The node outputs JSON data representing the event payload received from Arivo CRM. Each execution returns an array with one item containing the webhook event data under the json field.
The structure of the JSON depends on the event type but generally includes details about the affected entity and the nature of the event.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication token credential for Arivo CRM to register and manage webhooks.
- Uses Arivo CRM's webhook API endpoints to create, check, and delete webhooks corresponding to the selected event.
- The node dynamically loads available custom record definitions from Arivo CRM to populate options when subscribing to custom record events.
Troubleshooting
- Webhook registration failure: If the node cannot create or find the webhook on Arivo CRM, ensure the provided API credentials have sufficient permissions and that the webhook URL is accessible externally.
- Missing custom record definition: When selecting custom record events, if no definitions appear or an error occurs, verify that the API credentials allow fetching custom record definitions and that the specified ID is valid.
- Unsupported custom record action error: This error occurs if the event string for custom records does not match expected patterns (
created,updated,deleted). Ensure the event property is correctly set. - Event payload issues: If the workflow does not trigger as expected, confirm that the Arivo CRM instance is sending events to the correct webhook URL configured by the node.
Links and References
- Arivo CRM API Documentation (hypothetical link for reference)
- n8n Expressions Documentation
- n8n Webhook Node Documentation