// Sequences & Automation

Sequence Webhooks

Send step-completion callbacks to external systems from your sequence workflow

1 min read
Updated March 18, 2026
sequenceswebhooksintegrationsautomation

You can add a webhook URL to any sequence step. When that step completes, demeterrr sends a POST request to your endpoint.

01

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
02

Webhook Payload Shape

Step callbacks include fields such as:

  • event (step.completed)
  • sequenceId
  • sequenceStepId
  • stepIndex
  • stepType
  • contactId
  • organizationId
  • sendingId
  • timestamp
03

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.

04

Implementation Best Practices

  • Make your endpoint idempotent (sendingId + stepIndex is a good dedupe key)
  • Return quickly (2xx) and process asynchronously
  • Capture payload logs for debugging
  • Add retry logic on your side if needed
05

Troubleshooting

If webhooks are not arriving:

  1. Confirm URL is valid HTTPS.
  2. Verify the step actually runs (not skipped/cancelled).
  3. Check endpoint latency and timeouts.
  4. Review external logs for rejected requests.

See Sequence Troubleshooting for full diagnostics.

Was this article helpful?

Let us know if you found this article helpful or if you need more information.

Take Control Of Your Reputation. Take Control Of Your Reputation. Take Control Of Your Reputation. Take Control Of Your Reputation.

Join hundreds of businesses already using demeterrr to collect feedback, boost reviews, and grow faster.

Start Your Trial