Skip to content
All articles
Security1 May 2026·3 min read

A blog bot that pitches its own posts: building a Slack-native publishing system on Cloudflare Workers and Durable Workflows

The useful frame is not "is this secure" but "what does an attacker get if this one thing goes wrong, and how quickly would we know".

Paycux engineering

The useful frame is not "is this secure" but "what does an attacker get if this one thing goes wrong, and how quickly would we know".

This piece walks through how we think about it at Paycux, what we have changed our minds about, and where the sharp edges are.

The interface problem

That brings us to the interface problem. Rotate on a schedule, not on an incident. A rotation path that has been exercised is a routine change; one that has never been used is an outage waiting for the worst possible moment.

Blast radius is the metric that actually matters. A credential that can read one organization's data is an incident; the same credential scoped to every organization is a company-ending event, and the difference is a design decision made months earlier.

Meeting people even further inside Slack

That brings us to meeting people even further inside slack. Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.

Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.

  • Scope credentials to the smallest useful blast radius
  • Alert on the abuse you cannot prevent
  • Exercise the rotation path before you need it
  • Log the decision, not just the outcome

Cloudflare Workers + durable workflows

Cloudflare Workers + durable workflows deserves its own treatment. Rotate on a schedule, not on an incident. A rotation path that has been exercised is a routine change; one that has never been used is an outage waiting for the worst possible moment.

Blast radius is the metric that actually matters. A credential that can read one organization's data is an incident; the same credential scoped to every organization is a company-ending event, and the difference is a design decision made months earlier.

Claude Code is the dev loop

Claude Code is the dev loop is where this gets concrete. Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.

Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.

Rotate on a schedule, not on an incident.

The AI pipeline: right model for the right job

Consider the ai pipeline: right model for the right job. Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.

Blast radius is the metric that actually matters. A credential that can read one organization's data is an incident; the same credential scoped to every organization is a company-ending event, and the difference is a design decision made months earlier.

When the bot proposes its own posts

Consider when the bot proposes its own posts. Blast radius is the metric that actually matters. A credential that can read one organization's data is an incident; the same credential scoped to every organization is a company-ending event, and the difference is a design decision made months earlier.

Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.

Stats that estimate time saved

That brings us to stats that estimate time saved. Rotate on a schedule, not on an incident. A rotation path that has been exercised is a routine change; one that has never been used is an outage waiting for the worst possible moment.

Rotate on a schedule, not on an incident. A rotation path that has been exercised is a routine change; one that has never been used is an outage waiting for the worst possible moment.

Where this leaves us

If there is one thing worth taking away, it is that the expensive decisions are the ones made implicitly. Making them on purpose costs an afternoon.

If you are working through the same problem and want to compare notes, the docs cover the mechanics and the console shows the behaviour on your own data.

Everything here, already built

Sign-in, enterprise SSO, directory provisioning, roles and an audit trail behind one API. Start with the quickstart and have a working sign-in this afternoon.

Start selling to enterprise customers

Create an account, point sign-in at Paycux, and get back to the part of the product that is actually yours.