GateKit icon

GateKit

Universal messaging gateway - send messages across multiple platforms

Actions51

Overview

This node interacts with a universal messaging gateway API to check the delivery status of a message job. Specifically, the Messages: Status operation allows users to query the current status of a message sending job by providing its unique job ID within a specified project.

This is useful in scenarios where you have sent messages across multiple platforms (e.g., Telegram, Discord, WhatsApp) and want to programmatically verify if the message was delivered, is still pending, or failed. For example, after triggering a message send operation, you can use this node to poll for the delivery status and take further actions such as logging, alerting, or retrying failed messages.

Properties

Name Meaning
Message job ID The unique identifier of the message job whose delivery status you want to check.
Project The project identifier under which the message job was created; used to scope the request.
JobId Alias for the message job ID parameter (same as "Message job ID").

Note: The properties "Message job ID" and "JobId" represent the same required input — the job ID string.

Output

The output JSON contains the response from the messaging gateway API about the status of the specified message job. This typically includes fields indicating whether the message job is pending, completed successfully, or failed, along with any relevant metadata or error details.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests against the messaging gateway API.
  • The node sends HTTP GET requests to the endpoint /api/v1/projects/{project}/messages/status/{jobId}.
  • The project parameter scopes the request to a specific project context in the messaging platform.

Troubleshooting

  • Invalid or missing job ID: If the job ID is incorrect or not provided, the API will likely return an error indicating that the job was not found. Ensure the job ID matches a valid message job.
  • Unauthorized access: If the API key credential is missing or invalid, authentication errors will occur. Verify that the API key is correctly set up and has permissions for the target project.
  • Project not found: Using an incorrect project identifier may cause 404 errors. Confirm the project name or ID is correct.
  • Network issues: Connectivity problems can cause request failures. Check network access and API URL configuration.

Links and References

Discussion