GateKit

Universal messaging gateway - send messages across multiple platforms

Actions26

Members Actions
Projects Actions
- Create
- Update
Platforms Actions
Messages Actions
- List
- Stats
- Get
- Cleanup
- Send
- Status
- Retry
- Sent
ApiKeys Actions
Platform Logs Actions
- Logs

Overview

The "Send" operation of the "Messages" resource in this node allows users to send messages across multiple messaging platforms through a unified gateway. This node is useful for scenarios where you want to programmatically deliver messages to one or more recipients on different platforms (e.g., Telegram, Discord, WhatsApp) without dealing with each platform's API separately.

Practical examples include:

Sending notifications or alerts to specific users or groups on various chat platforms.
Broadcasting announcements to multiple targets simultaneously.
Delivering customized message content with advanced options and metadata for richer communication.

Properties

Name	Meaning
target	Single recipient target specified as `platformId:type:id` (e.g., telegram:user:12345).
targets	Multiple recipient targets separated by commas, each in the format `platformId:type:id`.
text	The plain text content of the message to be sent.
content	Full message content as a JSON object for advanced usage, allowing rich message structures.
options	JSON object specifying additional message options (e.g., formatting, delivery preferences).
metadata	JSON object containing metadata related to the message, such as tags or custom attributes.
projectSlug	Identifier of the project under which the message is sent; required to specify the context.

Output

The output of this operation contains a JSON object representing the response from the messaging gateway API after sending the message(s). This typically includes details such as message IDs, status, timestamps, and any errors if occurred.

If the node supports binary data output (not indicated here), it would represent attachments or media sent along with the message, but this operation focuses on JSON message content.

Dependencies

Requires an API key credential for authenticating with the GateKit messaging gateway service.
Needs the base URL of the API configured via credentials.
The project slug must correspond to an existing project configured in the GateKit system.
The node relies on the GateKit API endpoints to send messages.

Troubleshooting

Missing or invalid projectSlug: Ensure the project identifier is correct and exists in the GateKit system.
Invalid target format: Targets must follow the platformId:type:id format exactly; otherwise, the API may reject the request.
Empty message content: Either text or content should be provided; sending empty messages will likely cause errors.
API authentication errors: Verify that the API key credential is valid and has permissions to send messages.
Rate limits or platform restrictions: Some platforms may impose rate limits or require special permissions; check platform-specific logs or documentation.
Malformed JSON in content/options/metadata: Ensure these fields contain valid JSON objects to avoid request failures.

Links and References

GateKit API Documentation (hypothetical link)
Messaging platform integration guides (Telegram, Discord, WhatsApp) within GateKit docs
n8n documentation on using HTTP Request nodes and credentials for API integrations