Pump Up connects AI agents to Close CRM to analyze leads, deals, and communication activities for revenue operations. Rather than running unverified automated outreach or bulk sequences, agents read parent lead records, associated opportunities, and separate timeline activities—such as emails, calls, and notes. The agent flags discrepancies, drafts follow-ups or opportunity updates, and stops for human approval before applying changes to Close.
3 related templates
Sales
Find out why the deal was lost, beyond the CRM dropdown.
HubSpot, Gmail, Google Drive, Attio, Pipedrive, Close, Bigin
View templateCustomer success
Find the next team, site, or use case inside a happy customer.
HubSpot, Google Sheets, Gmail, Google Drive, Close, Attio, Pipedrive
View templateSales
Resolve the unanswered proposal before deciding what to send next.
Pipedrive, PandaDoc, Gmail, Attio, Close, Capsule CRM, HubSpot, Outlook, Google Drive, OneDrive
View templateRevenue operations teams, sales leaders, and account managers using Close who want automated deal and pipeline analysis without sacrificing human oversight.
During a closed-lost audit for a $24,000 SaaS contract, the opportunity status in Close was marked as 'Lost - Price Resistance.' However, recent email threads and meeting notes on the parent lead record revealed that the prospect repeatedly requested HIPAA compliance certifications that were never provided. The AI agent compared the activity timeline with the opportunity fields, flagged the discrepancy, and drafted an update to recategorize the loss reason to 'Product / Security Gap.' Instead of overwriting Close data autonomously, the agent routed the comparison packet to the sales manager, who approved the correction and assigned a product-marketing follow-up task directly on the Close lead.
No. While Close provides automated email sequence capabilities, Pump Up workflows intentionally require explicit human authorization before sending customer messages or enrolling contacts in outbound sequences.
In Close, other records are children of a Lead. Fetching a lead includes its contacts and opportunities by default, but activities such as emails, calls, and notes are excluded and must be retrieved separately via activity endpoints.
The agent requires API read access to leads, opportunities, and activities, plus scoped write permissions for opportunities and lead notes. External changes should always be gated by human approval.
Custom fields in Close are identified by specific custom field IDs (custom.cf_xxx) on the lead or opportunity object. Workflows must map these field IDs explicitly during initial setup.