Manage
Pipelines
Understand GrowthEngene pipelines, runs, watch lists, and workflow tracking.
Quick Answer
When To Use Pipelines
Use pipelines when a workflow needs staged tracking, repeated runs, review queues, or watch lists across jobs, leads, companies, or contacts.
Pipelines are the bridge between discovery and action. They can take data from jobs, posts, companies, people, and email discovery, then decide whether to store a lead, enroll a campaign, generate a draft, or send a resume email.
- Track workflow stages.
- Review run history.
- Watch selected targets.
- Organize long-running automation.
Common Pipeline Steps
The campaign and pipeline specs describe a modular pipeline engine. A pipeline step reads from a shared context object, writes output back, and hands the workflow to the next step.
- job_search: collect or select jobs.
- job_analyzer and resume_matcher: evaluate fit.
- company_lookup: resolve company identity and domain.
- person_lookup or decision_maker_search: find people.
- email_finder or hiring_team_email_resolver: resolve contact methods.
- store_lead: save useful contacts.
- enroll_campaign or send_resume_email: move to action.
Pipeline Types
GrowthEngene can model several high-value pipeline shapes. Each shape uses similar building blocks but starts from a different source and ends in a different action.
- Job Application: job search, resume match, company, person, email, and resume email or campaign enrollment.
- Lead Collection: company or job source, person lookup, email finder, and stored lead.
- Recruiter Outreach: recruiter/person lookup, company context, email finder, and campaign enrollment.
- Company Job Monitor: watched company job signal, match, people discovery, and outreach action.
- Post-Engagement Outreach: post signal, contact extraction, enrichment, and follow-up action.
Review And Debugging
Pipeline runs should explain what happened at each stage. When a run stops, the reason should point to a missing source, missing person, missing email, low confidence, missing sender, missing resume, policy block, or pacing block.
- Inspect run history and per-step output.
- Check whether the pipeline type matches the linked action plan.
- Confirm required steps exist for the intended send posture.
- Use watch lists when a workflow should continue monitoring selected targets.
Frequently Asked Questions
Are pipelines the same as campaigns?
No. Pipelines organize workflow progress, while campaigns manage outreach steps, messaging, and replies.
When should I link an Action Plan to a pipeline?
Link an Action Plan to a pipeline when discovery results should continue into enrichment, email finding, lead storage, campaign enrollment, or resume sending.
Why did a pipeline stop before sending?
It may have stopped because a required person, email, sender, resume, confidence threshold, suppression check, or pacing rule was missing.