Actions10
- Queue Actions
- Message Actions
Overview
This node integrates with Cloudflare Queues, allowing users to manage queues and messages within their Cloudflare account. Specifically, the "Get Info" operation under the "Queue" resource retrieves detailed information about a specific queue by its ID.
Common scenarios for this node include:
- Monitoring queue configurations and status.
- Retrieving metadata or settings of a particular queue.
- Integrating queue information into workflows for decision-making or reporting.
For example, a user might want to fetch the current configuration of a queue before updating it or use the queue info to verify that a queue exists before sending messages.
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 unique identifier of the queue to retrieve information for. |
Output
The output is a JSON object containing the response from the Cloudflare API for the requested queue. This typically includes details such as the queue's name, settings (like delivery delay, message retention period, max retries), and other metadata provided by Cloudflare.
No binary data is output by this operation.
Example output structure (simplified):
{
"success": true,
"result": {
"id": "queue-id",
"name": "example-queue",
"settings": {
"delivery_delay": 0,
"message_retention_period": 345600,
"max_retries": 3,
"dead_letter_queue": ""
},
...
}
}
Dependencies
- Requires a valid Cloudflare API key credential with permissions to access Queues.
- The Cloudflare account must be on a paid Workers plan; otherwise, API calls will return 403 Forbidden errors.
- The node uses the Cloudflare REST 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 means invalid API token or account ID. Verify credentials and ensure the API token has Queue 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 ID.
- If the node is set to continue on fail, error details are returned in the output JSON under an
errorfield.