How to Build a Tines Workflow for Phishing Triage
Tines is a security automation platform built around “stories” — visual workflows made of actions, branches and loops, with no code required unless you want it. A phishing triage story connects the report mailbox to your email gateway and EDR, enriches the indicators, and purges confirmed bad mail from every inbox in about two hours of building.
It sits in the same space as Torq and SOAR tools, with a reputation for a gentler learning curve and a community library of shared stories you can copy.
What is a Tines story?
A story is a sequence of actions (an HTTP call, an app integration, a code snippet, a formula) connected by branches (if/else on the output) and loops (for each item in a list). Each action’s output is available to later actions as structured JSON.
The mental model that makes Tines click: it’s a spreadsheet pipeline where each cell can be a web request. Nothing is hidden in a code block unless you put it there.
Step 1: start with the event transform
The trigger is usually a webhook from your report button or an email monitor. Tines receives a payload of varying shape, so the first two actions are always cleanup:
- Event Transform — map the incoming fields to a stable schema (reporter, subject, sender, urls, attachment hashes).
- Formula action — extract URLs from the subject and body with a regex formula.
Doing this once at the top means every downstream action reads the same field names, which saves you from rewriting branches when a reporter uses a different form.
Step 2: enrich with two parallel branches
Branches in Tines run in sequence unless you set concurrent execution on them. For enrichment, you want parallel: sender domain reputation and URL checks together, so the story finishes in two seconds instead of six.
Actions worth adding:
- Domain age lookup (an API or a small Python action calling a whois service).
- URL reputation from your existing blocklist vendor.
- A check against the recipient list pulled from your mail admin.
What about Tines’ built-in integrations?
It covers Microsoft 365, Google Workspace, CrowdStrike, Okta, Slack, Jira, VirusTotal and a few hundred more. The library is broad. What it doesn’t have, an HTTP action covers — most security vendors publish a REST API and a Tines HTTP action is five fields.
Step 3: branch on the verdict, purge on malicious
The verdict branch is a simple OR over the enrichment outputs: domain under 30 days old, URL on both blocklists, or attachment hash known-bad.
On the malicious path:
-
Loop over affected recipients.
-
Call the mail gateway’s purge endpoint per mailbox — or one bulk call if the vendor supports it.
-
Create a case in Jira or ServiceNow, or post to a Slack channel with the summary.
-
Send a one-line reply to the reporter.
On the benign path: reply to the reporter, close, no case created.
How do you test a Tines story safely?
Tines has a mode switch per action: you can run a story in dry-run and inspect each action’s output without executing the write. Use it on the purge call first, with a single test mailbox.
The way a story fails is almost always a field name mismatch on the third or fourth action, and dry-run surfaces those in seconds. Running live to find out is how people purge the wrong mailbox.
Step 4: add the approval gate before you go live
Approval actions pause a story and post an interactive message to Slack or Teams, waiting for a human to approve or reject. Put one before the purge call for the first month.
A useful detail: approvals can carry a timeout. Set 8 hours, with a default action on expiry — for phishing purge, expiry should mean “do not purge, escalate to the on-call analyst” rather than “purge anyway”.
How does Tines compare with Torq?
Both automate security workflows and both run in the cloud. Tines leans on visual assembly and a large community story library; Torq leans on AI-generated steps and heavier native case management. For a team that wants to read a workflow and understand exactly what it does, Tines’ structure is easier to audit. For a team that wants a case queue inside the same product, Torq does more of that natively.
Where Tines is the wrong choice
Teams without anyone who can read an API response, or without a defined phishing process to encode. Tines makes automation legible, not trivial — the story is only as good as the decision table behind it. And teams that need deep case management: Tines is the automation layer, not the analyst workspace.
Quick Summary
- A Tines story is actions, branches and loops over JSON, with 800+ integrations and an HTTP fallback.
- Transform the event at the top so every downstream action reads stable field names.
- Run enrichment branches concurrently to keep verdicts under a few seconds.
- Dry-run the purge action on a single test mailbox before going live.
- Add an approval gate with an 8-hour timeout that defaults to escalate, not purge.
Related guides
- Build your first Torq security workflow — the same phishing triage playbook in a heavier platform.
- Build your first Pipedream workflow — if the workflow is internal ops rather than security.
