Triggers, flows and background jobs
Some of the work in Elbuz runs without a person: on a schedule or in response to an event.
This section covers how to create such a rule, what to do when the schedule is on but nothing happened in the morning, and how to find out who exactly changed or deleted data.
Subsections
Automatic rules (triggers)
“Event → condition → command” rules for documents and contacts: how to create them, what they can do and how to test them.
Schedule, job queue and flows
How to set up scheduled runs, what to do when a schedule didn't fire, how to monitor the job queue and chain operations into a flow.
Articles in this section
- Who did this: the operation log and what a deletion leaves behind
Where to see who changed or deleted a record: the operation log, change history, and the document and contact trash. How long each log is kept and what can no longer be restored.
