Actions11
- Deals Actions
- Contact Actions
- Emails Actions
- Organization Actions
- To-Dos Actions
Overview
This node integrates with the GrandCentral API to perform various automation actions. Specifically, for the Organization resource and the Remove Organization Tag operation, it removes a specified tag from an organization. This can be useful in scenarios where you want to dynamically manage organization tags based on workflow conditions, such as cleaning up outdated tags or managing segmentation.
For example, if an organization no longer fits a certain category or campaign, this node can remove the associated tag automatically, helping keep your data organized and relevant.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; currently supports "Access Token" |
| Organization | The identifier (ID or unique string) of the organization from which to remove the tag |
| Tag | The specific tag to remove from the organization |
| Untag All Contacts | Boolean flag indicating whether to also remove this tag from all contacts under the organization (optional) |
Output
The node outputs JSON data representing the response from the GrandCentral API after attempting to remove the tag. The output is an array of objects containing details about the action performed. Each item corresponds to one input item processed.
No binary data output is produced by this node.
Dependencies
- Requires access to the GrandCentral API.
- Requires an API key credential configured in n8n for authentication.
- The node makes a POST request to the
/automations/actionendpoint of the GrandCentral API with parameters specifying the operation and its inputs.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an incorrect organization ID or tag name may result in errors or no changes.
- Network connectivity issues can prevent the API call from succeeding.
Error messages:
- Authentication errors typically indicate invalid or expired tokens; verify and update your API key.
- Validation errors may occur if required parameters like organization or tag are missing or malformed.
- API rate limits or server errors will return corresponding HTTP error codes; retry after some time or check API status.
Links and References
- GrandCentral API Documentation (replace with actual URL if available)
- n8n documentation on Creating Custom Nodes