Approving an external write action from Camelia

When Camelia wants to take an action that changes something on a connected integration — posting, sending, creating, updating, or deleting — she pauses and asks you to approve it through a Human Input Popup (HIP).

Why you're being asked

Integration actions are classified as read or write. Read actions run immediately so Camelia can answer your questions. Write actions are different: they affect the outside world, so they raise a HIP approval before running. Until you approve, nothing leaves HIIE.

What the approval does

Approving the HIP authorizes that specific external write. Behind the scenes, the server mints a one-time, server-side proof-of-approval token bound to your account and the specific integration tool. The execution route requires that token, so the action you approved is the action that runs — and a scripted call that tries to skip the popup is refused.

Declining

If you decline, the write simply doesn't happen. Camelia continues the run without taking the external action, and you stay in full control of what your connected accounts do.

One at a time

Approval HIPs are queued and shown one at a time. If a single run wants to make several external writes, you'll review each one in turn rather than facing a stack of dialogs — so you always know exactly which action you're approving.

Skipping the prompt

If you'd rather not be asked for every write, there is an auto-approve setting ("Dangerously accept forever"). It is off by default, and leaving it off keeps each external write under your explicit, per-action review.