Feature · Sales Workflow Automation

A sales workflow automation layer the team actually trusts.

A sales workflow automation layer turns stage changes, meeting events, inbound signals, and manager actions into enforced follow-ups, handoffs, and approvals. Strkr's Flows runs the automation native to the CRM, with versioning, a visual canvas, and audit on every action - so the automation is readable, auditable, and testable without a sync tool.

Start free trial See pricing
What automation triggers on

The events a sales motion can react to.

The automation layer is only as useful as the triggers it listens to. Strkr's Flows ships triggers for every meaningful sales event: stage change, meeting booked, email reply, deal update, inbound form, and signature event. The sections below are the common triggers teams build on.

Stage change

Deal moved to a new stage.

The most common trigger. When a deal moves from Qualify to Discovery, Flow fires the discovery-call task, drops the recap template, and pings the SE. Stage automation is the backbone of the enforced motion.

Meeting booked

Calendar event created.

When a meeting is booked, Flow fires the pre-meeting prep: pull the account activity, assemble the meeting brief, drop it in the attendees' inboxes. The AE walks into the meeting prepared without a Monday morning scramble.

Email reply

Buyer responded.

When a buyer replies to a tracked email, Flow updates the engagement signal on the deal and alerts the rep. Buyer response is a high-signal event that most CRMs miss. Strkr captures it in the automation layer.

Deal field update

Amount, close date, next step.

When the amount or close date changes, Flow fires audit logging, manager notification (above threshold), and forecast refresh. Deal updates that drive forecast changes are first-class triggers.

Inbound form

Web form submitted.

An inbound form submission fires the lead routing flow: enrich, score, assign to a rep, send the welcome email, book the meeting. The inbound-to-first-touch cycle compresses from hours to minutes.

Signature event

DocuSign or PandaDoc reports signed.

When the signature provider reports signed, Flow advances the deal, writes the signed date, kicks off customer success onboarding, opens the project, and triggers commission. The close-week ritual becomes a flow.

What automation does

The actions the Flow can take.

A trigger is the when. An action is the what. Strkr's Flows library ships the common actions sales teams need: create task, send email, update field, assign owner, request approval, open project, and run a sub-flow. The sections below walk the primary actions.

Create task

Assign the next-step work.

The most common action. On stage change, Flow creates the right next-step task on the deal - discovery recap, proposal reminder, close-plan email, decision-committee call. The task lands on the owner's task list in Strkr.

Send email

Templated, personalized, logged.

Flow can send an email from a template with CRM field personalization. The email logs to the deal activity timeline. The rep stops copy-pasting the follow-up email after every meeting.

Update deal field

Write back on event.

Flow can update deal fields on an event. On signature received, set stage to Closed Won and set signed date. On meeting booked, set the next-step field. Deterministic updates reduce the "forgot to update it" problem.

Request approval

Discount, scope, legal entity.

On high-discount proposal send, Flow requests approval from the manager or CFO per policy. The approval lands on the approver's desktop with the deal context one click away. The decision writes to the audit timeline.

Open project

Customer onboarding kickoff.

On Closed Won, Flow opens the customer onboarding project in Projects, drops the kickoff tasks, and invites the CSM. The handoff is deterministic. Nothing falls between sales and success.

Run sub-flow

Compose complex sequences.

A Flow can invoke another Flow. A proposal-send flow invokes the approval flow, which invokes the signature flow, which invokes the handoff flow. Composition keeps individual flows readable while supporting complex sequences.

How the automation is built

Visual canvas, versioning, test, audit.

Flows is the automation surface. The canvas is readable by a non-admin, versioned by draft, testable with sample data, and auditable per run. The sections below are the mechanics that make the automation layer trustworthy at scale.

Visual canvas

Readable by the VP.

The Flows canvas renders triggers and actions as nodes with the data they operate on. A VP of Sales reads the canvas without a developer. The canvas is the readable artifact of the sales motion.

Draft and publish

Edit without breaking live.

Every Flow change lands as a draft. The sales ops lead edits, tests, and publishes. The live Flow continues until publish lands. No "I pushed a Flow at 2pm and the forecast broke."

Test with sample

Dry-run on a chosen deal.

The Flow builder supports a dry-run against a chosen deal. The dry-run shows what each action would have done without executing. The sales ops lead tests the Flow on a real deal shape before publishing.

Run history

Every execution, auditable.

Every Flow run writes to the audit history with trigger, inputs, actions executed, and outcome. The run history is the forensics tool when "why did this deal get the discount email." The audit is on by default.

Error handling

Retry, skip, alert.

When a Flow step errors - a required field missing, an external integration down - the Flow applies the configured policy: retry with backoff, skip and continue, or alert the sales ops lead. The behavior is explicit on the Flow, not an implicit default.

Permission on actions

Flow runs as the trigger owner.

A Flow executes under the permissions of the event owner by default. A deal update Flow runs as the deal owner. An inbound form Flow runs as the system account. Permission rules carry - a Flow cannot do what the owner cannot do.

What this replaces

The sync tools, the Zaps, the admin hours.

Most sales teams build automation across three tools: Salesforce flows for in-CRM, Zapier or Make for cross-system, and a manual process for the rest. Strkr runs all three on one Flows canvas. The sections below are the trade-offs.

Zapier scenario

Flexible, brittle, invisible.

Zapier is universal. The scenarios work until they do not, the audit lives in Zapier logs, and the sales ops lead has no visibility inside Strkr. Strkr's Flows runs natively with audit on the deal.

Make.com scenario

Powerful, offstage, licensed.

Make.com is a stronger Zapier. The cost is a separate subscription, a separate audit, and reps have no visibility. Strkr's Flows replaces the common sales scenarios with native automation.

Salesforce flows

Powerful, admin-heavy, release-shaped.

Salesforce Flow Builder is capable. Every change requires a Salesforce admin and a release cycle. Strkr's Flows is sales-ops-editable with draft and test flow.

HubSpot workflows

Clean, bundled, limited at depth.

HubSpot workflows are credible for mid-market sales motions. Complex approval chains, custom-object automation, and deep audit are limited. Strkr's Flows scales to those depths with the same canvas.

Manual process

Universal, expensive at scale.

The default sales automation layer is "the rep remembers to do it." At scale that layer breaks. Strkr's Flows automates the breakable parts of the motion so the rep spends time on buyer conversations.

Strkr

Native, auditable, included.

Sales workflow automation is included on every paid Strkr tier. The Flows canvas, draft and test, run history, error handling, and permission-aware execution. The seat price covers it.

Build the sales motion once. The automation runs it on every deal.

Start a free trial, open the Flows canvas, drop in a trigger, pick the actions, test on a sample deal, and publish. The first Flow saves an hour the first week.

Start free trial See sales workflow
Common questions

What buyers ask about this feature.

What is sales workflow automation?

Sales workflow automation is the layer that turns sales events - stage change, meeting booked, email reply, signature received - into deterministic follow-ups, handoffs, approvals, and alerts. Instead of relying on reps to remember the next step, the system fires the step. In Strkr the automation is built on Flows, a visual canvas with versioning, test, audit, and permission-aware execution. The canvas is readable by a non-admin, so the sales ops lead builds and maintains automation without a developer release cycle.

What events can trigger a flow?

The common triggers are stage change, meeting booked, email reply, deal field update, inbound form submission, and signature event. Flows also triggers on time (scheduled or delay-based), on manual button click (a rep triggers a flow from the deal), and on sub-flow invocation (one flow calls another). Each trigger carries the event context - the deal, the owner, the fields that changed - which the Flow actions read.

How is it different from Zapier?

Zapier is a universal cross-system automation tool. Strkr Flows is sales-native automation. The differences are: Flows runs inside Strkr with permission-aware execution and audit on the deal, Flows has first-class triggers for the sales events (stage change, signature, approval), and Flows is included on every paid tier without a separate subscription. For cross-system automation outside Strkr, Zapier remains the right choice; for in-sales automation, Flows is the native fit.

Can we test a flow before publishing?

Yes. Every Flow has a dry-run mode. The sales ops lead picks a real deal from the record and runs the Flow against it. The dry-run shows what each action would do - the email that would send, the field that would update, the approval that would route - without actually executing. The pattern catches edge cases on real data before the Flow goes live. Draft Flows are also saved separately from the live version so the live motion stays stable while a change is in progress.

Does the Flow audit every run?

Yes. Every Flow run writes to the audit history with trigger event, input context, each action taken, the outcome of each action, and the overall success or failure. The audit is the forensics tool when a stakeholder asks "why did this deal receive the discount approval email." The audit also surfaces errors - a Flow that failed on a required field returns a visible error on the audit timeline rather than silently dying.

Is sales workflow automation included on every tier?

Yes. The Flows canvas, trigger library, action library, draft and publish, test with sample, run history, and error handling are included on every paid Strkr tier. Sub-flow composition, custom-trigger authoring, and multi-step approval routing are included on Pro and above. There is no separate automation SKU, no credit meter on Flow runs, and no per-execution charge.

Related features

Pair this with...

Sales Workflow Sales Process Automation Sales Process Workflow AI Workflow Automation Sales Proposal Automation AI Sales Automation

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.

Start free trial See pricing