CompanyManifestoCustomer storiesShip logCareersSandboxPricing
Log in
Product · Workflow Engine

Build the playbooks. Let agents execute them.

Multi-step jobs, branching logic, approval queues, escalation rules, quiet hours, CRM updates. You design the workflow; AI agents execute the steps that need judgement; rule-based steps run themselves.

Traditional workflow tools (Zapier, n8n) execute rules you wrote. ScendCore workflows mix rules with agent steps — an agent decides what to do at a decision point, the workflow handles the deterministic parts around it. Less brittle, less authoring.

See it in action

A real workflow — with one AI decision step inside it.

Trigger fires when a form is submitted. Rule-based branch routes ICP-fit leads to Emma, who decides where each one goes next. Hybrid by design — rules where rules work, agents where judgment is needed.

app.scendcore.com / workflows / qualify-inbound
Qualify Inbound LeadLive · 423 runs / 7 days
v12 · auto-saveEdit policy
Form submitted
Trigger · webhook
ICP match?
Branch · rule
Emma decides
AI step · classify intent
Emma
Long-term nurture
Add to Mark's cadence
Book meeting
Sophie · calendar
Approval queue
Routes to AE · 4h SLA
Selected · AI stepEmma decides what to do
Agent
Emma · Lead Engagement
Autonomy
Auto (within policy)
Input context
Form fields · ICP score · history
Possible outcomes
High valueMid valueLow value
Capabilities

Build governed automation that AI can execute safely

Capability
Purpose
Visual workflow builder
Drag-and-drop builder with 19+ node types. Author in minutes, not weeks.
Multi-step agent jobs
Coordinate complex tasks across multiple agents — Mark prospects, Emma qualifies, Sophie books.
Branching + conditions
Reply-aware logic. The workflow picks the right branch based on what happened, not just what you predicted.
Approval queues
High-risk steps pause for human approval. Mobile-friendly approval UI; SLA timers; auto-escalate on stall.
Escalation rules
Triggers human takeover when the agent hits its policy boundary or risk threshold.
Quiet hours + business hours
Workflows respect timezone-aware quiet hours per contact. No 2am SMS to a prospect in Sydney.
CRM writeback
Every workflow step that touches your CRM logs as a native activity with full attribution.
Wait states
Pause until a signal lands ("when this deal hits stage Negotiation" / "when 7 days pass without reply").
Detail

What the engine handles for you

AI-native

Agent steps are first-class

A workflow node can be "let Emma decide" — not just "run this rule." The agent reads context, takes the action, hands off to the next step. Workflow + intelligence in one tool.

  • "Agent decides" as a node type
  • Per-step autonomy controls
  • Outcome-aware branching from agent decisions
  • Audit log per step with inputs + result
Governed

Built for compliance + RBAC

Every workflow is versioned. Every approval is logged. RBAC controls who can author what. Workflow changes diff like code; approvals required before promotion to production.

  • Version history + diff per workflow
  • Per-workflow RBAC (who can edit, who can run)
  • Production / staging environments
  • Approval-to-promote workflow changes
Extensible

Custom steps via Skills

Need a step that calls your internal API? Author a Custom Skill in the developer platform; the workflow calls it like any built-in node.

  • Skill-as-node — any HTTPS endpoint
  • Per-skill auth (JWT, mTLS, OAuth)
  • Skill test harness with preview
  • Marketplace of community skills (coming Q3)
Pre-built

18+ starter templates

Common motions ship as templates — cold outbound, warm follow-up, recovery, expansion, renewal risk save plan. Clone, customise, run.

  • Cold outbound · warm follow-up · recovery
  • Renewal risk save plan
  • Expansion intent surface
  • Custom templates per industry
Pricing

Included from Starter

Solo gets basic automations; Starter unlocks the full Workflow Engine with multi-step + approvals. Pro adds advanced orchestration.

Available from
Starter
from $249/mo
Rule-based steps (CRM updates, branching) are free. Agent decision steps consume AI Credits. External SMS/voice/data steps consume Wallet.
See full pricing →
FAQs

Common questions

How is this different from Zapier or n8n?
Zapier and n8n execute rules you author — every branch must be written explicitly. ScendCore workflows let an agent decide what to do at a decision point, so you author the structure once + the agent adapts. For deterministic glue (push X to CRM when Y happens), they're equivalent; for judgement steps, this is much less brittle.
Can I import existing workflows from Outreach or Salesloft?
Yes — importers convert sequence step content + cadence timing to ScendCore workflows. AI reviews each step; you approve before they go live.
How are workflow approvals routed?
Per-workflow approver lists with role-based fallback (e.g. "Manager of the rep who triggered" or "Whoever's on duty"). Approvers get mobile-friendly notifications via Slack, email, or push.
What's the difference between a workflow and a "skill" on the developer page?
A workflow is the structure of work — multi-step orchestration. A skill is a single tool an agent can call within a step ("look up NetSuite," "check inventory"). Workflows are authored by RevOps; skills are authored by engineering.

Design the playbook. Then go to lunch.

Multi-step, governed, AI-native. The workflow runs whether you're watching or not.

Built by a team that's delivered for
© 2026 ScendCore, operated by Sprintmore LLC · Frisco, Texas, USA
Workflow Engine — Governed revenue automation | ScendCore