Webhooks

Webhooks go both ways, and the two don't share a setup.

Kindgi starts runs from your systems' webhooks. Register a webhook trigger, and a signed request from WooCommerce, Drupal's Webhooks module, GitHub, Shopify or any Standard Webhooks sender starts a run of your flow: Start runs from WooCommerce, Drupal or any signed webhook.

Kindgi tells your app when a run ends. Instead of polling a run, register a webhook endpoint, a URL in your app, and Kindgi sends it a signed run.finished request each time a run you started completes, fails or is cancelled.

• Get a webhook when a run finishes: store the signing secret, register the endpoint, and answer each request.
• Verify a webhook: check the signature in TypeScript or Python, and deduplicate retries.
• Test and replay deliveries: send a test event, see what was delivered, and send a failed delivery again.
• Webhook events and deliveries: every event and what it carries, how deliveries are retried, and the console's Webhooks page.

Requests are signed in the Standard Webhooks format, so a receiver in another language can use any Standard Webhooks library.