Cloudia

Overview

This node, named "Cloudia," is designed to send messages through different messaging resources. It supports multiple messaging platforms or services, including a generic "Customer" resource and two WhatsApp integrations ("Whatsapp Web" and "Whatsapp Gupshup"). The node allows users to select the resource and operation they want to perform, then constructs and sends the appropriate API request to deliver messages.

Common scenarios for this node include:

• Sending personalized messages to customers via a custom customer messaging system.
• Sending WhatsApp messages using either a web-based WhatsApp integration or the Gupshup WhatsApp API.
• Automating message delivery workflows where different messaging channels are used depending on the context.

Practical example:

• A user wants to send a welcome message to a new customer by specifying their name and channel integration ID.
• Another use case could be sending templated WhatsApp notifications to users via the Gupshup platform.

Properties

Name	Meaning
Channel Integration ID	The numeric ID of the channel integration to which the message will be sent (e.g., 123).
Name	The name of the customer to whom the message will be sent (e.g., "Felipe Miranda").

Note: These properties correspond to the "Default" Resource and Operation as requested. The node also supports other resources and operations with additional properties not listed here.

Output

The node outputs an array of JSON objects, each representing the response from the messaging API for each input item processed. Each JSON object contains the result of the message sending operation, such as success confirmation or error details.

If the node encounters errors during execution and "Continue On Fail" is enabled, it outputs an error object with an error field describing the issue for that particular item.

The node does not output binary data.

Dependencies

• Requires an API key credential for authentication with the Cloudia service or the respective messaging platform APIs.
• Uses internal helper functions to build request bodies and URLs based on the selected resource and operation.
• No external environment variables are explicitly required beyond the API key credential.

Troubleshooting

• Unsupported resource or operation errors: If you select a resource or operation not supported by the node, it will throw an error indicating the unsupported choice. Ensure you select valid combinations.
• API request failures: Errors returned from the messaging API (e.g., invalid API key, incorrect parameters) will cause the node to fail unless "Continue On Fail" is enabled.
• Missing required properties: Make sure to provide all required input properties such as "Channel Integration ID" and "Name" to avoid validation errors.
• Credential issues: Verify that the API key credential is correctly configured and has the necessary permissions.

Links and References

• No direct external links are provided in the source code.
• For more information about the messaging platforms (WhatsApp Gupshup, WhatsApp Web), consult their official documentation.
• Refer to n8n documentation on creating and configuring credentials for API authentication.