Feature · Create Workflow

How to create a workflow in Strkr Flows on day one.

The practical guide to building your first workflow in Strkr Flows. Triggers, conditions, actions, testing, publishing, and the starter patterns a RevOps lead ships before Monday.

Start free trial See pricing

The five-step build

From empty canvas to running automation.

Creating a workflow in Strkr Flows is a five-step build: pick a trigger, build the conditions, choose the actions, test with a sample record, and publish. Each step has specific choices that affect the Flow quality. The sections below walk the five steps with the choices that produce a Flow worth running in production.

Step 1

Pick a trigger.

Open the Flows admin surface, click new workflow, and pick the triggering event from the dropdown. Options include CRM record created or updated, lead captured, email replied, SMS inbound, meeting booked, project transitioned, campaign enrolled, scheduled time, custom field changed, and more than sixty others.

Step 2

Build the conditions.

Add condition nodes to filter when the Flow should actually run. Pick a field on the triggering record, pick an operator (equals, contains, greater than, in list), pick a value or reference another field. Nest conditions up to three levels deep with AND and OR groups.

Step 3

Choose the actions.

Add action nodes for what the Flow should do when the trigger fires and conditions match. Create or update a record, send an email, send an SMS, post to Slack, trigger a Strkr AI step, call a webhook, enroll in a campaign. Chain actions with the output of one feeding the next.

Step 4

Test with a sample record.

The preview mode runs the Flow against a sample record non-destructively. The canvas shows which conditions evaluate true, which actions would fire, and what the AI step would return. Logic errors surface before customers see them.

Step 5

Publish.

Click publish. The new version takes over new runs; in-flight runs finish on the version they started on. Each publish is numbered so you can see what changed between versions and roll back with one click.

Review loop

Watch the first runs land.

After publish, watch the first ten runs in the audit log. Confirm the conditions evaluate as intended. Confirm the actions fire as intended. Adjust the Flow if the real-world payload shape surprises the logic. The first-week review loop catches the few cases the sample record did not cover.

Picking the right trigger

The choice that shapes everything downstream.

The trigger choice shapes the whole Flow. An event trigger fires once per matching event; a scheduled trigger fires on a cadence; a conditional trigger fires when a record enters a state. Picking the wrong trigger shape produces either a Flow that misses runs or a Flow that fires too often. Below are the shapes and when each one fits.

Event trigger

Fires once per matching event.

A deal moves to Proposal; the Flow fires once. A form submits; the Flow fires once. Event triggers are the default for most workflows. Pick the event most tightly coupled to the business moment you want to automate.

Scheduled trigger

Fires on a cadence.

A Monday 8am rollup. A nightly reconciliation. A 7-day-ahead reminder. Scheduled triggers run on a cron expression respecting the tenant timezone. Pick scheduled for anything that needs to happen on a clock rather than on an event.

Record state trigger

Fires when a record enters a defined state.

A deal has been in Proposal for 10+ days with no activity. An account health score drops below the threshold. A contact passes a nurture milestone. Record-state triggers are a hybrid of event and query; they fire when a condition becomes true, not when a field happens to change.

Webhook trigger

Fires on an inbound HTTP call.

A third-party system that lacks a native integration can trigger a Flow via an inbound webhook. The webhook payload becomes the trigger context; the Flow continues as if the event came from inside Strkr. Pick webhook for custom or legacy integrations.

Manual trigger

Fires when a user clicks a button.

Some workflows exist to let a rep run a action on demand. A deal-specific brief generator. A one-click outreach draft. A custom report. Manual triggers appear as buttons on the record view; the Flow runs when clicked.

Trigger composition

A Flow can have more than one.

A Flow can accept multiple triggers (deal updated OR scheduled daily) to handle both event-driven and scheduled runs with the same action chain. The canvas shows each trigger with its own entry point feeding the same downstream logic.

Building clean conditions

The branching logic that reads like English.

Conditions filter when the Flow should actually run. Clean conditions read like a business rule rather than like a boolean expression. The condition builder uses form inputs so the output reads back as a sentence on the canvas. The sections below cover the patterns that produce readable conditions.

Single condition

One field, one operator, one value.

The simplest condition picks a field, an operator, and a value. Deal amount is greater than 25,000. Contact country equals United States. Lead score is greater than 60. Single conditions handle most routing decisions.

AND group

All must be true.

An AND group requires every condition inside to evaluate true for the group to pass. Deal amount above 25k AND stage is Proposal AND close date is in current quarter. The group reads as a readable rule and matches how business logic actually gets stated.

OR group

Any can be true.

An OR group passes if any condition inside evaluates true. Lead source is paid search OR lead source is content download. OR groups handle the any-of-these-channels-count pattern that comes up in routing and reporting.

Nested logic

AND of ORs, or OR of ANDs.

Three levels of nesting cover almost every business rule. (Deal amount above 50k) AND (stage is Proposal OR stage is Negotiation) AND (close date is in current quarter). The canvas shows the nested structure visually; the reviewer can confirm intent without parsing parentheses.

Reference another field

Compare one field to another.

Conditions can reference another field on the same record rather than a hard-coded value. Close date is after start date. Discount percent is greater than owner discount cap. The field-to-field reference catches rule violations the hard-coded version misses.

Keep it simple

Flat beats nested when possible.

When a nested condition reads clumsily, split the Flow into two Flows instead. A single Flow with three levels of nesting that nobody can read is worse than two Flows with simple conditions. Readability is a quality metric, not a code-golf category.

Choosing the right actions

What a Flow should actually do when the conditions match.

Actions are where the Flow produces work. Each action does one thing (create a record, send a message, update a field, call an AI step). The output of one action feeds the input of the next. Clean action chains are short and specific; messy action chains try to do too much in one Flow.

Create or update

Write to any Strkr record.

Create a contact, lead, account, deal, project, issue, campaign enrollment, task, note, or custom field value. Update any of the same. The action configuration maps Flow context fields to record fields; the write happens with the owner permissions.

Send a message

Email, SMS, Slack, native.

Send an email through Gmail or Outlook via per-user OAuth. Send SMS through Strkr Messaging. Post to Slack through the connected app. The message content pulls from a template with Flow context variables; the delivery is logged.

Strkr AI step

A model-powered action in the chain.

The AI step takes an input (record, text, context) and returns an output (classification, draft, summary, score). The output feeds the next action. Example: AI drafts a follow-up email; the next action places the draft in the rep queue.

Call a webhook

Outbound POST to any URL.

For systems without a native connector, a webhook action POSTs a JSON payload to the target URL. The payload shape is configurable. Response data can feed subsequent Flow steps for round-trip integrations.

Wait

Pause for a duration or until a condition.

A wait node pauses the Flow for a configured duration (five minutes, two hours, three days) or until a condition becomes true (reply received, record field changed). Pattern applies to nurture cadences and multi-step follow-ups.

Code step

For the ten percent that needs it.

A code step runs a short JavaScript or Python function with the Flow payload as input. Sandboxed with resource ceilings and admin-approved credential grants. Use for bespoke parsing, complex transforms, or legacy integrations without a native connector.

Starter Flows for day one

The six workflows a RevOps lead ships first.

Below are the six starter workflows a RevOps lead typically ships in the first week on Strkr Flows. Each one is a documented pattern with a visible payback. Enable them in the recommended order; each pays back fast enough to buy momentum for the next.

Flow 1

Inbound lead routing.

Trigger: form submitted. Conditions: service area match, lead score above threshold. Actions: enrich firmographics, assign to AE by territory, create Slack ping, generate prep brief. Payback: SLA on inbound drops from thirty minutes to under one minute.

Flow 2

Stale deal nudge.

Trigger: scheduled daily. Conditions: deal past qualification stage, no activity in 10+ days. Actions: Strkr AI drafts a nudge referencing last meeting note, drops in AE queue. Payback: deals that would have slipped get touched; slip rate drops thirty to fifty percent.

Flow 3

Meeting prep brief.

Trigger: calendar event booked 24 hours out, external attendee. Actions: AI reads account record, pulls recent news, drafts talking points, attaches to the calendar event. Payback: AE research hour disappears; first-call quality lifts.

Flow 4

Closed-won handoff.

Trigger: deal moves to Closed Won. Actions: spawn implementation project from template, draft welcome email, create Google Calendar kickoff event, ping CSM in Slack with handoff brief, write commissions ledger. Payback: two-day handoff coordination collapses to two minutes.

Flow 5

Churn-risk escalation.

Trigger: health score drops below threshold OR usage drops week-over-week by 30%. Actions: AI drafts save-motion brief, assigns task to CSM, pings exec sponsor in Slack. Payback: save motion starts before the exec call, not after.

Flow 6

Monday pipeline digest.

Trigger: scheduled Monday 7am local. Actions: AI rolls up the week forecast per rep, flags red deals, computes variance against last week, drafts narrative per manager, sends tailored emails. Payback: standup prep done before the first coffee.

Flows ships on Pro. The six starter workflows above are editable templates in the trial.

Create a workflow this afternoon. Watch the first run land. Add the next starter tomorrow. The ritual of continuous automation begins with the first Flow.

Start free trial See AI workflow automation

Common questions

What buyers ask about this feature.

What are the five steps to create a workflow in Strkr?

First, pick a trigger from the dropdown (event, scheduled, record state, webhook, or manual). Second, build the conditions using form inputs that pick a field, an operator, and a value. Third, choose the actions that fire when the conditions match (create or update a record, send a message, call a Strkr AI step, trigger a webhook, add a wait, or run a code step). Fourth, test with a sample record using the preview mode, which runs the Flow non-destructively and shows which conditions evaluate true and which actions would fire. Fifth, publish and watch the first ten runs in the audit log to confirm the real-world payload matches your assumptions.

Which trigger shape should I use?

Pick an event trigger (fires once per matching event) for most workflows. Deal moves to Proposal, form submitted, email replied, SMS inbound. Pick a scheduled trigger for anything that happens on a clock rather than on an event: Monday rollup, nightly reconciliation, 7-day-ahead reminder. Pick a record state trigger when the Flow should fire when a record enters a defined state (deal stuck in Proposal for 10+ days with no activity, account health below threshold). Pick a webhook trigger for custom or legacy integrations. Pick a manual trigger for actions the rep runs on demand with a button on the record view. A Flow can accept more than one trigger for workflows that need both event and scheduled behavior with the same action chain.

How do I write conditions that are easy to review?

The condition builder uses form inputs rather than expression syntax, so the output reads back as a sentence on the canvas. Pick a field, pick an operator appropriate to the field type (equals, contains, greater than, in list), pick a value or reference another field. Combine with AND and OR groups up to three levels deep. When a nested condition reads clumsily, split the Flow into two Flows with simple conditions instead; readability is a quality metric. Reference another field (close date after start date, discount percent above owner cap) catches rule violations the hard-coded version misses.

What actions can a Flow trigger?

Create or update any Strkr record (contact, lead, account, deal, project, issue, campaign enrollment, task, note, custom field). Send an email through Gmail or Outlook, send SMS through Strkr Messaging, post to Slack through the connected app. Call a Strkr AI step for classification, drafting, summarization, or scoring. Call an outbound webhook to a system without a native connector. Add a wait node to pause for a duration or until a condition becomes true. Add a code step (short JavaScript or Python function, sandboxed with resource ceilings) for the ten percent of workflows that need bespoke logic. Every writable surface in the product plus every native integration is a callable action.

How does the preview mode work?

The preview mode runs the Flow against a sample record non-destructively: no actual writes happen, no messages send, no AI steps spend credits. The canvas shows which conditions evaluate true, which actions would fire if the Flow were live, and what the AI step would return. Logic errors surface before customers see them. The preview is the first-line test; the second-line test is the first-week review of real runs in the audit log, which catches the few payload shapes the sample record did not cover.

What should I build first?

Build the six starter workflows in order: inbound lead routing (form fill to assigned AE in under a second), stale deal nudge (daily draft for deals quiet 10+ days), meeting prep brief (brief lands 24 hours before every external meeting), closed-won handoff (signature triggers project creation, welcome email, CSM task, commissions write), churn-risk escalation (health score drop triggers CSM save-motion draft), and Monday pipeline digest (rollup lands in the sales channel before standup). Each one pays back fast enough to buy momentum for the next. The six together typically save a mid-market revenue team twenty to forty rep-hours a week by the end of the first month.

Related features

Pair this with...

AI Workflow Automation CRM Automation Content Workflow Software AI Workflow Builder

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