Actions11
- Contact Actions
- Deals Actions
- Emails Actions
- Organization Actions
- To-Dos Actions
Advanced
AI-generatedOverview
This node integrates with the GrandCentral API to perform various automated actions across multiple resource types such as contacts, deals, emails, organizations, to-dos, and advanced custom operations. It is designed to trigger specific operations by sending requests to the GrandCentral automation endpoint.
Common scenarios include:
- Adding notes or tags to contacts.
- Managing deal statuses, owners, and stages.
- Sending emails.
- Tagging or untagging organizations.
- Creating and managing to-do tasks.
For example, a user could automate adding a note to a contact when a certain event occurs or automatically move a deal to a new stage based on workflow triggers.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; currently supports "Access Token" only. |
Since the request payload is constructed from all node parameters, the actual operation and resource are fixed in the node configuration and not exposed as input properties here.
Output
The node outputs an array of JSON objects representing the response from the GrandCentral API after performing the requested automation action. Each item corresponds to one input item processed.
- The
jsonoutput contains the API response data for the executed operation. - No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the GrandCentral API.
- Uses the internal helper function
gcApiRequestto send POST requests to/automations/action. - No additional external dependencies beyond the configured API access.
Troubleshooting
- Authentication errors: Ensure the provided access token is valid and has sufficient permissions.
- Invalid operation or parameters: The node sends all parameters as-is; incorrect or missing required fields for the selected operation may cause API errors.
- API connectivity issues: Network problems or incorrect API endpoint configuration can lead to request failures.
- Empty or unexpected responses: Verify that the operation and resource combination is supported and that input parameters are correctly set.
Links and References
- GrandCentral API documentation (not provided in source; consult official GrandCentral resources)
- n8n documentation on creating custom nodes and using credentials