Read vs write integration actions and when approval is required
When Camelia uses a connected integration, the action is classified as either a read or a write. That classification determines whether it runs immediately or waits for your approval.
How actions are classified
HIIE inspects the integration tool's name and looks for the first recognized verb. Read-type actions run immediately so Camelia can answer your question. Write-type actions — those that change something, like post, send, create, delete, or update — raise an approval popup before they run. If the verb isn't recognized, the action defaults to requiring approval (it fails safe toward asking you first).
The approval popup
Write actions surface a true-gate human approval popup. You review what Camelia wants to do and approve or decline it. Nothing is written to your external account until you approve.
Auto-approve option
Your account settings include an "Auto-approve integrations" toggle, off by default. When you turn it on, Camelia can run external write actions without asking for per-action approval. Leave it off if you want to review every change.
A built-in safeguard
For external write approvals, the server mints a one-time, server-side proof-of-approval token bound to you and the specific tool. The execution route requires that token for writes, so a scripted or forged call that tries to skip the approval popup is refused. This means the approval gate can't simply be bypassed by calling the API directly.