Skip to main content

Event-Driven Integrations

The strongest production pattern is webhook-driven ingestion plus scheduled reconciliation. Webhooks are the primary operating model. Reconciliation exists to repair drift, not to replace event handling.

This pattern is the default foundation for robust external integrations built on the SpotDraft API.

Why both are needed​

  • webhooks provide low-latency updates
  • reconciliation catches missed, delayed, or dropped downstream processing
  • direct status fetches are still useful for repair, backfill, and incident debugging
  1. accept webhook deliveries
  2. verify and enqueue them
  3. process idempotently
  4. run a scheduled sync that checks for recent changes by timestamp
  5. compare SpotDraft state with your internal state and repair drift

Typical downstream consumers​

This architecture commonly feeds:

  • CRM status sync
  • ERP and procurement updates
  • storage or repository copy flows
  • Slack or Teams notifications
  • warehouse sync repair jobs

What to avoid​

  • polling every contract on a short interval just to detect lifecycle changes
  • treating the webhook payload as the only durable source of truth
  • writing downstream side effects directly inside the webhook request thread
  • Use Webhooks for delivery, verification, and receiver design.