Overview
This node acts as a trigger for various GrandCentral events by handling incoming webhook notifications. It listens for specific event types configured by the user and activates workflows when those events occur in the connected GrandCentral system.
Common scenarios where this node is beneficial include automating processes based on business activities such as invoice creation, contact updates, deal progress, project milestones, proposal status changes, subscription events, support ticket updates, and user management actions. For example, you could use it to automatically send follow-up emails when a proposal is accepted or update CRM records when a deal stage changes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with the GrandCentral API. Currently supports only "Access Token" authentication. |
| Events | The list of GrandCentral event types to listen for via webhook. Multiple events can be selected. Examples include: Invoice Created, Contact Deleted, Deal Stage Changes, Project Completed, Proposal Sent, Subscription Cancelled, Ticket New Message, User Role Updates, etc. |
Output
The node outputs JSON data representing the payload received from the GrandCentral webhook for the triggered event(s). This JSON contains all relevant information about the event that occurred, allowing subsequent workflow nodes to process or act upon it.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the GrandCentral API using an access token credential.
- Needs proper configuration of webhooks on the GrandCentral side to send event notifications to the URL provided by this node.
- The node uses internal helper functions to make authenticated HTTP requests to the GrandCentral API for webhook management (creation, checking existence, deletion).
Troubleshooting
- Webhook Not Triggering: Ensure the webhook URL generated by the node is correctly registered in the GrandCentral system and that the selected events are enabled.
- Authentication Errors: Verify that the access token provided is valid and has sufficient permissions to manage webhooks and receive event data.
- Webhook Creation Fails: Check network connectivity and API limits; also confirm that no conflicting webhook exists for the same URL.
- Unexpected Payloads: Confirm that the events selected match the expected data structure and that the GrandCentral system is sending data in the correct format.
Links and References
- GrandCentral API documentation (for webhook and event details) — typically available from the service provider's developer portal.
- n8n Webhook Node documentation for general webhook setup and troubleshooting guidance.