Spojit
Sub-workflows

Build once.
Call it anywhere.

Call one workflow as a step inside another. Build a reusable building block once, give it inputs and outputs, and use it across every workflow that needs it, instead of copy-pasting the same logic and maintaining it in ten places.

  1. New order
    trigger
  2. Enrich customer
    call workflow
  3. Create invoice
    action
call
called by 4 workflows
01Look up CRM
02Score account
03Return enriched record
How it works

Compose, don't copy-paste

01

Build a workflow

Create a focused workflow that does one job well, with clear inputs and a clear result.

02

Call it from another

Drop a call-workflow step into any other workflow and pass it the inputs it expects.

03

Update it in one place

Improve the building block once, and every workflow that calls it gets the change.

Capabilities

Composition that scales

Call as a step

A whole workflow becomes a single node in another one, so complex logic stays tidy.

Inputs and outputs

Pass data in and read a clear result out, like calling a function with a defined contract.

Reuse everywhere

Use the same building block across as many workflows as you like, with no duplication.

One place to update

Fix a bug or improve the logic once, and every caller picks it up automatically.

Nest deeply

Building blocks can call other building blocks, so you compose larger systems from small parts.

Test in isolation

Run and verify a sub-workflow on its own before it is used inside the bigger picture.

Use cases

Shared logic, one source of truth

Common subroutines

Enrich a customer, validate an address, or format a message once, then reuse it everywhere.

Standardize a process

Make sure every workflow handles a shared step the exact same approved way.

Break up a big flow

Split a sprawling workflow into named pieces that are far easier to read and change.

Team building blocks

Share reusable workflows across the team so everyone builds on the same foundation.

The difference

Sub-workflows vs copy-paste

Change shared logic in one place, instead of hunting down every copy of it.

Use a sub-workflow when

  • The same logic appears in several workflows
  • You want a single place to maintain it
  • A large workflow is easier to reason about in pieces

Copy-paste means

  • The same logic duplicated in many places
  • Fixing one bug in all of them at once
  • Copies drifting out of sync over time

Build reusable workflows

Start free and turn a workflow into a building block you can call anywhere. No card needed.