Actions10
- Queue Actions
- Message Actions
Overview
This node integrates with Cloudflare Queues, allowing users to manage queues and messages within their Cloudflare account. It supports operations such as listing all queues, creating, updating, deleting, and retrieving information about queues. Additionally, it enables sending single or batch messages, pulling messages from a queue, acknowledging processed messages, and retrying failed messages.
Typical use cases include:
- Managing message queues for asynchronous processing workflows.
- Sending tasks or events to queues for distributed processing.
- Retrieving and handling messages from queues in automated pipelines.
- Implementing retry logic for failed message processing.
For example, a user might list all existing queues to monitor their status, send messages to a queue for background processing, or pull messages to trigger downstream automation.
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. |
Relevant input properties for the Queue - List operation:
The "List" operation under the "Queue" resource does not require additional parameters beyond selecting the operation itself.
Output
The node outputs JSON data representing the response from the Cloudflare Queues API for the requested operation.
For the List Queues operation, the output JSON contains the full API response listing all queues associated with the user's Cloudflare account. This typically includes details such as queue IDs, names, settings, and metadata.
No binary data output is produced by this node.
Dependencies
- Requires a valid Cloudflare API key credential with permissions to access Queues.
- The Cloudflare account must be on a paid Workers plan, as free plans cannot access the Queues API (otherwise, 403 Forbidden errors occur).
- The node makes HTTP requests to the Cloudflare API endpoint:
https://api.cloudflare.com/client/v4/accounts/{accountId}/queues
Troubleshooting
403 Forbidden Error:
Occurs if using a free Cloudflare Workers plan. Solution: Upgrade to a paid Workers plan at https://dash.cloudflare.com/{accountId}/workers/plans.401 Unauthorized Error:
Indicates invalid API token or account ID. Verify that the API token is correct and has the necessary Queue permissions.404 Not Found Error:
Could mean either the specified queue ID does not exist or the account ID is incorrect. Double-check the Queue ID and Account ID values.General API Errors:
The node surfaces error messages returned by the Cloudflare API. Review these messages for guidance on resolving issues.