Explore

Build

/...

Agents

Lead-to-Deal Pipeline Agent — AI Agent by David Hakobyan

Automates the full lead-to-deal pipeline: finds prospects in Apollo.io, enriches and creates contacts in HubSpot, notifies the sales team in Slack, and sends Calendly booking links — eliminating manual prospecting handoff.

Category: Workflow AI Agents. Model: claude-sonnet-4-6.

System Prompt

You are a sales pipeline automation agent. Your job is to run the full lead-to-deal handoff end to end: search Apollo.io for prospects matching given criteria, enrich and create or update those contacts in HubSpot (setting lifecycle stage, owner, and deal details as appropriate), notify the sales team in a designated Slack channel with a concise prospect summary, and send a Calendly booking link to the prospect via HubSpot email or as a Slack message to the rep. Prioritize accuracy — verify contact data before creating records. Deduplicate against existing HubSpot contacts before creating new ones. Log every action taken and surface any errors or missing data clearly so a human can review.

README

# Lead-to-Deal Pipeline Agent The Lead-to-Deal Pipeline Agent automates the end-to-end prospect handoff: it searches Apollo.io for leads that match provided ICP criteria, verifies and enriches contact data, deduplicates against existing HubSpot records, then creates/updates contacts (and associated companies/deals) with accurate lifecycle stage, owner, and deal metadata. It notifies the sales team in a designated Slack channel with a concise prospect summary, and sends a Calendly booking link via HubSpot email or as a Slack message to the assigned rep. Every action is logged, and any data gaps or API errors are surfaced clearly for quick human review. It runs on model `claude-sonnet-4-6` and uses MCP servers: Apollo (prospecting and enrichment), HubSpot (CRM objects and email), Slack (channel alerts/DMs), and Calendly (meeting links). Tools include `agent_toolset_20260401` and one `mcp_toolset` per server (`apollo`, `hubspot`, `slack`, `calendly`), each with an always-allow permission policy—ensure your server-side auth and RBAC are properly scoped. Quick start: provision the MCP endpoints with valid credentials and permissions; gather HubSpot owner IDs, lifecycle stages/pipeline names, your target Slack channel ID, and a Calendly organization/user link. Launch the agent with this config, then provide run-time inputs such as ICP filters (industry, title, geo, company size), desired HubSpot pipeline/stage, owner assignment, Slack channel, and a booking link or template. The agent will search Apollo, verify/dedupe, create/update CRM objects, post a Slack summary, and send a booking link; monitor the agent’s logs to validate actions and address any flagged data or permission issues before moving to production workflows or scheduled runs.

MCP Servers

apollo
hubspot
slack
calendly

Agent Configuration (YAML)

name: Lead-to-Deal Pipeline Agent
description: >-
  Automates the full lead-to-deal pipeline: finds prospects in Apollo.io, enriches and creates contacts in HubSpot,
  notifies the sales team in Slack, and sends Calendly booking links — eliminating manual prospecting handoff.
model: claude-sonnet-4-6
system: >-
  You are a sales pipeline automation agent. Your job is to run the full lead-to-deal handoff end to end: search
  Apollo.io for prospects matching given criteria, enrich and create or update those contacts in HubSpot (setting
  lifecycle stage, owner, and deal details as appropriate), notify the sales team in a designated Slack channel with a
  concise prospect summary, and send a Calendly booking link to the prospect via HubSpot email or as a Slack message to
  the rep. Prioritize accuracy — verify contact data before creating records. Deduplicate against existing HubSpot
  contacts before creating new ones. Log every action taken and surface any errors or missing data clearly so a human
  can review.
mcp_servers:
  - name: apollo
    url: https://mcp.apollo.io/mcp
    type: url
  - name: hubspot
    url: https://mcp.hubspot.com/anthropic
    type: url
  - name: slack
    url: https://mcp.slack.com/mcp
    type: url
  - name: calendly
    url: https://mcp.calendly.com
    type: url
tools:
  - type: agent_toolset_20260401
  - type: mcp_toolset
    mcp_server_name: apollo
    default_config:
      permission_policy:
        type: always_allow
  - type: mcp_toolset
    mcp_server_name: hubspot
    default_config:
      permission_policy:
        type: always_allow
  - type: mcp_toolset
    mcp_server_name: slack
    default_config:
      permission_policy:
        type: always_allow
  - type: mcp_toolset
    mcp_server_name: calendly
    default_config:
      permission_policy:
        type: always_allow
skills: []