The simplest story design is linear, where actions run sequentially from top to bottom without branching. Here are a few examples of when to use a linear story design:
For straightforward processes with a single path.
When each step must be completed before the next begins.
For simple data transformations or notifications.
When you're first learning Tines and want to build confidence.
Anatomy of a linear story
A linear story typically follows this structure:
Kickoff: Where the story begins (i.e., webhook, scheduled action, receive email).
Processing: Actions/tools that transform or enrich data.
Output: The final result (i.e., notification, system update, data storage).
Each action or tool passes its event data directly to the next element in the story sequence, creating a singular flow of events.
Linear story example
Let's look at a practical example of a linear story: Automated Vulnerability Alert Processing
1. Receive Vulnerability Alert (Webhook)
↓
2. Extract CVE Details (Event Transform)
↓
3. Enrich with Vulnerability Database Info (HTTP Request)
↓
4. Format Alert Message (Event Transform)
↓
5. Send to Security Team (Send Email)Kickoff: Step one - Receive Vulnerability Alert
Processing: Steps two - four
Output: Step five - Send to Security Team
Benefits of linear design
Simplicity: Easy to follow and understand.
Predictability: Data flows in one direction.
Troubleshooting: Easier to identify where issues occur.
Readability: Clear visual representation of the process.
Maintenance: Straightforward to update or modify.
When to expand beyond linear
As you become more comfortable with Tines, you'll recognize when a process is too complex for a purely linear approach. Consider moving to a branching design when:
Your process needs to handle different scenarios based on data values.
You need to implement approval workflows with multiple outcomes.
Your automation needs to process different types of inputs differently.
Linear stories are the building blocks of automation in Tines.
A linear story is the introductory design to workflows in Tines. Mastering this pattern first will provide a solid foundation for moving on to more complex designs.