Actions10
- Queue Actions
- Message Actions
Overview
This node enables interaction with Cloudflare Queues, a service for sending and receiving messages in a queue system. Specifically, the Send Batch operation allows users to send multiple messages at once to a specified queue. This is useful for efficiently enqueueing many messages in bulk rather than individually, which can improve throughput and reduce API calls.
Common scenarios include:
- Bulk processing tasks where many jobs or events need to be queued simultaneously.
- Sending batches of notifications, logs, or data payloads to be processed asynchronously.
- Integrating with systems that generate multiple messages at once and require reliable queuing.
Example: A user wants to enqueue 50 log entries generated by an application to a Cloudflare Queue for later processing by a worker script. Using this node’s Send Batch operation, they can submit all 50 messages in one request.
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 Cloudflare queue where messages will be sent. |
| Messages | Collection of messages to send in batch. Each message includes: |
| - Body | The content of the individual message. |
| - Delay Seconds | Optional delay (in seconds) before the message becomes available in the queue. |
Output
The output is a JSON object representing the response from the Cloudflare Queues API after attempting to send the batch of messages. It typically contains information about the success or failure of the batch send operation, including any metadata returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires a valid Cloudflare account with a paid Workers plan enabled; free plans cannot access the Queues API.
- Requires an API authentication token with permissions to manage queues and send messages.
- The node uses the Cloudflare REST API endpoint for queues under the user's account.
- Users must configure credentials in n8n with their Cloudflare API token and account ID.
Troubleshooting
- 403 Forbidden Error: Indicates the account does not have a paid Workers plan. Upgrade your Cloudflare plan to enable Queues.
- 401 Unauthorized Error: Usually caused by invalid API token or incorrect account ID. Verify credentials and ensure the token has appropriate permissions.
- 404 Not Found Error: Could mean the specified queue ID does not exist or the account ID is incorrect. Double-check the queue ID and account details.
- Empty or malformed messages: Ensure each message in the batch has a valid body string. Delay seconds should be a non-negative number.
- API rate limits or network issues: May cause intermittent failures; retry logic or error handling in workflows is recommended.