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

  1. Product story: How DripPulse works — objects, execution, and human control in one place.
  2. First win: Getting started — problems solved, what to launch first, and a 10-minute setup path.
  3. Instant Operator: Operator instant quickstart — built-in goals, plan apply, activity log.
  4. Batch data: Sources & batch data — save CSV/Postgres; run on agent Batch tab.
  5. First workflow conceptually: Inbound lead qualification (end-to-end narrative + payloads).
  6. API: Programmatic quickstart, external agents (docs URLs, sessions vs enrollments), event bridge (webhooks → your server → API), then full reference.
  7. Integrations: External tool adapters — providers, guardrails, and integration_action patterns.
  8. Go live safely: Production readiness (keys, webhooks, retries, limits, logs).

Trust & operations

End-to-end recipes

All guides (HTML)

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.