Skip to content

Event Catalog

Kiket extensions and automations react to a common set of events emitted by the workflow runtime. Use this catalog to understand the payload structure, delivery expectations, and troubleshooting tips for each channel before you wire receivers or implement CLI tooling.

Delivery basics

  • Source – Events originate from the workflow runtime (workflow.*), marketplace (marketplace.*), dbt runners (analytics.*), or the extension delivery pipeline (extension.*).
  • Envelope – Webhooks receive JSON objects with event, id, timestamp, organization_id, and payload.
  • Retries – Kiket retries failed deliveries with exponential backoff for 24 hours. Responses must complete within 10s (configurable via manifest).
  • Auth – Verify HMAC signatures using the X-Kiket-Signature header and the webhook secret from Settings → Extension Secrets or the CLI.

Workflow events

Event Description Payload highlights
workflow.issue.transitioned Issue status changed (manual or automation). Issue metadata, previous/next states, actor, comments.
workflow.issue.assignment.updated Assignment change from AI, automation, or manual override. Issue, previous assignee, new assignee, recommendation metadata.
workflow.sla_status SLA risk, warning, or breach for an issue. SLA target, elapsed time, recommended action.
workflow.approval.requested Approval stage triggered. Approval ID, required role/entity, custom metadata.
workflow.approval.resolved Approval approved/denied. Resolution, approver, optional reason.

Extension + marketplace events

Event Description Payload highlights
extension.delivery.started Extension invocation scheduled. Installation ID, secret scopes, delivery options, action key.
extension.delivery.completed Invocation succeeded. Duration, response body, diagnostics array.
extension.delivery.failed Invocation failed (timeout, 4xx/5xx, validation). Error category, detailed message, retry count.
marketplace.installation.created Customer installation created. Product, plan, workspace metadata.
marketplace.installation.secrets.pending Required secrets missing or expiring. Secret keys, due dates, secret health summary.

Analytics + dbt events

Event Description Payload highlights
analytics.dbt.run.started dbt run triggered (Cloud Build). Trigger source, build ID, target workspace.
analytics.dbt.run.completed Run finished (success/failure). Status, duration, manifest location (GCS URL).
analytics.dbt.run.failed dbt run failed before completion. Exit code, log pointers, failing model names.

Troubleshooting

  • No deliveries – verify webhook endpoint availability, TLS cert validity, and that the extension manifest lists the correct event in delivery.events.
  • Signature mismatch – ensure you hash the exact request body with the current webhook secret. Secrets rotate automatically when overwritten via the CLI or Settings → Extension Secrets.
  • Late/duplicate events – deduplicate via the id field. Retries reuse the same ID and attempt counter.