AVA has 173 tools she can use across your connected platforms. Most of them take real actions — creating records, restoring deleted data, activating automation flows, modifying fields, removing team members.

Before AVA executes any action that changes your data or your platform configuration, she stops and confirms.

Two categories of actions

AVA classifies every action as either read or write.

Read actions — querying your data, generating reports, browsing records, viewing history — happen immediately. There is nothing to confirm because nothing changes.

Write actions — creating, updating, restoring, deleting, activating, deactivating — require explicit confirmation before execution. AVA will not proceed without it.

What a confirmation looks like

Before executing a write action, AVA will describe exactly what she is about to do:

"I'm going to restore the deleted Acme Corp project record from March 14th. This will: - Re-create the record in your Podio Client Projects app - Restore its 12 field values as they existed at the time of deletion - Re-attach its 3 file attachments from FileHaven

>

Shall I proceed?"

The description is specific. It tells you the record, the platform, the fields involved, and what the outcome will be. There are no surprise side effects.

Tell AVA yes to proceed. Tell her no, or ask to change something, and she will adjust or stop.

Irreversible actions get additional caution

Some actions are difficult or impossible to reverse:

  • Deleting a record that has no backup (though ThatApp's lake usually does have it)
  • Permanently removing a team member's access
  • Deleting a credential
  • Bulk-modifying a large number of records

For these actions, AVA is more explicit about the consequences and may ask you to confirm a specific aspect of the outcome — not just the action itself.

"This will permanently remove Sarah's access to the Salesforce connection. She will be logged out of any active sessions immediately. This cannot be undone through AVA — you would need to re-invite her. Do you want to continue?"

You can always cancel

At any point in a multi-step operation, you can tell AVA to stop. She will halt the operation, report on what was completed and what was not, and ask what you would like to do next.

What this means in practice

AVA is not an auto-pilot. She is a capable colleague who proposes what she is about to do, waits for your approval, and then acts.

You are always in the loop. You always know what is about to happen before it happens. If something AVA proposes looks wrong, you say so and she corrects course.

This is intentional. The capability to take real action across your platforms is powerful. The confirmation requirement is what makes it safe.

Related: Introducing AVA — Your Organizational Brain · What AVA Can Do — All 173 Actions · How to Have a Productive Conversation With AVA