← Documentation home
Getting started with DripPulse
Plain-language orientation for buyers and implementers. For HTTP examples, use the programmatic quickstart and API reference.
What is DripPulse?
DripPulse is a CRM and automation platform built API-first. You model work as workflows (steps such as triggers, filters, and actions),
deploy agents from templates or from those workflows, and integrate external systems through connections, webhooks, and the JSON API.
Unlike a traditional CRM where the UI is the center of gravity, DripPulse is designed so scripts, backends, and AI agents can discover capabilities,
run jobs, and report results over HTTP—with humans steering via the dashboard when needed.
What problems it is meant to solve
- Repeatable revenue and ops work (qualification, routing, follow-ups, logging) expressed as explicit workflows instead of one-off scripts.
- One API surface for automation and integrations, scoped to your organization.
- Visibility into runs, costs, and monitoring from the app while execution stays automated.
What is an “agent” here?
An agent is a deployed instance—usually created from a template or bound to a workflow—that executes according to policies and configuration you set.
It is not a generic chatbot: it is tied to your org’s data and integrations and to the steps you defined.
What agents automate vs. what stays human
- Automated: steps you put in a workflow (e.g. fetch data, score, send outbound webhooks, call configured integrations, log outcomes).
- Human: strategy, template and workflow design, API key issuance, billing, team membership, and any step you deliberately leave outside automation.
- Team guardrail: the Approver role exists for organizations that want a review-oriented permission tier alongside Admin, Editor, and Viewer.
Core data model (conceptual)
Everything below is scoped to your organization (multi-tenant isolation).
| Area | What it is |
|---|
| Organization & account | Your tenant; billing and settings attach here. |
| Users & team | People with roles (Admin, Editor, Viewer, Approver) who use the dashboard. |
| API keys | Programmatic credentials; Authorization: Bearer; revocable; org-scoped. |
| Workflows | Directed steps (trigger → processing → actions). Testable before production use. |
| Agent templates | Reusable definitions used to spawn agents with a chosen policy. |
| Agents | Running instances; executions, logs, metrics, and costs are observable per agent. |
| Projects | Grouping / organization of work (as exposed in the API and UI). |
| Integrations & data sources | Connections to external tools and imported data (see Settings and API). |
| Webhooks (outbound) | Subscribe to events and deliver payloads to your URLs. |
| Reports | Generated artifacts and schedules supported by the API. |
Exact fields and payloads are in the API reference; the dashboard reflects live state for your org.
How a workflow runs (mental model)
[ Trigger ] e.g. schedule, inbound event, manual test
|
v
[ Filter / logic ] qualify rows, branch, score
|
v
[ Actions ] email, webhook, CRM update, custom integration step
|
v
[ Log / metrics ] executions, monitoring, cost signals
Step types available to the builder are described in the API (GET /api/v1/workflows/step_types) and in the workflow builder guide.
Permissions and security (basics)
- Dashboard access is controlled by team roles; only trusted admins should invite members or change roles.
- API keys carry the same org scope as a logged-in session for API calls—store them as secrets; revoke when rotated or leaked.
- OAuth (e.g. Google sign-in) and admin login are documented on the login side of the product; use production-hardened passwords for any admin path.
- Inbound webhooks from providers (e.g. Stripe) use provider signatures, not your org API key—see the API reference “Inbound webhooks” section.
Your first ~10 minutes in the product
- Sign in: Open Sign in and use Google or your organization’s admin credentials (as provisioned for your tenant).
- Orient: From the dashboard, open Workflows and AI Agents to see how automation is organized.
- Connect: Under Settings (and related areas), configure integrations or data sources your org actually uses—availability depends on your plan and what is enabled.
- Design or pick automation: Read the template guide; optionally build a draft in the workflow builder guide.
- Deploy an agent: From AI Agents, deploy from a template or workflow; confirm status under Monitoring.
- API path (optional): Create an API key, then run the quickstart against
/api/v1.
Routing, qualification, and prioritization
There is no single hidden “magic” router: you encode rules in workflow steps (filters, scores, branches) and in agent configuration.
Prioritization is whatever your steps implement—e.g. ordering, thresholds, or downstream CRM views fed by DripPulse.
Dashboard tour (what to expect)
- Home: summary of activity and shortcuts into the product.
- Agents & monitoring: what ran, errors, and operational health.
- Workflows: author, test, and manage automation graphs.
- Team: invites and roles.
- API keys: create and revoke programmatic access.
- Billing: plan and subscription management (Stripe-backed where enabled).
Next steps
- Template guide — agent templates and policies.
- Workflow builder — custom flows and testing.
- Programmatic quickstart — curl and API patterns.
- API reference — every route in one place.
- Pricing — plans and limits at a glance.