Destination - Cloudflare Queues

[Swahjak]

Is your feature request related to a problem? Please describe.

We run our integration platform on Cloudflare Workers with CF Queues for async processing. Outpost's filtering and subscription management capabilities would be perfect for our event fan-out needs, but we can't deliver events directly to our existing CF Queues infrastructure.

Currently, to get events from Outpost into CF Queues, we'd need to:

1. Set up a webhook destination pointing to a CF Worker
2. Have that Worker validate and forward to the Queue

This adds an extra network hop, additional Worker invocations (cost), and another failure point in the delivery chain.

Describe the solution you'd like

Add a cloudflare_queues destination type that publishes directly to Cloudflare Queues via the Queues HTTP API.

Configuration fields:

• account_id (required) - Cloudflare Account ID
• queue_id (required) - Queue ID to publish to

Credential fields:

• api_token (required, sensitive) - Cloudflare API Token with queues:write permission

API endpoint:

POST https://api.cloudflare.com/client/v4/accounts/{account_id}/queues/{queue_id}/messages
Authorization: Bearer {api_token}
Content-Type: application/json

{
  "messages": [{ "body": <event_payload> }]
}

The implementation would follow the existing AWS SQS pattern — both are managed queue services with HTTP APIs.

Describe alternatives you've considered

1. Webhook → Worker → Queue proxy: Works but adds latency, cost, and complexity
2. AWS SQS or GCP Pub/Sub: Would require moving off Cloudflare infrastructure or running hybrid, adding operational overhead
3. Build custom event router: We're evaluating this but would prefer to use Outpost if it supported our infrastructure

Additional context

• Cloudflare Queues is GA as of 2024 and growing in adoption
• Natural fit for users already on Cloudflare Workers (Outpost itself can run on CF Workers)
• Similar complexity to existing AWS SQS destination
• Cloudflare Queues documentation
• Queues HTTP API reference

[alexluong]

Hi there, thanks for the detailed request, super helpful! This is definitely something we should support. We'll prioritize this internally. I can't quite guarantee a certain timeline because we're working hard to finalize v1.0. With that said, if you're interested in opening a PR for this, I'd be happy to help review and support further.

If you do plan on implementing this, let me know and I can share more about our destination logic, etc.

[Swahjak]

Hey @alexluong. That's fine and not going to lie; I had a bit of help from a little someone called Claude 😉. I'm not necessarily in a rush, as described it works fine for now just having a CF worker as webhook receiver.

[alexluong]

Noted! I saw your PR #657 and did a rough review btw, super cool! Did you test it by chance? I see the API body doesn’t fully match with Cloudflare API docs, so I was going to find some time and QA it later.

[Swahjak]

@alexluong honestly; no. I haven't had the chance to spin-up outpost just yet. I'm already in contact with one of your colleagues to get early access to the cloud platform, but given we're planning to using outpost in combination with our integration platform that we currently run on CF this was an early start on getting this into the platform.

I'm more than willing to do this properly, I just haven't gotten to it yet.

[alexbouchardd]

@Swahjak Thanks for the contribution. I've reached out for Early Access to the managed version.