Actions52
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
- Platforms Actions
- Projects Actions
- Webhooks Actions
Overview
This node operation allows you to check the delivery status of a previously sent message by querying its job ID. It is useful in scenarios where you want to track whether a message has been successfully delivered, is still pending, or has failed. For example, after sending a notification or alert through multiple messaging platforms, you can use this operation to verify the current status of that message delivery job.
Properties
| Name | Meaning |
|---|---|
| Message job ID | The unique identifier of the message delivery job whose status you want to check. |
| Project | The project identifier within which the message job exists. |
| JobId | Alias for the message job ID parameter (same as "Message job ID"). |
Output
The output JSON contains the status information of the message delivery job identified by the provided job ID. This typically includes fields indicating whether the message is pending, sent, failed, or other relevant status details returned by the messaging gateway API.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential configured with access to the messaging gateway service.
- The node makes authenticated HTTP GET requests to the messaging gateway's API endpoint for message status.
- The
projectproperty must correspond to a valid project identifier 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 or no data. Ensure the job ID matches a valid message job.
- Unauthorized errors: Occur if the API key credential is missing, invalid, or lacks permissions for the specified project.
- Project not found: If the project identifier does not exist or is misspelled, the request will fail.
- Network issues: Connectivity problems may cause timeouts or failures; verify network access to the API URL.
- To resolve errors, double-check all input parameters, ensure proper credentials are set up, and confirm the project and job ID values.
Links and References
- Messaging Gateway API Documentation (refer to your service provider's official docs for message status endpoints)
- n8n HTTP Request Node documentation for understanding how API calls are made
- General best practices for managing API keys and project identifiers in your messaging platform