Launching a sequence to a candidate

Last updated: August 3, 2026

Once a flow is built, adding a candidate to it is what actually starts their outreach. This article covers how to enroll a candidate (one at a time or in bulk), situations where Kula won't let you add someone, and what happens when a flow step needs your review before it can go out.

Who can do this: Any user with flow-related permissions can add an existing candidate to a flow — this doesn't require permission to create new contacts, since you're enrolling a profile that already exists in Kula, not creating one.

Where to find it: A candidate's own profile (More → Add to Flow), the Kula Everywhere LinkedIn extension, or a bulk selection from a Flow or Project candidate list.


Adding a candidate to a flow

From a flow's candidate list, Add candidates gives you three ways to bring candidates in:

  • Kula Everywhere — source and add a candidate directly from their LinkedIn profile using the Kula Everywhere Chrome extension, once your flow is active. See Creating an outreach sequence (link to be added) for how the LinkedIn path works.

image.png
  • Candidates — select from candidates who already exist in Kula and add them to the flow directly, without needing to source them again.

image.png
  • CSV — upload a CSV file to add a batch of candidates to the flow at once, useful if you're bringing in a list you've already put together outside Kula rather than sourcing them one at a time.

image.png
  • You can also add a candidate to a flow one at a time from their own profile via More → Add to Flow, or in bulk from a Flow or Project candidate list by choosing a page size (20, 50, or 100) or Select All, then applying Add to a Flow as a bulk action across everyone selected.

If you're adding an existing candidate to a flow you just created for the first time, you may be redirected to the Contacts page to find and select them rather than staying in the flow itself — that's expected current behavior, not an error on your end.


When a candidate can't be added

  • If a candidate is already part of the job your flow is linked to — for example, they're sitting in the Prospect stage — Kula may block adding them to that flow.

  • The reasoning is that being on the job already implies they've consented and shown interest, so there's no need to run them through an outreach sequence asking again.

  • If you hit this, try the recommended order instead: add candidates to a Project first, then to a Flow, and only then formally onto the Job — rather than adding them to the job first.


AI-personalized steps: review before send

If a flow step has AI personalization turned on, Kula generates a draft message automatically for every candidate who reaches that step — you don't need to trigger this manually, and it also happens automatically for candidates added later.

  • What the AI uses: primarily LinkedIn enrichment data — profile summary, work experience, and skills. If that data isn't available, it falls back to more generic input, and personalization quality drops as a result. It's worth making sure LinkedIn enrichment is complete before a candidate reaches a personalized step.

  • What you can configure: the role being hired for, key focus areas for the message, and a preferred tone (Professional, Casual, Enthusiastic, or Persuasive).

  • Version limits: each candidate gets up to 3 message versions — one initial draft plus two regenerations. After that, regeneration is disabled, though you can still manually edit the message.

  • Review is required, one at a time: a personalized message has to be reviewed and approved by a recruiter before it sends. There's currently no bulk-approve option.

  • What happens if it's not approved: if a candidate reaches a personalized step without an approved message, the sequence automatically pauses for that candidate at that step and holds. Once you approve it, the flow resumes and sends on schedule.


Good to know

  • Adding an existing candidate to a brand-new flow may redirect you to Contacts to find them — that's current expected behavior, not a bug.

  • A candidate already active in the flow's linked job can be blocked from being added to that flow. If this happens, try adding them to a Project first, then the flow.

  • AI-personalized steps pause automatically if a message isn't approved yet. At scale, manual review capacity — not message generation — is the real bottleneck.

  • Bulk-adding candidates to a flow is supported from Flow or Project candidate lists, with page sizes up to 100 or a Select All option.

FAQ

  • How do I add one candidate to an existing flow? Open their profile and choose More → Add to Flow, or use the Kula Everywhere Chrome extension from their LinkedIn profile once the flow is active.

  • Can I add many candidates to a flow at once? Yes — from a Flow or Project candidate list, select a page (up to 100) or Select All, then apply Add to a Flow as a bulk action.

  • Why can't I add this candidate to our flow? If they're already part of the job the flow is linked to, Kula may block it since that's treated as them already having consented or shown interest. Try adding them to a Project first, then the flow.

  • Does someone need to manually write a personalized message for every candidate? No — if AI personalization is enabled on a step, Kula generates a draft automatically for each candidate. You still need to review and approve it before it sends.

  • What happens if I don't approve a personalized message in time? The sequence pauses automatically for that candidate at that step and waits. Nothing sends until you approve it — then it resumes on schedule.

Need help?

If you have questions or need assistance, reach out to us at support@kula.ai or use the in-app chat.