Sequence Webhooks
Send step-completion callbacks to external systems from your sequence workflow
You can add a webhook URL to any sequence step. When that step completes, demeterrr sends a POST request to your endpoint.
Why Use Step Webhooks
Common use cases:
- Create CRM tasks after key touchpoints
- Notify Slack/ops systems
- Trigger downstream workflows in middleware tools
- Persist sequence milestones to internal analytics
Webhook Payload Shape
Step callbacks include fields such as:
event(step.completed)sequenceIdsequenceStepIdstepIndexstepTypecontactIdorganizationIdsendingIdtimestamp
Delivery Behavior
- Webhook call uses POST with
application/json - Timeout is short (10 seconds)
- Failures are non-fatal (workflow continues)
This design prevents external outages from blocking core sequence delivery.
Implementation Best Practices
- Make your endpoint idempotent (
sendingId + stepIndexis a good dedupe key) - Return quickly (2xx) and process asynchronously
- Capture payload logs for debugging
- Add retry logic on your side if needed
Troubleshooting
If webhooks are not arriving:
- Confirm URL is valid HTTPS.
- Verify the step actually runs (not skipped/cancelled).
- Check endpoint latency and timeouts.
- Review external logs for rejected requests.
See Sequence Troubleshooting for full diagnostics.
// Related articles
Sequence Step Types
Understand each step type in the sequence builder and when to use it
API-Triggered Sequences
Enroll contacts into sequences programmatically using the API
Sequence Troubleshooting
Diagnose why sequences are not running or certain steps are skipped
Creating Your First Sequence
Build and activate an automated multi-step sequence for survey and follow-up workflows
Was this article helpful?
Let us know if you found this article helpful or if you need more information.
Join hundreds of businesses already using demeterrr to collect feedback, boost reviews, and grow faster.
Start Your Trial