GateKit icon

GateKit

Universal messaging gateway - send messages across multiple platforms

Actions51

Overview

The "Retry" operation under the "Messages" resource allows users to retry sending a previously failed message job within a specified project. This is useful in scenarios where message delivery has failed due to transient issues such as network errors or temporary platform outages. By retrying the failed message job, users can attempt to resend the message without manually recreating it.

Practical examples include:

  • Automatically retrying failed notifications sent via messaging platforms.
  • Manually triggering a retry for a specific failed message job after investigating the failure cause.
  • Integrating with workflows that monitor message statuses and trigger retries when failures occur.

Properties

Name Meaning
Failed message job ID The unique identifier of the failed message job that you want to retry.
Project The identifier of the project within which the message job exists.
JobId Alias for the failed message job ID parameter (same as "Failed message job ID").

Note: The properties "Failed message job ID" and "JobId" represent the same value and are required to specify which failed message job to retry.

Output

The node outputs the JSON response from the API call that attempts to retry the failed message job. This typically includes details about the retry request status, such as confirmation that the retry was initiated or any error messages if the retry could not be performed.

The output does not include binary data.

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests to the GateKit API.
  • The node makes HTTP POST requests to the endpoint /api/v1/projects/{project}/messages/retry/{jobId}.
  • The user must have appropriate permissions on the specified project to perform message retries.

Troubleshooting

  • Invalid or missing job ID: If the provided job ID does not exist or is incorrect, the API will return an error indicating the job was not found. Verify the job ID before retrying.
  • Insufficient permissions: Ensure the API key used has permission to access the project and perform message retries.
  • Project not found: Confirm that the project identifier is correct and that the project exists.
  • API connectivity issues: Network problems or incorrect API URL configuration may cause failures. Check the API base URL and network connectivity.
  • Message already succeeded or cannot be retried: Some message jobs may not be eligible for retry if they are not in a failed state or if retry limits are exceeded.

Links and References

Discussion