Workflow Builder Walkthrough in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

The Sparkforge Workflow Builder uses an infinite canvas with triggers, actions, drip and conditional logic, stats view, and version history. Save and Publish are independent — both must be set for a workflow to run live.

The Workflow Builder runs your automations. This is the layout, the controls, and the practical tips for keeping workflows clean.

Infinite Canvas

Pan freely across the workflow. Use Fit to Screen and zoom controls in the bottom-left, and the Minimap in the bottom-right to navigate large workflows.

Keep workflows small enough to fit on one screen. Group related actions and use clear names. Big sprawling workflows are hard to debug.

Workflow Switcher

Open the Workflow Switcher from the left panel or press Shift + W. Search or scroll to jump between workflows without leaving the builder.

Add a Trigger

  1. Click Add New Trigger.
  2. Pick a trigger type (Contact Added, Appointment Booked, etc.).
  3. Configure the conditions.

Every trigger fires independently when its conditions are met. If you don't want overlap, isolate triggers in separate workflows.

Add an Action

  1. Click the + on the workflow line.
  2. Pick an action (Send Email, Assign to User, etc.).
  3. Configure the details.

Advanced action types

  • Drip Actions — slow contacts down between steps.
  • Conditional Actions — branch based on data.
  • Goal Actions — let contacts skip ahead when criteria are met.

Always rename actions. Default labels make canvas view useless.

Stats View

Toggle Stats View in the top-left to overlay communication stats on each action. Click any number to drill in. Stats persist for deleted actions, so historical data stays.

Test the Workflow

  1. Click Test Workflow.
  2. Pick a contact.
  3. Click Run Test.

Test mode is imperfect — re-running with the same contact can produce odd results. For real validation, publish and use a fresh test contact live.

Save vs Publish

These are independent. A workflow can be saved-but-draft (won't run) or published with unsaved changes (running on the last saved version).

  • Save — top-right, hit it whenever the red unsaved-dot appears.
  • Draft / Publish toggle — controls whether the workflow actually executes.

Contacts in waiting steps stay put when you toggle to draft. They resume on publish.

Version History

Click the History icon top-right to see prior versions. Back to Builder returns to editing.

Best Practices

  • Avoid loops. The builder blocks visual loops but not logical ones built across actions.
  • Keep workflows screen-sized. Split big logic into separate workflows linked by Add to Workflow.
  • Name everything clearly — future you and your team will need it.

Frequently Asked Questions

What happens to contacts in a workflow when I switch it to draft?

They freeze at their current step. When you re-publish, they resume from where they were.

Can a contact be in multiple workflows at once?

Yes. Use the Add to Workflow action to enroll a contact in additional workflows.

How do I send data to an external app?

Use the Webhook action. Configure the URL, method, headers, and body.

What's a Goal Event for?

It lets a contact jump ahead in the workflow when they hit a specific outcome — useful for skipping nurture steps once someone converts.

Frequently Asked Questions

What happens to contacts in a workflow when I switch it to draft?
They freeze at their current step. When you re-publish, they resume from where they were.
Can a contact be in multiple workflows at once?
Yes. Use the Add to Workflow action to enroll a contact in additional workflows.
How do I send data to an external app?
Use the Webhook action. Configure the URL, method, headers, and body.
What's a Goal Event for?
It lets a contact jump ahead in the workflow when they hit a specific outcome — useful for skipping nurture steps once someone converts.

Was this article helpful?