Turn Actions off, replace a schema, or remove an Action

When you're done, your Chirp's Actions are paused, updated or gone, as you need.

Who can do this: the account owner on any plan, and workspace admins and editors. An editor who can't publish can replace or remove, but someone who can publish has to click Publish changes.

Turn all Actions off

At the top of 7. Actions, switch Actions on off. "Turning Actions off applies right away, for visitors too. Your settings are kept." Switch it on again any time.

With Actions off, the Chirp (and your preview) can't use them, and it tells people it can't check or do that right now. Handy while you fix an Action whose calls keep failing.

Replace the schema

When the API changes, open the Action and click Replace schema (1). Paste the new schema and click Replace.

"Operations keep their on/off switches, and the API key stays." Operations with the same method and path keep their settings. One whose method or path changed counts as new. New operations are switched on (up to 30 across the Chirp). Your Authentication choice stays, unless the new schema uses another kind of sign-in: then the schema's replaces it, so check Authentication afterwards. "Schema replaced. Publish to use it for visitors."

Remove an Action

Click Remove (2) and confirm: "Remove the Action "…"? Visitors keep using it until you publish." Then click Publish changes. Its key is deleted once you publish (on a draft Chirp, straight away). Its call history stays until it ages out.

Good to know

• Replacing and removing need publishing; the Actions on switch and keys don't.
• Discard in the bar at the top brings a removed Action back, until you publish. It throws away every change you haven't published, not only this one. A draft Chirp has no Discard.
• Going back to an earlier version brings back that version's Actions, but not the keys of Actions you removed and published: those show Needs an API key. Add the key again, then publish.