Introduction
Stories are a collection of interconnected actions working towards a singular mission that can be automated. They can be viewed as analogous to use-cases or playbooks. For example, you might have a phishing story, an offboarding story, or an incident response story. To support sharing, stories can be imported and exported.
A story is made up primarily of actions and tools.
Adding actions to stories
Actions can be added to a story in three ways:
Dragging an empty action or a template onto the storyboard.
Copy and pasting actions into the storyboard from another story.
Copy and pasting a cURL request into the Tines storyboard.
Learn more about actions here.
Default stories
When Tines tenants are created they contain 1 story:
Your first story: This story contains a quick video demonstrating the basics of Tines and instructions to build your first story.
Managing stories using terraform
Tines supports Infrastructure as Code (IaC) for stories and other resources using the official Terraform provider for Tines. This enables you to manage, version, and automate your Tines stories alongside the rest of your infrastructure.
Why use Terraform with Tines?
Version control: Store your stories as code in Git.
Automation: Deploy and update stories automatically as part of your CI/CD pipeline.
Consistency: Ensure your Tines environment matches your desired state.
For more information see: