Automations your ops team can build before lunch.
Visual canvas. Triggers, conditions, actions, loops. Branch on AND/OR logic. Walk related records up to three levels deep. Approval blocks, A/B tests, reply tracking, custom-object iteration, failure replay. Built in, not bolted on, not metered, not behind an Enterprise paywall.
A real automation engine, not a Zapier embed.
Strkr Flows ship with the same primitives Salesforce Flow Builder offers, and a few more it doesn't. Built on a DAG engine with cascade guards, dry-run mode, per-block metrics, and failure-notification fanout. Designed to run thousands of flows per tenant without breaking a sweat.
Records, schedules, manual fires.
On record created, updated, stage-changed. Cron schedules in your tenant timezone with DST handling. Manual 'run flow' from the record kebab. Webhook-in triggers. All in one builder, all with the same condition language.
Formulas with AND, OR, NOT.
Walk dotted paths: account.tier = 'strategic' AND owner.role = 'AE'. Up to three levels of related-record lookup. Three different authoring modes: ALL of, ANY of, or write the expression yourself. Live validation as you type.
Update, create, assign.
Update fields, create tasks, assign owners, send Slack, post webhooks, send emails (with Marketing add-on). Round-robin from a configured user pool, with capacity guards and PTO awareness.
React Flow + Dagre auto-layout.
Drag blocks, draw edges, click 'Tidy' to auto-arrange. Real product UI, not a placeholder iframe. Block hover-toolbars for duplicate and delete. Per-block metrics chips so you see what's working at a glance.
Validate before you publish.
Click 'Test run' from the editor. The engine walks the graph against a real record, returns what would happen, never touches the DB. Action handlers return wouldDo outputs. Safe iteration, fast feedback.
Throughput, success rate, p95 latency.
Every flow has a Live tab: 30-day throughput chart, in-flight by step, per-block fired counts. Performance tab with a funnel. Enrolled tab with per-record run history. The trust-building view.
Flows on Pro: 50,000 runs per month, unlimited active flows.
Starter ships with 1,000 runs a month. Pro lifts that to 50,000. Scale and Enterprise are unmetered. Most customers never see overage. Build a workflow on a Friday afternoon, watch it run a thousand times by Monday.
The details Salesforce charges extra for.
Flow Builder on Salesforce is included on Enterprise plans only. Per-run limits apply on every tier. Strkr Flows ship on Starter with the same DAG model, the same condition AST, and the same per-block dashboards. We just charge less and explain it more clearly.
No runaway loops.
Flow A updates a record, fires Flow B, which updates the same record, which... Strkr caps cascade depth at 10 and stops cold. Salesforce's depth-3 wall, more than tripled. Real-world flows almost never go past 3, but the headroom matters when something goes wrong.
Email the right people when a flow breaks.
Configure notification targets per flow: a role, a team, or specific users. Failed runs trigger a fanout via the existing notification system. Slack pings, in-app, email, all wired. No 'silent flow failure for three weeks' incidents.
Schedules in your local time.
0 9 * * * means 9am in your tenant's zone, not UTC. DST handled automatically via IANA names. Picker translates the cron to plain English so your ops team isn't memorizing crontab syntax. Most customers never type a raw cron string.
History shows the exact flow that fired.
Re-publishing a flow doesn't retroactively change run history. Every run records the version that ran it. The audit trail is real audit trail, not a moving target.
The Strkr-only details once you outgrow the simple cases.
Every other automation builder hits the same wall once you graduate past stage-change Slack pings. Loops, approvals, A/B tests, reply tracking, failure replay, custom-object iteration. They're all in the box.
Pause for a human, resume on a click.
Wait-for-approval blocks pause a run, drop it on the admin's approvals queue, and resume down the matching outbound port once someone clicks approve or reject. Add a note. Auto-expire after a timeout. No external Jira required.
Run two flows side by side, see which one wins.
Bind two or more flow variants to the same trigger with a weighted split. Strkr routes incoming records by your traffic weights, records variant lineage on every run, and surfaces the comparison in the dashboard. Update weights without a redeploy.
Loop and get-records across your custom data.
Define a custom object once. Loop over it, query it with the same filter AST as deals or contacts, fire record_created and record_updated triggers on it. The Flow engine doesn't care if the object is built in or built by you.
Math, strings, dates, branching with one block.
Drop a compute block, write an expression: vars.score = round(record.amount * 0.1 + length(record.tags), 2). Variables, record fields, loop items, trigger payloads. Function allowlist for safety. No sandbox escape hatches needed.
email_replied trigger fires only on real replies.
Inbound email lands on a Gmail thread your team previously sent to. Strkr knows it's a reply, not a fresh inbound, and fires email_replied. Build 'if no reply in 3 days, ping rep' or 'route hot reply to the AE'. Works on every connected inbox.
Failed runs land in a queue, not a void.
Block handlers that throw end up in the dead-letter queue with the original record context. Retry once the upstream issue is fixed. Or set a per-flow retry policy with exponential backoff and let Strkr re-fire automatically before giving up.
Re-run yesterday's failures with one click.
Pick a flow and a time window. Strkr re-fires every recorded run from that period: every Slack ping, every task creation, every webhook out. Useful when an integration was down for an hour and you need to catch back up.
Owner plus collaborators per flow.
Hand a flow to a specific user as its owner. Add viewers and editors per flow. Admins always have full access. Server-side ACL gates every read and write so a sales-ops contributor can't accidentally publish to a marketing flow.
One bad flow can't burn your monthly cap.
Per-tenant monthly run cap by tier. Per-flow per-minute rate limit. The emitter refuses to spawn runs once the cap is reached, logs the refusal, and resumes on the next billing cycle or tier upgrade. Quiet, automatic, predictable.
What teams are running today.
Deal stage → Slack ping.
When a deal moves to qualified, post in #wins, tag the owner, link to the deal, include account tier and amount. Built in three blocks.
NPS detractor → CSM task.
When NPS < 7, create a task on the account's CSM with a 7-day due date and a templated outreach script. Auto-routes to a manager if no CSM is assigned.
Renewal 60 days out → workflow.
60 days before any deal's renewal_date, fire a flow: update health field, generate renewal one-pager from doc template, schedule QBR task, notify the AE.
Funnel + step timing on every flow.
Try it free. Bring your team next week.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.