Actions10
- Queue Actions
- Message Actions
Overview
This node allows you to manage Cloudflare Queues, a service for sending, receiving, and managing messages in queues within the Cloudflare Workers environment. It requires a paid Workers plan on Cloudflare.
The Create Queue operation lets you create a new queue with customizable settings such as delivery delay, message retention period, max retries, and dead letter queue configuration.
Typical use cases include:
- Setting up new message queues for asynchronous processing workflows.
- Configuring queues with specific retry policies and message retention times.
- Automating queue creation as part of infrastructure provisioning or deployment pipelines.
Example: Automatically create a queue named "order-processing" with a 10-second delivery delay and a dead letter queue for failed messages.
Properties
| Name | Meaning |
|---|---|
| Cloudflare Queues require a Workers Paid plan | Notice that a paid Workers plan is required; free accounts will get 403 errors. |
| Queue Name | The name of the queue to create. |
| Settings | Collection of optional queue settings: |
| - Delivery Delay | Delay in seconds before a message is delivered. |
| - Message Retention Period | How long messages are retained in seconds (default is 4 days). |
| - Max Retries | Maximum number of retries allowed for a message. |
| - Dead Letter Queue | Name of the queue where messages exceeding max retries are sent. |
Output
The output is a JSON object representing the response from the Cloudflare API after creating the queue. This typically includes details about the newly created queue such as its ID, name, and configuration.
No binary data output is produced by this operation.
Dependencies
- Requires a valid Cloudflare API key credential with permissions to manage queues.
- Requires the Cloudflare account to have a paid Workers plan enabled; otherwise, API calls will return 403 Forbidden errors.
- The node makes HTTP requests to the Cloudflare API endpoint for queues under the account.
Troubleshooting
- 403 Forbidden Error: 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: Invalid API token or account ID. Verify your Cloudflare API credentials and ensure the token has queue management permissions.
- 404 Not Found Error: Could mean the specified queue or account does not exist. Double-check the queue name/ID and account ID.
- If the node is set to continue on failure, error details will be included in the output JSON for easier debugging.