Personalised Lead Outreach Template

• What it does: Enriches lead data with Apollo, PredictLeads, and web search, then hands off to an agent that writes and sends personalized outbound emails via Gmail.
• Best for: sales teams, growth and demand-gen teams, agencies running outbound campaigns, B2B outreach
• Apps used: Apollo.io, PredictLeads, Web Search, Gmail
• Setup time: 10 to 15 minutes

Personalised Lead Outreach is a no-code, two-agent workflow that turns a lead email (or minimal identifiers) into enriched prospect data and a tailored outbound email. The Lead Data Specialist enriches the lead using Apollo, PredictLeads, and web search; the Email Content Writer drafts personalized copy and sends it via Gmail. This template acts as a starting point: any app, instructions, and agents can be updated as required for your own use case—simply ask Max (Agent Builder) to update the workflow as needed. Last verified from workflow config on March 2026. Includes common failure modes and fixes.

---

Problem this solves

• Manual lead research and enrichment slow down outbound; you send generic emails or skip personalization.
• Copy-pasting between enrichment tools, spreadsheets, and email wastes time and introduces errors.
• You want campaign-ready, personalized emails without building custom pipelines or code.
• One place to trigger enrichment and send, with control over tone and campaign context.

---

What this agent does

This template can:

• Enrich leads from minimal input (e.g. email) using Apollo.io people enrichment
• Look up company details and latest news or events via PredictLeads
• Use web search to find recent prospect and company activity for personalization angles
• Structure enriched data (role, company, pain points, relevance) for the email agent
• Hand off enriched lead data to the Email Content Writer via structured input
• Write personalized outbound email copy aligned with campaign goals and tone
• Send the email via Gmail (subject, body, recipient from lead data)
• Optimize for replies with short, clear copy and soft CTAs (no spam triggers)

---

How it works

1. You provide lead input (e.g. lead email) via the text trigger in Playground or your deployment channel.
2. Lead Data Specialist receives the input and enriches the prospect using Apollo (people enrichment), PredictLeads (company lookup, news/events by domain), and web search (recent activity).
3. The agent structures the data (target, product relevance, benefit insights) and validates key fields.
4. The specialist hands off the enriched lead data to the Email Content Writer (structured LeadInfo schema).
5. Email Content Writer drafts personalized subject and body using campaign context and personalization rules, then calls the Gmail send-email tool to deliver the email.
6. The workflow completes; you can run it per lead or in batch from the SketricGen portal or on a schedule.

---

Requirements

• Apollo.io account (for people enrichment)
• PredictLeads account (for company lookup and news/events by domain)
• Gmail account with send access (or another mailing tool if you swap the Gmail node)
• Campaign context: target audience, product description, primary benefit (editable in the Lead Data Specialist agent instructions)
• Lead identifier to start: at minimum, lead email; other fields can be inferred or enriched

---

Setup guide

1. Clone the template and open it in AgentSpace.
2. Update the Campaign Content Guidance section in the Lead Data Specialist agent instructions (target audience, product description, primary benefit). The example uses SketricGen; replace with your campaign.
3. Connect Apollo.io: click the Apollo tool node → Connect → authorize (people-enrichment).
4. Connect PredictLeads: click the PredictLeads tool node → Connect → authorize (company lookup, news/events by domain).
5. Connect Gmail: click the Gmail tool node → Connect → authorize (send email). You can replace with another mailing app from the SketricGen marketplace if preferred.
6. Optional: enable Web Search if not already on (for extra prospect/company research).
7. (Optional) Adjust the Writing & Structure Guidelines in the Email Content Writer agent (tone, reading level, structure).
8. Run Test Workflow with a sample lead email. Confirm enrichment and that the email sends to the correct recipient with expected subject and body.
9. Deploy or run on schedule as needed from the SketricGen portal.

Common issues and fixes

• Email not sending: check Gmail connection and that to is the lead email from enriched data; ensure body is HTML and no placeholder brackets remain.
• Enrichment incomplete or wrong: verify Apollo and PredictLeads are connected; provide a valid business email; avoid making up names (use only prospect info from tools).
• Personalization feels generic: tighten Campaign Content Guidance and ensure Lead Data Specialist has enough signals (company news, role) from PredictLeads and web search.
• Spam or deliverability: keep subject and body short, avoid spam triggers and ALL CAPS; use soft CTAs.

Customization knobs

• Swap Gmail for another mailing tool in the marketplace; update the Email Content Writer instructions to use the new tool’s parameters.
• Edit Campaign Content Guidance per campaign or segment.
• Adjust Email Content Writer tone, structure, and personalization rules in the agent instructions.
• Add or remove enrichment tools (e.g. more data sources) and pass additional fields in the handoff schema.

---

Apps used

(Scopes vary by how you connect each app.)

---

Use cases

• Outbound campaign launch: Enrich a list of leads and send personalized cold emails from one workflow. Best for sales and demand-gen teams.
• Account-based outreach: Use company and news signals from PredictLeads to tailor messaging per account. Best for B2B and ABM.
• Agency client campaigns: Run multiple campaigns by updating Campaign Content Guidance and connecting client mailing tools. Best for agencies.
• Follow-up sequences: Trigger the workflow per lead (e.g. from CRM or sheet) to send consistent, personalized follow-ups. Best for SDRs and growth teams.
• Event or news-triggered outreach: Use PredictLeads news/events to time and personalize outreach. Best for sales and marketing.

---

Example prompts and outputs

Example 1: Single lead

Prompt (input): john.doe@acme.com

Output: Lead Data Specialist enriches the lead (Apollo + PredictLeads + web search), then Email Content Writer sends a personalized email to john.doe@acme.com with a subject and body aligned to role, company, and campaign. Confirmation that the email was sent.

Example 2: Lead with context

Prompt (input): jane@startup.io – we’re targeting ops leads who need workflow automation

Output: Enrichment focuses on ops role and workflow pain points; email copy references automation benefits and soft CTA. Email sent to jane@startup.io.

Example 3: Batch (conceptual)

Run the workflow once per lead (e.g. from a list). Each run: one lead in → one enriched, personalized email sent. Use Playground, API, or schedule as needed.

---

Why you need this template

• One workflow from lead identifier to sent email; no manual copy-paste between enrichment and email.
• Consistent personalization using structured data and campaign context instead of ad-hoc research.
• Editable in AgentSpace: change campaign copy, add tools, or adjust handoff schema without code.
• Faster outbound cycles: enrich and send in minutes; scale by running per lead or on schedule.

---

FAQs

1) Is this an AI agent template or a fixed automation?

It is a multi-agent workflow you can edit in AgentSpace (two agents: Lead Data Specialist and Email Content Writer). You control campaign context, tools, and copy rules. This template acts as a starting point: any app, instructions, and agents can be updated for your own use case—simply ask Max (Agent Builder) to update the workflow as needed.

2) Do I have to use Apollo and PredictLeads?

The template is designed for Apollo (people enrichment) and PredictLeads (company and news). You can add or swap tools (e.g. other enrichment sources) and update the Lead Data Specialist instructions and handoff schema.

3) Can I use something other than Gmail to send?

Yes. Connect another mailing tool from the SketricGen app marketplace and update the Email Content Writer agent to call that tool’s send action and parameters.

4) What input do I need to start the workflow?

At minimum, the lead’s email. The Lead Data Specialist enriches from there. You can pass more context (e.g. name, company) in the trigger input if available.

5) Where do I set campaign messaging (product, audience, tone)?

In the Lead Data Specialist agent instructions, under Campaign Content Guidance: Target Audience, Product Description, Primary Benefit. Update this per campaign. The Email Content Writer uses this plus the enriched lead data.

6) Why did the email not send?

Check: Gmail (or your mailing tool) is connected; the enriched data includes a valid recipient email; the Email Content Writer is not leaving brackets or placeholders in subject/body; bodyType is set to "html" when required by the tool.

7) Can the agent make up prospect details?

No. The Lead Data Specialist is instructed to use only prospect information from the tools (Apollo, PredictLeads, web search); do not guess or invent names or data.

8) How do I avoid spam triggers?

The Email Content Writer instructions enforce short sentences, no aggressive sales language, no excessive punctuation or emojis, no ALL CAPS, and soft CTAs. Keep campaign copy aligned with those rules.

9) Can I run this for many leads at once?

The workflow runs one lead per execution. To run for many leads, trigger it repeatedly (e.g. from a list via API or Playground, or from another workflow that loops over leads).

---

Related templates

• Personal Ops AI Assistant [blocked] – calendar, comms, and retrieval in one place.
• AI Receptionist [blocked] – route inbound messages to Q&A, booking, or escalation.
• Marketing Strategy [blocked] – research and strategy for campaigns.
• Internal Team Support [blocked] – internal Q&A and procedures.
• Structured Output [blocked] – fetch structured company or entity data for use in other workflows.