Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.conversion.ai/llms.txt

Use this file to discover all available pages before exploring further.

Some tool calls pause and ask you to approve before they run. This applies to anything that changes your workspace in a way worth confirming, such as creating, updating, applying, or moving assets.

​
How approvals work

When Conversion AI needs approval, a card appears in the chat with a short summary of what’s about to happen and two buttons:
  • Allow: runs the tool.
  • Deny: skips it. Conversion AI sees the denial and decides what to do next, usually stopping to ask you for direction.
If several approval-required tools are queued up in a row, you step through them one at a time, with a 1 of 3 style counter showing your progress. Examples of approval messages:
Are you sure you want to create a contact for “alex@acme.com”? Rename audience to “VIP customers”? Create campaign “Q2 launch”? Add 47 contacts to audience?

​
What requires approval

The general rule: reads don’t, writes do. Anything that creates, updates, applies, or moves something asks for approval. Anything that lists, gets, or counts does not.
See Tool calls for full list of tools that require approval
Renaming an email, form, workflow, audience, campaign, or folder changes the live asset immediately. There’s no preview step. Artifact creation only produces a preview; the live change happens at apply time, which has its own approval.

​
Best practices

  • Batch related changes in one instruction. A request like “go ahead and rename all of these” still produces an approval per action, but you’ll step through them together rather than reprompting Conversion AI each time.
  • Use Deny when something is wrong. Denying is a clear signal. Conversion AI will stop and ask you for direction rather than guess at a different approach.