Getting started

Outcome-first orientation. For HTTP examples see the programmatic quickstart; for architecture read How DripPulse works.

What is DripPulse?

DripPulse is an agent-operable CRM: the CRM operating layer where external agent systems can manage CRM work through workflows, APIs, skills packs, and governed execution. Use it to qualify leads, route opportunities, trigger follow-ups, and update CRM records—with humans in control where it matters—not only through manual UI work.

What problem it solves

• Stop manual lead triage — put scoring and routing in explicit workflows and agents.
• Speed up routing decisions — encode ownership and SLA rules once, reuse everywhere.
• Standardize follow-up logic — same playbook for every rep, observable in logs.
• Automate CRM updates and signal handling — integrations and webhooks move data when events fire.

Instant results with built-in Operator (≈5–10 min)

Fastest path without API code: Dashboard → Tools → Operator → Start guided setup → apply a deterministic plan (default pipeline + hosted form). You’ll see outcomes in the activity log and can submit a test lead to CRM immediately. Full walkthrough: Operator instant quickstart (built-in goals: intake, qualification, routing, nurture).

What you can launch first

• Operator instant value — hosted form + activity log in minutes.
• Inbound lead scoring — Lead Qualification Agent (canonical example).
• SDR routing workflow — branch on region, industry, or score; assign queues.
• Opportunity summary agent — structured output for managers (via template / execute).
• Nurture from external events — your backend receives POST → DripPulse enrollments/bulk or agent execute (event bridge, recipe).

What is an agent here?

In DripPulse, an agent is a deployed runtime that receives scoped inputs, can use connected context, and returns structured outputs or actions as part of a workflow. It is not only a chatbot: it is a configured execution component inside an operational process. See Template guide for policies and deployment.

First successful setup in about 10 minutes

1. Workspace / org: Sign in and confirm you are in the right organization.
2. Project (optional): create or pick a project to organize workflows.
3. API key: Dashboard → API Keys → create; store the secret once.
4. Integration: Settings → connect at least one system you route or update against.
5. Simple workflow: draft a flow (trigger → log or notify step); Test with sample JSON.
6. Sample payload: use the quickstart’s workflow test call or agent execute with test data.
7. Execution logs: open Monitoring or GET .../agents/:id/executions to verify.
8. Promote: activate the workflow; watch first real runs; then tighten production controls.

Key concepts in one screen

How a run moves (visual)

  [ Trigger ]  schedule / webhook / manual test
       |
       v
  [ Filter / score / branch ]
       |
       v
  [ Actions ]  agents, webhooks, CRM updates
       |
       v
  [ Logs & metrics ]

What gets automated vs. what stays human

• Automated: steps you place in workflows and agents — scoring, routing branches, outbound hooks — within policy.
• Human: strategy, template/design changes, billing, API key issuance, and any step you deliberately exclude.
• Review tier: Approver role exists when you want a permission layer for sensitive configuration.

Billing (dashboard)

Dashboard → Billing shows plan, usage for the current billing period, and renewal or cancellation dates synced from Stripe when you open the page. If you scheduled cancellation at period end, the org moves to Free after that date when Stripe reports the subscription ended. Scheduled cancel shows Cancels on … while still active; after the period, limits reset to the free tier.

Where to go next

1. Operator instant quickstart — built-in use cases and activity log.
2. Sources & batch data — data on Sources; runs on agent Batch tab.
3. How DripPulse works — full object and execution model.
4. Build your first qualification story end-to-end.
5. Workflow builder · Templates.
6. API quickstart · API reference.
7. Production readiness for webhooks, retries, and keys.
8. RevOps guide if you configure from operations, not IDE-first.