Build and govern agent-operated CRM workflows
Learn how external agents can operate CRM records and workflows safely through skills packs, APIs, approvals, and production-ready execution patterns—without turning operations into a black box.
Full CRM (leads, contacts, accounts, opportunities, activities, pipelines) plus workflows that qualify, route, and run follow-up over REST APIs and webhooks. This is not only a workflow tool or a bolt-on copilot: agents execute the same records your team uses. Use these pages to validate architecture before you integrate or go live.
Pick your path
For founders & operators
See what ships in week one and how RevOps uses the product.
For RevOps teams
Routing, reviews, integrations, and health checks without reading RFCs first.
For developers
Authenticate, call the API, and inspect responses like production.
For agent builders
Skills packs, OpenAPI, and patterns for Claude, OpenClaw, and custom agents.
What you can do with DripPulse
Qualify inbound leads automatically
Score, tier, and route leads from forms, ads, or webhooks—see the lead qualification recipe (canonical Lead Qualification Agent example).
Route opportunities to the right owner
Encode ownership and SLA logic in workflows and agents. Opportunity routing recipe.
Trigger follow-up from events
Nurture and signal-driven sequences: your backend bridges events to enrollments/bulk. Event bridge · Nurture recipe.
Run agents against CRM & integration data
Deployed agents execute over your org-scoped data with observable runs, logs, and metrics. Batch many rows via Sources + agent Batch tab.
Operator instant value (built-in)
Guided setup, hosted forms, and activity log—see CRM outcomes in minutes. Instant quickstart.
Monitor execution and review outcomes
Dashboard monitoring, agent execution history, and operational checks—day-two guide.
Start here
- Product story: How DripPulse works — objects, execution, and human control in one place.
- First win: Getting started — problems solved, what to launch first, and a 10-minute setup path.
- Instant Operator: Operator instant quickstart — built-in goals, plan apply, activity log.
- Batch data: Sources & batch data — save CSV/Postgres; run on agent Batch tab.
- First workflow conceptually: Inbound lead qualification (end-to-end narrative + payloads).
- API: Programmatic quickstart, external agents (docs URLs, sessions vs enrollments), event bridge (webhooks → your server → API), then full reference.
- Integrations: External tool adapters — providers, guardrails, and
integration_actionpatterns. - Go live safely: Production readiness (keys, webhooks, retries, limits, logs).
Trust & operations
- Production readiness hub — checklist and deep links.
- Authentication & API keys — scope, rotation, environments.
- Webhook signing & verification — outbound HMAC and inbound providers.
- Retries & idempotency — safe replays for agents vs workflows.
- Monitoring & troubleshooting — failed runs, logs, alerts.
- Rate limits — backoff and burst handling.
- Human approval gates — workflow approval steps, default fallback gate, and template deploy sign-off.
End-to-end recipes
- Recipe 1: Inbound lead qualification
- Recipe 2: Opportunity routing & prioritization
- Recipe 3: Nurture & follow-up automation
All guides (HTML)
- How DripPulse works
- Getting started
- Operator instant quickstart
- Sources & batch data
- Operator & use cases
- For Revenue Operations teams
- Template guide
- Workflow builder
- Human approval gates
- External tool adapters
- Event bridge (start workflows from your backend)
- Pricing & plans
- Programmatic API quickstart
- API reference
- External agents & sessions
- Agent skills (Claude/OpenClaw)
- CRM data portability (import/export JSON)
- Production readiness (keys, webhooks, idempotency, …)
- Monitoring & troubleshooting
- Status
Sign in for API keys Open API quickstart
At a glance: how data flows
Triggers DripPulse Outcomes --------- --------- -------- Webhook / → Workflow steps → CRM update schedule / + deployed agents Webhook to your systems manual test (org-scoped) Notifications / tasks
For objects, permissions, and review: How DripPulse works.