251
All workflows

Email buyers at newly funded companies

Finds companies that just raised with People Data Labs, gets each buyer's email from Apollo, and queues an approved email in lemlist.

Outcome

  • A table of every funded company with its buyer and their work email, or a note on why there is none.

  • An approved three-sentence email for each buyer, queued in your lemlist campaign.

How it works

  1. P

    Find funded companies, by Search companies by People Data Labs

    List up to max_companies companies matching target_segment whose last_funding_date falls within funding_window. Keep name, website, latest round and date.

  2. A

    Find the buyer, by Search people by Apollo

    For each company's domain, find people with buyer_titles and keep the most senior, with their Apollo id; note the companies with no match.

  3. A

    Get their emails, by Enrich up to 10 people by Apollo

    Enrich each buyer, up to 10 per call. Keep their name, title and work email.

  4. Write emails, by Your agent

    Draft a three-sentence plain-text email per contact: congratulate the round, connect it to offer, ask one question. Show the drafts to the user.

  5. l

    Send, by Add a lead to a campaign by lemlist

    After the user approves, add each contact to campaign with their approved email in email_variable.

You'll be asked for

  • The kind of company to watch

    e.g. Series A B2B SaaS in the US

  • How fresh the round must be

    e.g. 30 days

  • The most companies to pull, since each costs a credit

    e.g. 50

  • The roles to reach, most senior first

    e.g. VP Marketing, Head of Growth

  • What you sell, in one line

    e.g. outbound email that books meetings

  • The lemlist campaign that sends the emails from your mailbox, by name

    e.g. Funding outreach

  • The custom variable the campaign's email prints as its whole body, set up once in lemlist

    e.g. drafted_email

funding-signal-outbound.mdView markdown

Email buyers at newly funded companies

Finds companies that just raised with People Data Labs, gets each buyer's email from Apollo, and queues an approved email in lemlist.

Set up the tools below, then run the steps in order for the user, carrying each step's results into the next. The run is done when the user has the outcome below.

Outcome

  • A table of every funded company with its buyer and their work email, or a note on why there is none.
  • An approved three-sentence email for each buyer, queued in your lemlist campaign.

Inputs

Ask the user for these before you start.

  • target_segment: the kind of company to watch, e.g. Series A B2B SaaS in the US
  • funding_window: how fresh the round must be, e.g. 30 days
  • max_companies: the most companies to pull, since each costs a credit, e.g. 50
  • buyer_titles: the roles to reach, most senior first, e.g. VP Marketing, Head of Growth
  • offer: what you sell, in one line, e.g. outbound email that books meetings
  • campaign: the lemlist campaign that sends the emails from your mailbox, by name, e.g. Funding outreach
  • email_variable: the custom variable the campaign's email prints as its whole body, set up once in lemlist, e.g. drafted_email

Set up

Search companies (People Data Labs, tool:people-data-labs/search-companies)

Use the API.

Note: Each record returned costs one credit, and size defaults to 1 (up to 100): set it, and page with scroll_token.

Apollo (tool:apollo/search-people, tool:apollo/bulk-enrich-people)

Use the first option your agent supports.

Notes:

  • Search people: Costs no credits and finds only net-new people, not contacts already saved in Apollo. Returns no emails: enrich the matches to get them. Up to 100 people per page and 50,000 in total.
  • Enrich up to 10 people: Credits are charged per person, only when data is found; unmatched people come back as null. Personal emails and phone numbers are off unless you set reveal_personal_emails or reveal_phone_number.
MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

{ "mcpServers": { "apollo": { "url": "https://mcp.apollo.io/mcp" } } }
  • Search people: call the MCP tool apollo_mixed_people_api_search
  • Enrich up to 10 people: call the MCP tool apollo_people_bulk_match
CLI (official)

Install the command and sign in with it, then confirm it runs.

brew install apolloio/apollo-io-cli/apollo-io-cli
apollo --version
  • Search people: run apollo people search
  • Enrich up to 10 people: run apollo people bulk-enrich

Add a lead to a campaign (lemlist, tool:lemlist/add-lead-to-campaign)

Use the first option your agent supports.

Note: The campaign automates outreach to its leads: confirm it first. findEmail, verifyEmail, findPhone and linkedinEnrichment spend credits, and a lead already in the campaign is refused with 400 LEAD_ALREADY_IN_CAMPAIGN.

CLI (official)

Install the command and sign in with it, then confirm it runs.

npm install -g @lemlist-official/cli
lemlist --version

Run lemlist api POST /campaigns/{campaignId}/leads/.

API (official)

Note: LEMLIST_API_KEY holds the base64 of :<api key>, an empty username and the key; 20 requests every 2 seconds per key.

Before step 1, confirm access to each service with its cheapest read-only call, like a list or a search. Never send or change anything to test access.

Steps

  1. Find funded companies with Search companies (People Data Labs). List up to max_companies companies matching target_segment whose last_funding_date falls within funding_window. Keep name, website, latest round and date.
  2. Find the buyer with Search people (Apollo). For each company's domain, find people with buyer_titles and keep the most senior, with their Apollo id; note the companies with no match.
  3. Get their emails with Enrich up to 10 people (Apollo). Enrich each buyer, up to 10 per call. Keep their name, title and work email.
  4. Write emails yourself. Draft a three-sentence plain-text email per contact: congratulate the round, connect it to offer, ask one question. Show the drafts to the user.
  5. Send with Add a lead to a campaign (lemlist). After the user approves, add each contact to campaign with their approved email in email_variable.

Rules

  • Use only the services set up above. The read-only calls they need, like listing ids or polling for results, are fine.
  • Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
  • Never print API keys.