Build and Publish a Journey
Updated 2 weeks ago
Build and Publish a Journey
Configure journey steps, review settings, and publish the workflow when it is ready to run.
Use the journey builder when you want to turn a draft into a workflow that can run for donors, trip participants, or recipients. The builder lets you edit steps in a simple list or in a visual map.
Journey builder in simple mode with the step list, selected step editor, and publish controls.
Understand journey status
Journeys use status to protect live workflows.
Draft journeys are editable and do not run yet.
Active journeys can process matching records.
Paused journeys stop processing until they are resumed.
Archived journeys are kept for history and are no longer part of active work.
When a journey is active or paused, the workflow structure is protected. Use Duplicate to Edit when you need to make a new draft based on a live journey.
Build in simple mode
Simple mode is best when you want to read the workflow as plain steps.
Open the draft journey.
Use the left step list to choose the step you want to edit.
Configure the selected step in the editor.
Use Add step, Insert step, or Add branch when the workflow needs another action.
Review the readiness banner as you work.
Step changes autosave while you edit. If a save is still in progress, wait for the save state to finish before leaving the builder.
Use the visual map
Use the visual map when the journey has branches or when you want to inspect the path at a glance.
Journey builder visual map with a payment recovery workflow and branch paths.
In visual mode, you can:
drag steps on the canvas,
add a step from the palette,
insert a step between two existing steps,
select a step to edit it,
review branch labels and path traffic when journey history is available.
Choose the right step
Use the step type that matches what you want the journey to do next.
Send message: Send an email or SMS from a shared source template, with optional copy changes for this step.
Send handwritten card: Request a Handwrytten card when your account and the journey audience support it.
Delay: Wait for hours, days, or weeks before the next step.
Condition: Split the journey into branches based on field values.
Tag: Add or remove a tag.
Update field: Update a donor, participant, or recipient field.
Create task: Create a staff task and optionally assign it.
Goal: Mark the journey outcome when a condition is met.
Notification: Notify staff groups with an internal message.
Configure messages
When a journey sends a message, select a saved email or SMS template in the journey step editor using Journeys templates. This keeps common copy reusable across journeys.
Use an override only when this step needs different copy from the shared source. Email steps can override the subject and body. SMS steps use one message body.
SMS options only appear when SMS is supported for your account. SMS delivery also depends on phone numbers, opt-in status, and your SMS provider setup.
Review settings
Use Settings when you want to confirm how the journey should behave before publishing.
Settings can include:
journey name and staff context,
whether a person can re-enter after a previous run,
goal and exit-rule summaries,
failure alert preferences,
delivery window notes,
safety limit notes.
Re-entry affects how people can enter future runs. Use the delivery health notes to record expectations your team should review before publishing.
Publish the journey
Publish only when the journey is ready for real records to enter.
Open the draft journey.
Review the readiness banner or Settings checklist.
Fix any required items.
Select Publish.
The checklist can flag missing triggers, missing message content, SMS setup issues, incomplete delay timing, branch paths, staff notification details, and other required step configuration. Gratona performs a final activation check when you publish.
After publishing, people enter the journey only when the selected trigger happens and they match the journey criteria.
Pause or resume a journey
Use Pause when a live journey should stop processing while your team reviews it. Use Resume when the journey should continue.
When you need to change the structure of a live journey, duplicate it, edit the new draft, publish the replacement, and then pause the old version when your team is ready.