Workflows
Conditions, thresholds, and actions — automated end to end.
Define what matters, set thresholds, and let Fastero handle the follow-through. Workflows check data, evaluate conditions, and route alerts to Slack, email, APIs, and notebook runs — so your team acts on problems instead of discovering them too late.
Workflow capabilities
From data check to routed action in one defined flow.
Workflows sit between triggers and actions. A trigger starts the flow, the workflow evaluates conditions and thresholds, and actions deliver the result to the right place.
Condition-based branching
Define conditions on query results, webhook payloads, or metric values. If revenue drops below a threshold, take one path. If it stays healthy, take another. Workflows branch based on data, not guesswork.
Threshold alerts to Slack and email
When a monitored value crosses a threshold — revenue dips, error rate spikes, pipeline stalls — the workflow sends a formatted alert to Slack or email with the relevant numbers included.
Notebook execution as a workflow step
Run a Jupyter notebook as part of a workflow. Useful for complex analysis that goes beyond a single SQL query — the notebook executes, and its output feeds the next step in the chain.
Downstream API calls
Call external APIs as workflow actions. Update a CRM record, create a Jira ticket, post to a webhook, or push data to Google Sheets. The workflow handles authentication and error retries.
Multi-step action chains
Chain multiple actions in sequence: run a query, check the result against a threshold, send a Slack alert, then update a tracking spreadsheet. Each step can pass data to the next.
Trigger integration
Workflows are activated by triggers — cron schedules, inbound webhooks, or data-change detection. The trigger starts the workflow; the workflow handles the logic and routing.
When to use workflows
Replace the manual checks your team runs every day.
Revenue and pipeline monitoring
Build a workflow that checks daily bookings against target, and alerts the revenue team in Slack when the number falls behind pace. Include the gap amount, the accounts that slipped, and a link to the full report.
Operational health checks
Monitor error rates, job completion status, or data freshness. When a data pipeline stalls or an integration stops syncing, the workflow fires an alert before downstream dashboards go stale.
Automated report distribution
Run a notebook that generates a weekly summary, then email the output to stakeholders and post a Slack digest. No one has to remember to pull the report — the workflow handles distribution.
Cross-system data routing
When a trigger detects a new high-value deal in the warehouse, the workflow can update HubSpot, notify the account manager, create a follow-up task in Jira, and log the event to a tracking sheet.
The trigger-workflow-action chain
Triggers start it. Workflows decide. Actions deliver.
A trigger fires (cron, webhook, or data change). The workflow evaluates conditions against the data. If thresholds are met, actions execute: Slack messages, emails, API calls, notebook runs. The entire chain runs without human intervention.
Step 1
Trigger fires
A cron schedule ticks, a webhook arrives, or a monitored query result changes.
Step 2
Workflow evaluates
Conditions check the data against thresholds. Branch logic routes to the right action path.
Step 3
Actions execute
Slack alert, email, API call, notebook run, or any combination — delivered automatically.
Related capabilities
Workflows connect to every part of the Fastero workspace.
Frequently asked questions
Common questions about workflows.
How are workflows different from triggers?
Triggers define when something happens — on a schedule, when a webhook arrives, or when data changes. Workflows define what happens next: they evaluate conditions, check thresholds, branch logic, and route actions. A trigger starts the workflow; the workflow handles the decision-making and action execution.
Can a workflow send alerts to both Slack and email?
Yes. Workflows support multi-step action chains. A single workflow can check a threshold, send a Slack alert, fire an email to a distribution list, and call an external API — all in sequence, with each step passing data to the next.
Is there a visual workflow builder?
Yes. Fastero provides a visual builder for defining conditions, thresholds, and action steps. It is intentionally simpler than tools like n8n or Make — designed for data teams who need if-then logic on query results, not for building complex multi-branch integration flows.
Can workflows execute Jupyter notebooks?
Yes. Notebook execution is a supported workflow action. This is useful when the analysis is too complex for a single SQL query — the notebook runs, and its output can feed downstream actions like Slack messages or API calls.
What kind of conditions can I define?
Conditions evaluate query results against thresholds (e.g., revenue below target), row counts (e.g., zero rows returned means no new signups), or value changes (e.g., a status field changed from "active" to "churned"). Branching logic routes to different action paths based on the evaluation.
How do workflows handle errors in action steps?
Failed action steps are logged with error details. For outbound webhook actions, Fastero retries with exponential backoff. You can inspect the execution log to see which step failed, what data was passed, and what error was returned.
Stop checking dashboards. Let workflows check for you.
Define a condition, set a threshold, and pick where the alert goes. Workflows run in the background so your team focuses on acting, not monitoring. Free to start.