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 process messages within those queues. Specifically, the "Acknowledge" operation for the "Message" resource lets users confirm that certain messages have been successfully processed, which typically removes them from the queue to prevent reprocessing.

Common scenarios include:

  • Confirming successful processing of messages pulled from a queue.
  • Managing message lifecycle in distributed systems where multiple consumers handle queued tasks.
  • Ensuring reliable message handling by explicitly acknowledging processed messages.

Practical example:
After pulling messages from a Cloudflare Queue and processing them (e.g., updating a database or triggering workflows), you use this node's acknowledge operation to inform Cloudflare that these messages can be removed from the queue.

Properties

Name Meaning
Cloudflare Queues require a Workers Paid plan Notice informing users that a paid Workers plan is required; 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 specific messages to acknowledge.

Output

The output JSON contains the response from the Cloudflare API after attempting to acknowledge the specified messages. This typically includes success status and any relevant metadata returned by the API.

No binary data output is produced by this operation.

Example output structure:

{
  "success": true,
  "acks": [
    {
      "lease_id": "lease1"
    },
    {
      "lease_id": "lease2"
    }
  ]
}

Dependencies

  • Requires a valid Cloudflare API key credential with permissions to access Cloudflare Queues.
  • The Cloudflare account must be on a paid Workers plan; otherwise, API calls will return 403 Forbidden errors.
  • Node configuration requires setting the Cloudflare Account ID and API token.

Troubleshooting

  • 403 Forbidden Error: Indicates the Cloudflare account is not on a paid Workers plan. Upgrade your plan at https://dash.cloudflare.com/{accountId}/workers/plans.
  • 401 Unauthorized Error: Invalid API token or Account ID. Verify credentials and ensure the API token has Queue permissions.
  • 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.
  • Empty or malformed Lease IDs: Ensure the Lease IDs input is a comma-separated string of valid lease identifiers without extra spaces or empty entries.

Links and References

Discussion