Before you dive into using Templates or building Custom Workflows, it's important to understand the basic building blocks that make up every workflow in Tesorio. If you're familiar with tools like Zapier or Make.com, these concepts will feel very familiar.
Each workflow in Tesorio is made up of a few core components:
Triggers
A Trigger is what starts a workflow. It's the event that tells the system, "Now it's time to take action."
Triggers can be based on:
Events (e.g., when an invoice is created, when a tag is added)
Schedules (e.g., every hour, every day, every week)
Triggers can also be configured with additional criteria, allowing you to narrow down exactly when a workflow should run. For example:
Trigger when an invoice is created and matches specific filters (such as invoice amount or customer tag).
Trigger when a customer tag is added only for certain tags.
This flexibility ensures that workflows are not just reactive but smart and targeted.
Actions
An Action is what happens after the trigger fires. It's the task or set of tasks that you want the workflow to perform automatically.
Examples:
Assign an invoice to a collections agent
Add a note to a customer record
Send a Slack notification
Apply or remove a tag on an invoice
A single workflow can have one or multiple actions based on your needs.
Flow Control Elements
Tesorio Workflows also offers powerful flow control components that allow for more complex workflows:
Loop on Items
This allows you to iterate over a list of items that a trigger provides.
For example, if a trigger returns multiple invoices, you can loop through each invoice and perform actions on each one individually.
Router
The Router component allows your workflow to branch into multiple paths based on conditions you define.
You can create complex branching logic with multiple conditions using AND/OR statements.
Each branch can have its own set of actions.
Includes an "Otherwise" path if none of the defined conditions are met.
Routers give you the ability to create dynamic, decision-based workflows that adapt based on the data.
Summary: How It All Connects
At a high level, a workflow follows this structure:
Trigger (with optional criteria/filters) ➔ (optional Loop and/or Router) ➔ Action(s)
Once the trigger happens, any filtering criteria are evaluated. If applicable, the workflow can loop through items or branch into different paths before carrying out the specified actions.
---
Understanding this basic structure will help you feel comfortable whether you're customizing a Template or building a workflow entirely from scratch.