Recipe 3: Nurture & follow-up automation

Event-driven sequences: when something happens in your stack, DripPulse triggers the right workflow steps and respects suppression rules you define.

Business goal

Trigger follow-up sequences when events occur (signup, trial milestone, engagement signal) without manual list pulls.

Prerequisites

• Event producer (product backend, ESP, or CRM) that can call DripPulse.
• List or preference data for suppression (unsubscribe, DNC) checked inside the workflow.
• Optional: inbound tracking endpoints for opens/clicks feeding back into qualification.

Architecture (logical)

  [Event source] --> [Webhook / poll trigger]
                           |
                     [Suppression gate]
                           |
              +------------+------------+
              v            v            v
        Branch A      Branch B      Agent content
              |            |            |
              +------------+------------+
                           v
              [ESP / CRM / internal task webhook]

Event payload example

{
  "event": "trial.day3.no_login",
  "user_id": "usr_7721",
  "email": "sam@example.com",
  "suppression_checked_at": "2026-04-02T10:00:00Z"
}

Workflow behaviors to model

• Trigger: webhook receives event → workflow instance starts.
• Agent or rule: choose template copy vs. static branch for simple cases.
• Outbound action: HTTPS action step to your ESP or internal queue.
• Confirmation: webhook delivery logs or ESP callback; retries with backoff on your side.

What you’ll see in the dashboard (reference)

1. Workflows: Trigger step shows last fired time; add a Test run using the sample event JSON to confirm the suppression gate.
2. Monitoring: Track volume per workflow; sudden drops may mean the upstream webhook stopped POSTing.
3. Webhooks: Outbound action deliveries to your ESP should show 2xx in /webhooks/:id/deliveries when you emit events through DripPulse subscriptions.
4. AI Agents (optional): If a content-selection agent runs, open its execution log to audit which branch fired.

Delivery & bounce notes

DripPulse exposes inbound nurture-related webhook paths (e.g. bounces) in the API reference. Wire ESP callbacks so failed sends update suppression.

What success looks like

• Eligible contacts receive the next step; suppressed contacts never get the send.
• Monitoring shows stable send → acknowledgment ratio.
• Failures are visible in workflow or webhook delivery history for replay.

Ops: RevOps guide · Troubleshooting