Automatic rules (triggers)
Elbuz sends an email, changes a status or creates a document on its own as soon as something happens to a document or contact. Here you will learn how to create such a rule, which events and commands are available, how to calculate a field value with a formula and how to test a rule before it emails all your customers.
- How to set up automatic rules: event → condition → command
How Elbuz triggers work: the app sends an email, changes a status or creates a document on its own when something happens to a record. Your first rule in seven steps, plus ready-made scenarios.
- How to choose an event and set a rule condition
Which events an Elbuz automatic rule reacts to, how to build a condition in the builder, use a date placeholder, catch a status change and allow repeats for the same record.
- What a rule can do: eleven commands
What each of the eleven Elbuz automatic rule commands does: email, SMS, task, creating and changing documents and contacts, posting, HTTP request, running a flow.
- How to test a rule and clean up after a mistake
How to make sure an Elbuz trigger fired and won't do anything extra: the Operation log, the rules diagram with warnings, loops, mass firing during import, interrupted runs and cleaning up the consequences.
- How to calculate a field value in a trigger with a formula
Use a formula instead of a fixed value in a trigger command: conditions, arithmetic, joining text and reading JSON. Syntax, data sources, ready-made formulas and what Elbuz checks when you save.
