Actions10
- Queue Actions
- Message Actions
Overview
This node integrates with Cloudflare Queues, allowing users to manage queues and their messages programmatically. Specifically, the Update Queue operation lets you modify settings of an existing queue such as delivery delay, message retention period, maximum retries, and dead letter queue configuration.
Typical use cases include:
- Adjusting queue behavior dynamically based on workload or application needs.
- Changing retry policies or message retention without recreating the queue.
- Redirecting failed messages to a different queue for further inspection or processing.
For example, you might update a queue to increase the message retention period during peak times or set a dead letter queue to capture messages that repeatedly fail processing.
Properties
| Name | Meaning |
|---|---|
| Cloudflare Queues require a Workers Paid plan | Notice informing that a paid Workers plan is required; free accounts will get 403 errors. |
| Queue ID | The unique identifier of the queue to update. |
| Settings | Collection of queue settings to update: |
| - Delivery Delay | Number of seconds to delay message delivery after enqueueing. |
| - Message Retention Period | Duration in seconds to retain messages in the queue (default is 4 days = 345600 seconds). |
| - Max Retries | Maximum number of times a message will be retried upon failure. |
| - Dead Letter Queue | Identifier of another queue where messages exceeding max retries are sent. |
Output
The node outputs JSON data representing the response from the Cloudflare API for the update request. This typically includes confirmation of the updated queue properties or error details if the update fails.
No binary data output is produced by this operation.
Example output structure (simplified):
{
"success": true,
"result": {
"id": "queue-id",
"name": "queue-name",
"settings": {
"delivery_delay": 10,
"message_retention_period": 345600,
"max_retries": 5,
"dead_letter_queue": "dead-letter-queue-id"
}
}
}
Dependencies
- Requires a valid Cloudflare account with a paid Workers plan; free plans cannot access queue APIs.
- Needs an API authentication token with permissions to manage Cloudflare Queues.
- The node uses the Cloudflare REST API endpoint for queues under the user's account.
Troubleshooting
- 403 Forbidden Error: Indicates the account does not have a paid Workers plan. Upgrade your Cloudflare plan to enable queue operations.
- 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 information.
- General API Errors: Network issues or malformed requests can cause failures. Review the error message returned and adjust parameters accordingly.
If the node is set to continue on failure, it returns error details in the output JSON for each failed item.