A radically new way of building
Tines helps the world's most security-conscious companies automate their repetitive workflows. But how does it actually work? Here are a dozen key features of Tines.
Seven Actions
and a storyboard
Every workflow is made up of a sequence of steps: "receive alert" → "check if duplicate" → "send notification". In Tines, we call these steps Actions.
Tines lets you automate any manual workflow by dragging, dropping and connecting a series of Actions together in what we call a Story.
Tines is powerful because there are only seven Action types. That’s it. Every Story you build will be a unique combination of them, configured in different ways. And anyone can learn how to use Actions: no code, no scripting, no SDKs.
Once you’ve mastered the seven Action types, you have every tool you need to automate your workflows. The Action types infinitely stack and combine – like Legos – allowing you to automate messy, real-world processes of unlimited complexity.
Templates and integrations
Tines comes with over 2,000 (and counting) pre-configured Action Templates, allowing you to instantly integrate with the tools in your security stack, like Crowdstrike, Jira, Slack, or VirusTotal.
For cases where there’s no template – like your internal tools or lesser-known APIs – it’s not a problem. You can directly configure an Action to do what you need, and create your own private Action Templates for those things you need frequently.
Story Runs
Send to Story
Sometimes, you’ll find sets of Actions that you want to reuse in different places. With Send to Story, you can call them from anywhere, even across different teams in your company. For example, HR could build a “Get Employee Information” Story, which all users and teams could make use of.
Automation needs humans
Great automation only happens when people are involved: from collaborating on building and maintaining Stories, to providing input and oversight when they run. Here are four features – Prompts, Teams, Annotations, and Forms – built for human involvement.
Prompts
Teams
Annotations
Forms
Smart retries
Monitoring
Scheduling
Say you have a story that onboards new employees on a daily basis. It fetches the list of new people from your HR system and creates new accounts in GSuite, Slack, ADP, Datadog and CrowdStrike. Using Scheduling it’s simple to define when and how often the story should run – without technical fuss like cron syntax.