Skip to article

Start email sequences when candidates join a job pipeline

Choose a scheduled start or automatically enroll new job-pipeline candidates, with individual timing and clear stopping rules.

Choose how your sequence starts

Once automation is configured for your workspace, open /tools/sequences and choose New sequence. Start now comes immediately after Name. Choose At a scheduled time to select a date, time, timezone and your own connected Gmail mailbox, then write Emails, choose People and review Launch.

Choose When an event happens, then use the Event dropdown above From to review the trigger, shown with an icon, title and short description. Candidate added to pipeline is currently the available event. Any job is the default for new automations and includes jobs created later in your workspace. Choose Selected jobs to limit the audience to specific pipelines. Saved automations keep their existing job scope. Write your emails and review the automatic audience before choosing Activate automation. This mode skips People because recipients join through the selected trigger.

New additions get their own follow-up schedule

The first trigger is Candidate added to a job pipeline. Creating a candidate alone or moving someone between stages does not start this automation. Existing pipeline members are not enrolled when you activate it.

Choose an immediate first email or a delay, plus your sending days, hours and timezone. Immediate means the earliest allowed sending time after the addition is processed; it does not promise delivery at that exact moment. Each person gets their own follow-up timing, counted from their previous successful email.

Hover, focus or tap the info icons beside the job choices, Sending days and Sending hours for details. Event delays count calendar days; emails due outside the selected days or hours wait for the next allowed sending time in your chosen timezone.

A person is enrolled at most once per automation. Removing and re-adding a candidate, adding them to several selected jobs, or retrying an event will not send duplicate introductions. An email address already running in another sequence is skipped instead of starting overlapping outreach.

See who joined and why someone was skipped

Open the automation to review People and Activity. Skipped additions include a reason, such as a missing usable email, an opt-out, an unavailable mailbox or an existing sequence. Emails use the mailbox selected for the automation, rather than the account of the person who added the candidate.

Pause the automation to stop accepting new additions and hold its existing follow-ups. Resuming accepts new additions from that point forward; additions from before you resumed that were not already enrolled do not catch up automatically. People already enrolled keep their approved emails and timing. Pause before changing an active automation’s job scope, sender or sending hours. Once a sequence has enrolled someone, create a new sequence if you want to switch between scheduled and event starts.

Stop for replies without stopping the automation

Stop follow-ups when the recipient replies. Otherwise, finish after the final email. These rules apply separately to each person; completing one person’s emails does not deactivate the automation.

An ordinary reply stops that person’s current sequence and does not create an organization-wide block on later sequences. Explicit opt-outs, permanent bounces and manual address holds remain broader protections. Reply detection depends on the connected mailbox. Meeting-booked stopping is not included in this version.

Workspace automation and sending must be configured before live delivery. Activating an automation alone does not enable Gmail sending, and an On hold status still means delivery is disabled. Sending limits, connection problems and background processing can delay emails.

← All articles