Cloudflare Queue icon

Cloudflare Queue

Send and receive messages using Cloudflare Queues (requires paid Workers plan)
Join our community

Actions10

Overview

This node integrates with Cloudflare Queues, allowing users to manage message queues and messages within those queues. Specifically, the Message - Retry operation enables retrying failed messages by specifying their lease IDs and optionally setting a delay before retrying.

Common scenarios for this node include:

  • Handling transient failures in message processing by retrying messages after a delay.
  • Managing message workflows where messages that previously failed need to be reprocessed.
  • Automating error recovery in distributed systems using Cloudflare Queues as a messaging backbone.

For example, if a message processing service fails to handle certain messages due to temporary issues, this node can be used to retry those messages after a specified delay, improving reliability without manual intervention.

Properties

Name Meaning
Cloudflare Queues require a Workers Paid plan Notice that Cloudflare Queues require a paid Workers plan; free accounts will get 403 errors.
Queue ID The identifier of the queue on which to operate.
Lease IDs Comma-separated list of lease IDs representing the messages to retry.
Retry Delay Seconds Number of seconds to wait before retrying the specified messages (optional delay).

Output

The output is an array of JSON objects representing the response from the Cloudflare Queues API for the retry request. Each item corresponds to the result of the retry operation for the given lease IDs.

If an error occurs, the output may contain an error object with fields such as:

  • error: A descriptive error message.
  • originalError: The original error message returned by the API.
  • httpCode: The HTTP status code of the error.

No binary data is produced by this operation.

Dependencies

  • Requires a valid Cloudflare account with a paid Workers plan (free plans cannot access Queue APIs).
  • Needs an API authentication token with permissions to manage Cloudflare Queues.
  • The node uses the Cloudflare REST API endpoint:
    https://api.cloudflare.com/client/v4/accounts/{accountId}/queues/{queueId}/messages/ack
  • Proper configuration of credentials in n8n for Cloudflare API access is necessary.

Troubleshooting

  • 403 Forbidden Error:
    This indicates the Cloudflare account does not have a paid Workers plan. Upgrade your plan at:
    https://dash.cloudflare.com/{accountId}/workers/plans

  • 401 Unauthorized Error:
    Usually caused by invalid API token or account ID. Verify that the API token has the required permissions for Cloudflare Queues and that the account ID is correct.

  • 404 Not Found Error:
    Could mean either the specified queue does not exist or the account ID is incorrect. Double-check the Queue ID and Account ID.

  • Invalid Lease IDs:
    Ensure the lease IDs are correctly formatted, comma-separated, and correspond to messages currently leased from the queue.

  • Retry Delay Issues:
    If the retry delay is set too high or negative, the API might reject the request or cause unexpected delays.

Links and References

Discussion