Actions10
- Queue Actions
- Message Actions
Overview
This node integrates with Cloudflare Queues, allowing users to send and manage messages within queues hosted on their Cloudflare account. It is particularly useful for workflows that require asynchronous message processing, task queuing, or event-driven architectures where messages need to be reliably sent, pulled, acknowledged, retried, or batched.
Typical use cases include:
- Sending individual or batch messages to a queue for later processing.
- Pulling messages from a queue to process them in downstream workflow steps.
- Acknowledging messages after successful processing to remove them from the queue.
- Retrying failed messages with optional delay.
- Managing message visibility and delivery timing.
Example: A user can send a message containing order details to a queue, which triggers downstream processing like inventory update or notification sending asynchronously.
Important: Cloudflare Queues requires a paid Workers plan; free accounts will receive 403 Forbidden errors when attempting to use this node.
Properties
| Name | Meaning |
|---|---|
| Cloudflare Queues require a Workers Paid plan | Notice informing users that a paid Workers plan is required to use Cloudflare Queues. |
| Queue ID | The identifier of the queue to operate on (required). |
| Message Body | The content of the message to send to the queue (required for Send operation). |
| Delay Seconds | Number of seconds to delay before the message becomes available for processing (optional). |
Output
The node outputs JSON data representing the response from the Cloudflare Queues API for each executed operation. The structure varies depending on the operation but generally includes:
- Confirmation of success or failure.
- Details about created or retrieved messages.
- Metadata such as lease IDs for message acknowledgment or retry.
- Error information if the operation fails.
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 have an active paid Workers plan to use Queues.
- Network access to Cloudflare's API endpoint
https://api.cloudflare.com/client/v4/accounts/{accountId}/queues.
Troubleshooting
- 403 Forbidden Errors: Occur if using a free Cloudflare Workers plan. Upgrade to a paid plan at https://dash.cloudflare.com/{accountId}/workers/plans.
- 401 Unauthorized Errors: Indicate invalid API token or account ID. Verify credentials and ensure the API token has Queue permissions.
- 404 Not Found Errors: Could mean the specified queue ID does not exist or the account ID is incorrect. Double-check these values.
- Message Format Issues: Ensure the message body is a valid string and delay seconds are non-negative numbers.
- Lease ID Handling: When acknowledging or retrying messages, provide comma-separated lease IDs exactly as received from pull operations.
If the node is set to continue on fail, errors will be returned in the output JSON with error details instead of stopping execution.