StatusedClaude Routines
Trigger Claude Code Routines from Statused notifications.
Claude Code Routines are Anthropic-managed cloud sessions of Claude Code that run on a schedule, in response to GitHub events, or when called via API. Pointing a Statused destination at a routine lets you turn an app or build status change into real work — auto-investigate a regression the moment a build goes invalid, draft a PR when your app enters review, post a structured summary to your release channel once a rollout completes, or anything else you can describe to Claude.
Prerequisites
- A Claude Pro, Max, Team, or Enterprise plan with Claude Code on the web enabled.
- A routine created at claude.ai/code/routines with an API trigger configured.
Setup
Create a routine with an API trigger
In Claude, go to claude.ai/code/routines and create a new routine (or open an existing one). Write the prompt you want Claude to run on each fire — for example, "Investigate why our iOS app's latest build was rejected and draft a fix PR."
Add an API trigger to the routine. This is what lets Statused start a run.
Copy the URL and generate a token
From the API trigger's settings:
- Copy the trigger URL. It looks like
https://api.anthropic.com/v1/claude_code/routines/trig_.../fire. - Click Generate token and copy the bearer token. It starts with
sk-ant-oat01-....
The token is shown only once
Anthropic displays the bearer token a single time. If you lose it, generate a new one from the same trigger — old tokens can be revoked from the same screen.
Add the destination in Statused
- In your dashboard, go to Destinations › Add Destination.
- Select the Claude Routines tab.
- Paste the Routine URL and the Bearer Token.
- Hit Add Destination.
Attach it to a workflow
Open or create a workflow under Workflows, pick your app, and select the new Claude Routines destination. From now on, every matching app or build status change will fire the routine.
How notifications are delivered
When a workflow fires, Statused makes a POST request to your routine URL with these headers:
| Header | Value |
|---|---|
Authorization | Bearer <your token> |
anthropic-beta | experimental-cc-routine-2026-04-01 |
anthropic-version | 2023-06-01 |
Content-Type | application/json |
The body is a single field:
{
"text": "The status of your app Markdown Email changed to Ready for Sale"
}Anthropic delivers text to your routine as run-specific context alongside the prompt you saved in the routine itself. You can reference it in the prompt as you would any other input — for example, "Use the status change in the trigger context to decide whether to open an issue."
Rotating the token
To rotate the bearer token, generate a new one from the routine's API trigger page in Claude, then open the destination's Edit page in Statused and paste the new value. The next notification will use the updated token.
Troubleshooting
Beta header may change
The anthropic-beta: experimental-cc-routine-2026-04-01 header reflects the current API surface for routines. If Anthropic publishes a new beta version, we'll update it on our side — but if you start seeing issues, reach out and we'll make sure your integration is up to date.
Related
- Anthropic — Claude Code Routines
- Webhooks reference — for sending the same status data to your own HTTP endpoint instead.