Actions52
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
- Platforms Actions
- Projects Actions
- Webhooks Actions
Overview
The node provides a universal messaging gateway that allows sending messages across multiple platforms within a specified project. It supports sending messages to single or multiple targets, with flexible content and options. This node is beneficial in scenarios where you want to automate communication across different messaging platforms (e.g., Telegram, Discord, WhatsApp) from a single interface.
Practical examples include:
- Sending notifications to users on various platforms simultaneously.
- Broadcasting announcements to multiple recipients identified by platform-specific IDs.
- Sending complex message content with metadata and custom options for advanced use cases.
Properties
| Name | Meaning |
|---|---|
| target | Single target identifier in the format platformId:type:id to send the message to. |
| targets | Multiple targets as a comma-separated list of platformId:type:id identifiers. |
| text | Text content of the message to be sent. |
| content | Full message content object in JSON format for advanced message structures. |
| options | JSON object specifying additional message options (e.g., formatting, delivery preferences). |
| metadata | JSON object containing metadata related to the message. |
| project | Identifier of the project under which the message will be sent. This is required. |
Output
The output contains the response from the messaging API after attempting to send the message(s). The main data is available in the json field, which typically includes details about the message job such as status, message IDs, or error information if the send operation failed.
If the node supports binary data output (not explicitly shown here), it would represent any media or attachments sent with the message, but this node primarily deals with JSON message content.
Dependencies
- Requires an API key credential for authentication to the messaging service.
- Needs the base URL of the messaging API configured in the credentials.
- The project identifier must correspond to an existing project in the messaging platform backend.
Troubleshooting
- Missing or invalid API key: Ensure the API key credential is correctly set up and has permissions to send messages.
- Invalid target format: Targets must follow the
platformId:type:idformat; incorrect formatting will cause errors. - Empty message content: Either
textorcontentshould be provided; sending empty messages may result in failure. - Project not found: Verify the project identifier exists and is accessible with your credentials.
- API errors: Check the returned error messages for rate limits, permission issues, or malformed requests.
Links and References
- Refer to the messaging platform's official API documentation for detailed message content structure and platform-specific requirements.
- Consult n8n documentation on how to configure API key credentials and use HTTP request nodes for similar integrations.