Building Campaign Flows

The Editor tab is where campaign automation is built in Leadpush. Each campaign is a workflow graph made up of one trigger, connected actions, and exit paths.

Open the campaign editor

Open a campaign from Messaging -> Campaigns, then select the Editor tab.

This view shows the full workflow canvas for the current campaign.

Start with the trigger

Every campaign begins with a trigger. Leadpush supports campaign triggers for:

• Event
• Contact Created
• Segment Entered
• Segment Left

Depending on the trigger type, you can configure extra details such as:

• the event name
• the segment that should trigger entry
• how often the same contact can enter or re-enter the campaign

For event and segment triggers, Leadpush also exposes frequency controls such as:

• One time
• Every re-match
• At fixed intervals

Event triggers can also be configured to run on every matching event.

Control the campaign entry rate

Event, contact-created, segment-entered, and segment-left triggers can throttle how quickly contacts begin the campaign. Choose a maximum per minute, hour, or day, and optionally limit entry to selected days and local-time hours. Contacts that arrive outside the window wait until its next opening.

For segment-entered triggers, the same entry rate applies to contacts already in the segment when the campaign is first published and to contacts that enter the segment later. A contact can have only one throttled entry waiting at a time.

The campaign Metrics tab includes a live Entry throttle panel. It shows how many contacts were accepted, started, are still waiting, or were skipped, along with the next scheduled entry, the end of the current backlog, and the next available rate slot. An overdue warning means a reserved entry is more than one minute late and the campaign queue workers should be checked. These operational values are not affected by the reporting date range.

For an initial segment audience, the panel also reconciles the snapshot total against processed, accepted, waiting, and skipped contacts. Totals remain visible after the queue drains or the campaign stops and are labeled with the time tracking began.

If a Segment Entered campaign includes existing contacts, Requeue current segment creates a fresh snapshot after the campaign is running. Every contact is checked against the published frequency rule before receiving a throttle slot. For example, a One time campaign skips contacts with any previous real execution, while contacts whose earlier reservation was cancelled before entry can be queued again. Stopping the campaign cancels an active requeue; restarting never resumes it automatically.

Add actions to the workflow

Once the trigger exists, you can add actions and connect them through the graph.

The available action types include email, event, contact update, integration, timing, branch, and exit nodes. For detailed settings and behavior for every node, see the Campaign Nodes reference.

Use these building blocks to define both the business logic and the delivery logic of the campaign.

Configure email steps

The Send Email action lets you attach content directly to the workflow.

From that step you can:

• create or attach a template
• edit the content later in the template editor
• choose a verified from address
• define the subject line

This makes the email step part of the campaign instead of a separate newsletter workflow.

Configure event and contact actions

Use Send Event when the workflow should emit a named event, optionally with a JSON payload.

Use Update Contact when the workflow should change contact attributes during execution.

These actions are useful when the campaign needs to update internal state as contacts move through the flow.

Add branching and timing controls

Campaigns can do more than send a single message. Use branch and timing nodes when the flow needs logic:

• Time Delay to wait before the next action runs
• Time Window to restrict execution to an allowed time range
• If / Else to split contacts based on segment-style conditions
• Random Cohort to route contacts into percentage-based paths
• Exit Campaign to stop processing cleanly

Together, these tools let you build onboarding flows, re-engagement sequences, event-driven automations, and branching lifecycle campaigns.

Trigger edits after publish

Once a campaign has been published, trigger details become locked. Leadpush still allows frequency and entry-rate settings to be updated through a new campaign version, but the core trigger definition should be treated as stable once the campaign is live. Existing waiting entries keep their original schedule; the new rate applies to future entries after the update is published.

Best practices

• Finalize the trigger first so the rest of the workflow reflects the right entry condition.
• Keep branch names and campaign descriptions consistent with the real business goal of the automation.
• Use delays and time windows intentionally so contacts are not advanced at the wrong time.
• Add an exit path anywhere the campaign should stop instead of letting the graph become ambiguous.
• Validate send-email steps before publishing so the campaign is not blocked by missing content.

Related guides

• Managing Campaigns
• Campaign Nodes
• Publishing and Simulating Campaigns
• Campaign Reporting
• Layouts
• Assets