Actions20
- Customer Actions
- Whatsapp Web Actions
- Whatsapp Gupshup Actions
Overview
The node named "Cloudia" is designed to interact with various resources, including customers and WhatsApp messaging services. Specifically, for the Customer resource with the Remove Tag operation, this node removes a specified tag from a customer record in the Cloudia system.
This functionality is useful in scenarios where you want to dynamically manage customer tags based on events or conditions in your workflow. For example, if a customer no longer qualifies for a certain marketing segment, you can remove the associated tag automatically.
Practical examples:
- Removing a promotional tag from a customer after a campaign ends.
- Cleaning up outdated or incorrect tags from customer profiles.
- Managing customer segmentation by adding/removing tags programmatically.
Properties
Name | Meaning |
---|---|
Cloudia API Key | An API key string used for authentication if not using stored credentials. |
Customer ID | The unique numeric identifier of the customer from whom the tag will be removed. |
Tag ID | The unique numeric identifier of the tag that should be removed from the customer. |
Channel Integration ID | (Not directly relevant for Remove Tag operation on Customer resource) |
Name | (Not directly relevant for Remove Tag operation on Customer resource) |
Note: Only Cloudia API Key, Customer ID, and Tag ID are relevant for the "Remove Tag" operation on the Customer resource.
Output
The node outputs an array of JSON objects representing the response from the Cloudia API for each input item processed. Each object contains the result of the tag removal request, typically confirming success or providing error details.
If the operation fails for any item and the node is configured to continue on failure, the output for that item will include an error
field with the error message.
No binary data output is produced by this node.
Dependencies
- Requires access to the Cloudia API endpoint.
- Needs an API key credential or manual API key input for authentication.
- No additional external dependencies beyond standard HTTP requests.
Troubleshooting
Common issues:
- Invalid or missing API key: Ensure the API key is correctly provided either via credentials or the input property.
- Incorrect Customer ID or Tag ID: Verify that the IDs exist and are valid in the Cloudia system.
- Unsupported resource or operation errors: Confirm that the resource is set to "Customer" and operation to "Remove Tag".
Error messages:
"Unsupported resource: ..."
: Occurs if the resource parameter is not recognized; fix by selecting a valid resource."Unsupported operation: ..."
: Happens if the operation is invalid for the selected resource; choose a supported operation.- API request errors returned from Cloudia will be included in the output's error field if "Continue On Fail" is enabled.
Links and References
- Cloudia API documentation (refer to your Cloudia provider's official docs for detailed API usage)
- n8n documentation on creating custom nodes and handling API requests