Introducing: story runs

Introducing: story runs

Tines is pretty simple: you take a security process you want to automate, break it into small steps, and use one of the seven action types in Tines to perform that step. After an action performs its function, it passes the result (an event) along to the next action in the story which then performs its function, and so on until there are no more steps to perform.

This “atomic” architecture means that with complex stories which process lots of events, troubleshooting and can be challenging. It also means that understanding how long it took Tines to process an email, a vulnerability scan, or a Git commit could be *clears throat* time-consuming (no pun intended).

To solve this challenge, we’re proud to announce story runs.

What’s in a run?

A story run allows you to trace the exact path an event took through a story. It contains the actions and their emitted events allowing you to easily troubleshoot and benchmark your automation stories.

How Tines story runs work

Simple example

Take the simplified Tines story below which receives a city name via a webhook action, gets the weather in that city, and finally emails the result:

We can follow the route taken through the story by clicking the “Story Runs” tab in the toolbar and selecting a run. In the “Actions & Events” panel we can see the order of actions and their emitted events in chronological order.

By clicking the action name in the story run, we can view and edit that action’s properties.

Complex example

Now, let’s take a more complex story containing multiple different branches an event could take.

When we view the run for this story, we can see that, as expected, Tines displays every action that emitted an event. In the below example, we see that it’s Tuesday so the “Send weather to Slack” action emitted an event.

In another run, because the event was received on Saturday, an event was emitted by the email action:


Story Run performance metrics

Each story run includes a start time, end time and duration.

With these metrics we can easily calculate time and resources saved through Tines. For example, a phishing response story might take 19 seconds to process a Tines email, whereas to perform the same response manually could take up to 30 minutes.

*Please note we recently updated our terminology. Our "agents" are now known as "actions," but some visuals might not reflect this.*

Do less. A lot more.

Subscribe to our newsletter and get world class automation ideas straight to your inbox.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.