Add to Workflow Action in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

The Add to Workflow action enrolls a contact into another workflow as part of an automation. Optionally pass the original trigger data along so the next workflow can personalize follow-ups.

The Add to Workflow action enrolls a contact into another workflow as a step inside the current one. It's how you chain automations together — for example, moving a contact from a lead-nurture flow into a post-booking flow once they schedule.

What it does

The action picks one target workflow and drops the contact into it at the start. With Pass Input Trigger Parameters turned on, the original trigger event data (form fields, appointment details, call info) carries over so downstream actions can use those values.

Why use it

Clean handoffs: move contacts between stages without manual re-enrollment.
Data continuity: trigger payload carries into the next workflow.
No extra trigger needed: the receiving workflow doesn't need its own start trigger.
Scales: chain as many workflows as your process needs.

How to configure it

Open Automation > Workflows.
Click + Create Workflow, then + Start from Scratch (or open an existing workflow).
Click the + icon and pick Add to Workflow.
Name the action — for example, Add to Appointment Follow-Up.
Pick the target workflow from the dropdown.
Optionally toggle Pass Input Trigger Parameters to carry the trigger payload across.
Click Save Action, save the workflow draft, run a test, then publish.

What gets passed

Pass Input Trigger Parameters carries the original trigger event data, not outputs from steps that ran later. Field availability depends on the trigger type:

Appointment trigger: contact name, email, phone, appointment date/time, calendar, status, appointment ID.
Form submission trigger: form name, submission timestamp, all submitted fields, contact details.
Survey trigger: survey name, submitted answers, contact details.
Inbound call/conversation trigger: contact details, source, timestamp, assigned user.
Custom event trigger: any custom fields defined in the event.

Example

A contact books on the calendar. The booking workflow's first action is Add to Workflow targeting Appointment Follow-Up with Pass Input Trigger Parameters enabled. The follow-up workflow uses the appointment date/time to send a confirmation, then a reminder.

Frequently Asked Questions

Can I add a contact to multiple workflows at once?

Each action targets one workflow. Stack multiple Add to Workflow actions in the same automation if you need to enroll into several at the same time.

What does Pass Input Trigger Parameters actually pass?

It passes the data from the original trigger event — the contact info, plus event-specific fields like appointment date or form values. It does not pass outputs from later actions.

How do I confirm the data carried over?

Run a test contact through the source workflow and check the merge field values in the receiving workflow's actions or the contact's activity log.

Does the receiving workflow need its own trigger?

No. The contact is enrolled at the start of the receiving workflow automatically. Build it starting with your first action.

Can I pass an API response from a Custom Code action?

Not directly. Pass Input Trigger Parameters only forwards the trigger payload. Store the API response in a contact field or custom value first, then enroll the contact into the next workflow.