Workflows

LinkedIn Posts Automation

Use GrowthEngene to discover relevant LinkedIn posts, identify contacts, prepare drafts, and manage outreach.

Quick Answer

GrowthEngene LinkedIn Posts workflows help find relevant posts, extract useful signals, identify contacts, and support outreach based on post activity.

What The Workflow Does

LinkedIn Posts automation monitors post opportunities, evaluates relevance, stores contacts, and can prepare outreach drafts or email discovery steps based on configured rules.

This workflow is designed for posts that contain hiring signals, apply instructions, direct emails, phone numbers, WhatsApp details, external apply links, or useful company/poster evidence.

  • Find relevant LinkedIn posts.
  • Classify useful and not useful opportunities.
  • Extract direct contacts such as emails, phones, mailto links, apply links, and LinkedIn profile/company URLs.
  • Create personal and agency draft variants where configured.
  • Queue email discovery when no direct email exists and poster/company evidence is strong enough.
  • Track applied, not interested, contacts, posts, and drafts states.

Recommended LinkedIn Posts Flow

Start with a narrow source and capture posts manually before creating a cron schedule. The first successful run should prove capture, relevance classification, contact extraction, and review-state creation.

  • Configure resume and matching settings if the workflow will generate resume replies.
  • Configure message settings, sender identity, and review requirements.
  • Create one narrow post source with a LinkedIn content search URL or saved post-search URL.
  • Run manual discovery before scheduling.
  • Review captured posts, relevance decisions, apply paths, contact evidence, and drafts.

AI Usefulness And Drafting

GrowthEngene can use deterministic prefilters and AI classification to decide whether a post is hiring-related and relevant. AI should receive cleaned, capped text and should not invent people, emails, companies, domains, or relationships.

The post workflow can store personal and agency draft variants separately so the operator chooses the appropriate sender route.

  • Clean post text before AI evaluation.
  • Preserve role, stack, location, seniority, compensation, and apply instructions.
  • Classify hiring intent, candidate relevance, apply path, confidence, and recommended action.
  • Create drafts only when the post is relevant or maybe relevant.
  • Require review before sending during early rollout.

Apply Path Handling

LinkedIn posts can point to different next actions. GrowthEngene should choose the safest action based on evidence and configured policy.

  • email_in_post: create email draft and attach resume where required.
  • phone_in_post: keep manual review or create a communication draft if supported.
  • external_apply_link: open or record manual application.
  • poster_dm: create LinkedIn DM draft for review.
  • comment_to_apply: create short comment draft for review.
  • poster_company_identified: enrich poster/company and consider email discovery.
  • unknown_apply_path: keep in review instead of sending.

Safe Scheduling

After manual capture works, create a schedule with conservative limits. Monitor the LinkedIn Posts settings page, scheduler, worker logs, and applied/draft states.

  • Use one or two narrow sources.
  • Keep daily auto saves, likes, reactions, and sends low.
  • Keep createResumeReplyReview enabled for first runs.
  • Leave scheduled auto-send disabled until direct-email, resume, sender, suppression, and pacing guards are proven.

Frequently Asked Questions

Can GrowthEngene use LinkedIn post signals for outreach?

Yes. Post activity can be used as context for identifying contacts and preparing relevant outreach workflows.

Should GrowthEngene run email discovery for every LinkedIn post?

No. Use direct contact evidence first, then run email discovery only when poster or company evidence is strong enough.

Can LinkedIn Posts create personal and agency drafts?

Yes. The workflow can keep personal and agency variants separate so the operator can choose the right sender path.

Related Guides