Actions10
- Queue Actions
- Message Actions
Overview
This node enables interaction with Cloudflare Queues, a managed message queue service integrated with Cloudflare Workers. It supports operations to create, delete, update, list, and get information about queues. The "Delete" operation specifically allows users to remove an existing queue by its ID.
Use cases include managing message queues for asynchronous processing workflows, such as task scheduling, event handling, or decoupling microservices. For example, you might delete obsolete or test queues to keep your environment clean.
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. |
| Queue ID | The unique identifier of the queue to delete. |
Output
The output is a JSON object indicating success and echoing the deleted queue's ID. Example structure:
{
"success": true,
"queueId": "the-queue-id"
}
No binary data is produced by this operation.
Dependencies
- Requires a valid Cloudflare API key credential with permissions to manage queues.
- The Cloudflare account must be on a paid Workers plan; otherwise, requests will fail with 403 Forbidden errors.
- The node makes HTTP requests to the Cloudflare API endpoint:
https://api.cloudflare.com/client/v4/accounts/{accountId}/queues.
Troubleshooting
- 403 Forbidden Error: Indicates the Cloudflare account is not on a paid Workers plan. Upgrade the plan at https://dash.cloudflare.com/{accountId}/workers/plans.
- 401 Unauthorized Error: Usually caused by invalid API token or incorrect account ID. Verify credentials and ensure the token has queue management 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.
- If the node is set to continue on failure, error details are returned in the output JSON under an
errorfield.