Triggers and pipelines · AutessaDB
Trigger execution history
AutessaDB records every trigger firing. The Trigger Execution History shows each firing month by month with its event id, trigger name, type, database event, response status and time, and each one opens to the trigger as it was when it fired, the row before and after, and the action's response, kept as encrypted payloads.
-- the problem
Debugging automation without evidence is guesswork
When a welcome email did not go out, you need to know whether the trigger fired, what the row looked like, and what the tool said back. The history keeps all three, even if the trigger has since been changed or deleted.
What you get
- Per-table, per-month history with failed responses badged red.
- Trigger Definition: a snapshot of the trigger at firing time, flagged if it was later deleted.
- Database Event: the row's before and after values, field by field.
- Trigger Response: the outcome, with a link to the agent conversation for agent triggers.
- Visible to the person the trigger ran as, the table's admins and company admins.
- Company-wide history newest first from the CLI, with full uncapped detail per event.
-- how it works
How does trigger execution history work in AutessaDB?
Open the history
AutessaDB, then Trigger Execution History; pick a table and month.
Find the firing
Scan for red failed responses.
Check the data
Open Database Event to confirm the row change looked as expected.
Read the response
Open Trigger Response for the error, or jump into the agent conversation.
-- every option
What each firing keeps
| option | what it does |
|---|---|
| Event id and time | When it fired and how to find it again. |
| Trigger name and type | Which trigger, and whether it invoked a tool, agent, multi-agent or table update. |
| Database event | INSERT, UPDATE or DELETE, with before and after values. |
| Response status | Success or failure, with the response body. |
| Definition snapshot | The trigger configuration that fired. |
-- example
Full reference in the AutessaDB CLI docs and the API reference.
-- permissions
Who can do what?
| access | can |
|---|---|
| The person the trigger ran as | See its firings. |
| Table ADMIN and company Admins | See every firing for the table. |
-- faq
Questions about trigger execution history
Can I see what a trigger looked like when it fired?
Yes. Each firing keeps a snapshot of the trigger definition, flagged if the trigger was later deleted.
Are trigger payloads stored securely?
Yes. Before and after payloads are stored encrypted and decrypted when you view them.
Can I read the history from the terminal?
Yes, per table and month with autessadb trigger history, or company-wide with autessa trigger-history.
100% customizable, code and all
Make AutessaDB fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours