Actions20
- Customer Actions
- Whatsapp Web Actions
- Whatsapp Gupshup Actions
Overview
This node integrates with the Cloudia platform to perform various operations related to customers and WhatsApp messaging. Specifically, for the Customer - Unassign User operation, it allows you to unassign a user from a customer by sending a request to the Cloudia API. This can be useful in scenarios where you need to manage customer-user relationships dynamically, such as removing access or reassigning responsibilities within your system.
Practical examples include:
- Automatically unassigning a sales representative from a customer after contract termination.
- Managing customer support assignments by unassigning users when tickets are closed.
- Integrating with CRM workflows to update customer-user mappings programmatically.
Properties
| Name | Meaning |
|---|---|
| Cloudia API Key | The API key used to authenticate requests to the Cloudia platform. |
| Customer ID | The unique identifier of the customer from whom the user will be unassigned. |
| Channel Integration ID | The ID of the channel integration related to the message or operation (context-specific). |
| Name | The name of the customer involved in the operation. |
Note: Although "Channel Integration ID" and "Name" appear in the properties, their exact usage depends on the specific operation implementation. For the "Unassign User" operation, the critical inputs are typically the Customer ID and API key.
Output
The node outputs an array of JSON objects representing the response from the Cloudia API for each input item processed. Each JSON object contains the result of the unassign user operation, which may include status information, confirmation messages, or error details if the operation failed.
If the operation involves binary data (not indicated here), it would be included accordingly, but this node primarily deals with JSON responses.
Dependencies
- Requires a valid Cloudia API key for authentication.
- Depends on the Cloudia REST API endpoint URLs and request body builders defined in the bundled resources.
- No additional external services beyond Cloudia are required.
- The node expects proper configuration of credentials or manual entry of the API key in the input properties.
Troubleshooting
- Common issues:
- Missing or invalid API key leading to authentication errors.
- Incorrect Customer ID causing "not found" or similar errors.
- Unsupported resource or operation errors if parameters are misconfigured.
- Error messages:
"Unsupported resource: ..."indicates the selected resource is not implemented."Unsupported operation: ..."means the chosen operation does not exist for the resource.- API errors returned from Cloudia will be passed through; check the API key validity and input parameters.
- Resolutions:
- Verify the API key is correct and has necessary permissions.
- Confirm that Customer ID and other IDs are accurate and exist in Cloudia.
- Ensure the node parameters match supported resources and operations.
Links and References
- Cloudia API Documentation (replace with actual URL)
- n8n Documentation on Creating Custom Nodes
- General REST API best practices for authentication and error handling.
Note: The above summary is based on static analysis of the provided source code and property definitions without runtime execution.