Flows
Every Week, Your Team Runs the Same Analysis. Files the Same Report. Makes the Same Judgment Call.
Fig automates that entire loop. Define the trigger, wire in the decision logic, and attach the action. Fig runs it end-to-end — every time the signal fires — without anyone having to remember to do it.
Every Flow Is a Business Workflow, Not a Technical Script
Signal → Decide → Act. Three steps that mirror how your best operators already think — now automated so nothing falls through the cracks.
Signal
Something happens that your business cares about — a metric crosses a threshold, a pattern repeats for 3 days, or it's Monday morning and the weekly review should run. The Signal step defines what kicks off the Flow, so that it fires exactly when it should — not when someone remembers to check.
Examples
Decide
Fig applies your business policies, checks the signal against your approved rules, and produces a structured recommendation. You can require multiple confirming signals before anything fires. You can require human approval before the action step runs. So that no decision is made on a single data point — and no action happens without the right person signing off.
Examples
Act
The right output goes to the right person, in the right place. A Slack message to the revenue ops channel. An email with the 7 accounts your CS team needs to call today. A task created in your project tool. So that the decision lands where it can be acted on — not in a dashboard someone has to remember to open.
Examples
Example Flows
Real decisions real teams run every week — automated end-to-end.
Weekly Revenue Review
Every Monday at 7am
Run variance analysis on last week's revenue
If anomaly detected, generate a situation brief and post to #revenue-ops Slack
Churn Signal Flow
When account signal score drops below 0.3
Corroborate with 2+ signals (usage, support tickets, payment delays)
Output entity list to CS team with ranked priority
CAC Budget Alert
Daily check of CAC by channel
If any channel exceeds $450 for 3 consecutive days
Pause budget and notify marketing VP
Monthly Cohort Analysis
First day of each month
Run cohort retention analysis for last quarter signups
Email report to exec team with gap closure recommendations
Why Flows Are Different from Existing Automation
Zapier, scheduled automations, and dashboard alerts each get you part of the way. Fig Flows close the loop.
Not an automated notification. A governed decision.
Zapier moves data. Fig Flows make decisions — with your approved metrics, your business policies, and corroboration requirements before any action fires.
Not a scheduled automation. A causal signal.
Scheduled jobs run on time. Fig Flows fire when the signal is real — corroborated by multiple metrics, checked against your baselines.
Not an alert. An output.
Pager alerts tell you something happened. Fig Flows tell you which accounts are affected, what caused it, and what to do — delivered as a structured output to the right person.
The output lands where your team already works.
Slack, email, or automated notification. A prioritized list of accounts. Downstream Flow trigger. Fig Flows don't create another dashboard — they deliver a decision to the person who needs to act on it.
Frequently Asked Questions
What is a Fig Flow?+
A Fig Flow is an automated decision workflow that runs Signal → Decide → Act end-to-end. You define a trigger (a metric threshold, a schedule, or an anomaly), a decision rule, and an action (Slack message, email, entity list). Fig runs the entire sequence without human intervention every time.
How are Flows different from Zapier or other automation tools?+
Zapier moves data between tools. Fig Flows make governed business decisions — checking your approved metric definitions, applying your business policies, and requiring corroborating signals before any action fires. The output isn't a data transfer. It's a decision.
What kinds of decisions can Flows automate?+
Any recurring decision with a verifiable trigger: weekly revenue anomaly checks, daily CAC alerts, monthly churn cohort analysis, account-level risk scoring, budget reallocation triggers. If your team runs the same analysis on a schedule, it can become a Flow.
Can a Flow require human approval before acting?+
Yes. You can configure any Act step to require human sign-off before it fires. The Flow surfaces the recommendation and waits for approval — useful for high-stakes decisions where you want an agent to do the analysis but a person to make the final call.
Explore the Platform
Metric Relationship Tree
Causal map of what drives what in your business
Learn moreMetric Definitions
Versioned, approved metrics for every agent and team
Learn moreBusiness Policies & Rules
Your business logic enforced on every query
Learn moreBusiness Entities
Accounts, customers, products resolved across sources
Learn moreMonitoring
24/7 anomaly detection with automatic root cause
Learn moreDecision Algorithms
12 built-in algorithms for governed analysis
Learn moreRoot Cause Analysis
Automated causal chain tracing
Learn moreIn-Memory Cache
Reduce warehouse costs, sub-second answers
Learn moreStop Re-Running the Same Analysis Every Monday.
Build your first Flow in minutes. Define the signal, wire in the decision, attach the action. Fig runs it automatically — with your approved metrics, your business policies, and corroborating signals built in.