
Why it matters
Automations nobody can read become automations nobody trusts.
When automations are hidden in scripts or scattered across apps, nobody can tell which event set off which process, so people double-check everything by hand.
Triggers & Actions spell out each rule in plain words, “when this happens, do that”, and show every time it ran.
How triggers & actions work
A clearer way to work.
Select a step to see what happens.
Step 1 of 5
Choose event
Pick what starts the rule, such as a paid invoice.
On screen
Event Source: Invoice paid
Interface and key controls
See the details that keep work moving.
Choose an event and an action, then run a test. Try the same event twice to see duplicate protection, or a record missing a field.
Trigger Filters
Amount ≥ $500.00
Field mapping
Test with
Business scenarios and exceptions
Designed for real-world exceptions.
Each event has an idempotency key so it runs once, retries stop at a set limit, and mapping errors say exactly which field is missing.
Business scenario
A practical day in the business.
Summit Ridge Landscaping in Fort Worth, TX wants to thank larger customers. Office manager Brenda Kolb set up one rule.
- Tue 2:14 PM — Invoice INV-3381 for $1,240.00 is paid by the Halverson family.
- 2:14 PM — The amount passes the $500.00 filter; a “Send thank-you card” task is created for account manager Cody Reed.
- 2:16 PM — The payment app sends the same event again; the duplicate is skipped.
- Wed 9:00 AM — A paid invoice without a mailing address fails with “Missing: mailing address.” Brenda fixes the record and reruns it.

What events can start an automation?
Events from Noxtill such as a new booking, a paid invoice or a submitted form, plus events from connected apps.
How do filters work?
Filters narrow when a rule runs, such as only for invoices over $500.00 or only at one location.
What prevents an automation from running twice?
Each event has a unique key. If the same event arrives again, the run is skipped and marked as a duplicate.
Who should use triggers and actions?
Ops teams who want simple, readable automations between their everyday tools.
What happens when an action fails?
It retries up to a set limit. If it still fails, the run shows the reason and can be rerun after the fix.
Make every automation easy to read.
Start a 14-day free trial or book a demo to set up your first trigger.
