Run outbound sales workflows with Claude Code
Four workflows cover pre-call research, event attendee scraping, a daily hot-leads digest, and post-call CRM updates and follow-up drafts. Task: Suggested implementation: Use Claude Code to orchestrate outbound sales workflows. Trigger pre-call research agents via HubSpot bookings to generate briefs posted to Slack. Use Firecrawl as an MCP server to scrape event attendees, enrich data via Leadsforge, and load into Salesforge campaigns. Schedule Claude Cowork to run a 7:30 a.m. hot-leads digest and automate post-call CRM updates.; tools: Claude Code, Claude Cowork. Human role: Source evidence is unavailable regarding specific human roles or manual interventions in the described workflows.; limitations: Prerequisites include access to HubSpot, Slack, Firecrawl, Leadsforge, and Salesforge APIs. Integration complexity is high; tuning agents to specific CRM structures and scoring rules may take approximately one week. Human approval is required for all outbound communications and CRM data updates to prevent errors..
Tools
Published on Agent Work Atlas:
Overview
Four workflows cover pre-call research, event attendee scraping, a daily hot-leads digest, and post-call CRM updates and follow-up drafts.
Workflow
Suggested implementation: Use Claude Code to orchestrate outbound sales workflows. Trigger pre-call research agents via HubSpot bookings to generate briefs posted to Slack. Use Firecrawl as an MCP server to scrape event attendees, enrich data via Leadsforge, and load into Salesforge campaigns. Schedule Claude Cowork to run a 7:30 a.m. hot-leads digest and automate post-call CRM updates.
Reported result
Actual outcomes are unknown as the source is unavailable (HTTP 403). Proposed acceptance check: Measure if pre-call brief generation time reduces from manual baseline (e.g., 30-45 mins) to under 2 minutes, and if event list creation drops from hours to 20-30 minutes. Verify if automated post-call admin tasks reduce manual effort significantly.
Human role
Source evidence is unavailable regarding specific human roles or manual interventions in the described workflows.
Limitations
Prerequisites include access to HubSpot, Slack, Firecrawl, Leadsforge, and Salesforge APIs. Integration complexity is high; tuning agents to specific CRM structures and scoring rules may take approximately one week. Human approval is required for all outbound communications and CRM data updates to prevent errors.
Try it
Act as a sales operations engineer. I need to set up an automated outbound sales workflow using Claude Code. Inputs: [HubSpot API Key], [Slack Webhook URL], [Firecrawl API Key], [Leadsforge API Key], [Salesforge API Key], [CRM Scoring Rules Document]. Steps: 1. Create a Claude Code script that listens for HubSpot meeting bookings. 2. Upon trigger, launch three parallel research agents to gather company and contact info. 3. Compile findings into a pre-call brief and post it to the specified Slack channel. 4. Build a separate workflow using Firecrawl (MCP) to scrape event attendee lists based on a provided schema. 5. Enrich scraped data using Leadsforge and push qualified leads to a Salesforge campaign. 6. Configure Claude Cowork to generate a 7:30 a.m. hot-leads digest and draft post-call CRM updates. Deliverables: Python/Node scripts for each workflow, configuration files for API keys, and a README. Quality Check: Run a dry run with 5 test leads. Verify Slack posts are accurate and CRM updates match source data. Do not send real emails or update live CRM records without my explicit confirmation. If any API key is missing, stop and ask for it.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.