# Choose operations, and when visitors confirm first

> Switch an Action's operations on or off, and choose which changes need the visitor to confirm before anything is sent.

Source: https://www.chirpbuilder.com/help/actions/operations-and-confirming  
Plans: Essentials, Creator, Business, Academy  
Last checked: 2026-10-27

When you're done, your Chirp uses only the operations you want, and asks visitors before the changes you
choose.

**Who can do this:** the account owner on any plan, and workspace admins and editors.

## Switch operations on or off

Open the Action in **7. Actions**. Each operation has a switch (1), its name, and its method and path.
Switch off the ones the Chirp shouldn't use. Visitors get the change once you click **Publish
changes**. The same goes for **Visitors confirm first** (2): switching it on protects visitors once you
publish.

![The newsletter webhook's operation: its on switch (1), the Changes data label, and Visitors confirm first switched on (2).](https://mjmtbasmrtksluvlnema.supabase.co/storage/v1/object/public/help-media/web-optimized/actions/operations-and-confirming/SS-ACT-040-01__operations__essentials__desktop__v01.webp?v=019d479433)

A Chirp can have up to 30 operations switched on, across all its Actions: "A Chirp can have up to 30
operations switched on. Switch some off first."

## What asks the visitor first

Operations are sorted by what they do:

- **Reads data** (GET): runs straight away, with no label.
- **Changes data** (POST, PUT, PATCH): asks first, unless you switch **Visitors confirm first** (2)
  off for it.
- **Deletes or cancels** (DELETE, or a name, path or summary with words like delete, remove, cancel,
  revoke or unsubscribe): always asks first. "Visitors always confirm this first."

Even with **Visitors confirm first** off, a change asks first when, earlier in the same reply, the Chirp
already got something back from an Action (this one included) or from a web search. That stops something
it read from making a change on its own.

A schema that marks an operation as harmless for GPTs (`x-openai-isConsequential: false`) starts with
**Visitors confirm first** off, except for deletes. When you replace the schema, the choice you made
stays.

When something asks first, the visitor sees a card with exactly what will be sent: see
[What visitors see when a Chirp wants to make a change](https://www.chirpbuilder.com/help/actions/confirmation-card).

## If it doesn't work

- **"… only reads data, so there's nothing to confirm."**
- **"… deletes or cancels something, so visitors always confirm it first."**
- **"… can't be switched on: …"**: the operation can't run; the reason follows. See
  [What Actions can't do yet](https://www.chirpbuilder.com/help/actions/limits).