From answering to acting
Where Ask reads and answers, an agent reads, plans, and does. You can place an agent inside your app to qualify inbound leads, triage support tickets, draft follow-up emails, or keep records up to date — working on behalf of the signed-in user.
How agents run
| Trigger | Example |
|---|---|
| Chat | A user asks the agent to do something in conversation. |
| Record event | A new lead is created → the agent scores and routes it. |
| Schedule | Every morning → the agent summarizes yesterday's tickets. |
| Workflow step | A workflow hands off to the agent mid-flow. |
What an agent can do
- Read and create records in your Tadabase tables.
- Update fields — status, owner, priority.
- Send email through your templates.
- Trigger a Tadabase workflow as a tool.
Every one of those runs through the user's permissions, so an agent can only touch data that user could touch by hand.
Approval gates by default
High-blast actions — sending an email, writing records, calling an external API — pause for human approval unless you explicitly grant the agent autonomy for that tool. The agent shows what it intends to do; a person clicks approve.