API Reference Card
All examples use three environment variables:
SALESFORCE_INSTANCE (e.g. yourorg.my.salesforce.com), SALESFORCE_ACCESS_TOKEN, and MAVERA_API_KEY. Store them in your secret manager — never commit tokens.Jobs Directory
CRM-to-Persona Pipeline
Pull contacts via SOQL, group by title/industry, create data-grounded personas
Deal-Stage Focus Group
Win/loss analysis via synthetic focus groups mapped to opportunity stages
Account Intelligence Brief
AI research briefs from Account, Contact, and Task data
Sales Note → Brand Voice
Extract winning language from Closed Won deal notes into a Brand Voice profile
Lead Scoring Validation
Validate lead scoring models with synthetic focus group feedback
Pipeline-Aware Content Generation
Generate stage-specific nurture content tied to your real pipeline
Competitive Displacement Tracker
AI-generated battle cards from competitor mentions in opportunities
Customer Success Interview Prep
QBR prep documents from Account health, Cases, and Activities
Production Tips
SOQL pagination — Queries returning more than 2,000 rows include a
nextRecordsUrl field. Follow it until done: true:
Concurrency — Salesforce allows 25 concurrent long-running requests. For batch jobs across hundreds of accounts, use a semaphore or queue (
asyncio.Semaphore(25) in Python, p-limit(25) in Node).
Custom field discovery — Not sure if Competitor__c or Health_Score__c exists in your org? Use the Describe endpoint:
What’s Next
HubSpot Integration
8 jobs — lifecycle personas, deal replay, meeting analysis
Personas API
Full reference for POST /api/v1/personas
Focus Groups API
Full reference for POST /api/v1/focus-groups
Mave Agent
Full reference for POST /api/v1/mave/chat