Actions11
- Deals Actions
- Contact Actions
- Emails Actions
- Organization Actions
- To-Dos Actions
Overview
This node integrates with the GrandCentral API to perform various automated actions on different resources such as contacts, deals, emails, organizations, and to-dos. Specifically, for the Contact resource and the Tag Contact operation, it allows you to add a tag to a specified contact within your GrandCentral system.
This functionality is useful in scenarios where you want to categorize or label contacts automatically based on certain triggers or workflows. For example, tagging a contact as "VIP" after a purchase or marking them as "Newsletter Subscriber" when they sign up.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; currently supports "Access Token" |
| Contact | The unique identifier (string) of the contact to which the tag will be added |
| Tag | The tag (string) that will be added to the specified contact |
Output
The node outputs JSON data representing the response from the GrandCentral API after attempting to tag the contact. This output typically includes details about the success or failure of the tagging action and any relevant metadata returned by the API.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the GrandCentral API.
- Requires an API key or access token credential configured in n8n for authentication.
- The node sends a POST request to the
/automations/actionendpoint of the GrandCentral API with the operation and parameters.
Troubleshooting
Common issues:
- Invalid or expired access token may cause authentication failures.
- Incorrect contact ID or tag name might result in errors or no changes.
- Network connectivity issues can prevent the API call from succeeding.
Error messages:
- Authentication errors usually indicate problems with the provided API key/token; verify and update credentials.
- Validation errors from the API may indicate missing or malformed parameters; ensure the contact ID and tag are correctly specified.
- General API errors should be checked against GrandCentral API documentation for specific error codes and messages.
Links and References
- GrandCentral API Documentation (replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes