Skip to main content
Deck pushes structured events to your infrastructure as things happen. Credentials authenticate, tasks complete, files get captured. Every state change produces an event you can subscribe to, filter, and replay.

​
Event structure

Events follow an object.action naming convention. The data field contains a summary of the resource at the time of the event. 
{
  "id": "evt_a1b2c3d4...",
  "object": "event",
  "type": "task_run.completed",
  "data": {
    "id": "trun_a1b2c3d4...",
    "object": "task_run",
    "status": "completed",
    "result": "success",
    "task_id": "task_a1b2c3d4...",
    "credential_id": "cred_a1b2c3d4...",
    "agent_id": "agt_a1b2c3d4...",
    "source_id": "src_a1b2c3d4...",
    "runtime_ms": 12453,
    "created_at": "2025-01-15T09:30:00Z",
    "updated_at": "2025-01-15T09:31:15Z"
  },
  "created_at": "2025-01-15T09:31:15Z"
}

​
Destinations

Events are delivered to destinations you configure. Deck supports webhooks and native cloud infrastructure out of the box.
TypeIdentifier
Webhookwebhook
AWS SQSaws_sqs
AWS Kinesisaws_kinesis
AWS S3aws_s3
GCP Pub/Subgcp_pubsub
Azure Service Busazure_servicebus
RabbitMQrabbitmq
Hookdeckhookdeck
Create a destination in the Console or via the API and subscribe to the events you care about: 
POST /v2/event-destinations

{
  "name": "Production Webhook",
  "type": "webhook",
  "webhook": {
    "url": "https://your-app.com/webhooks/deck"
  },
  "events": ["credential.verified", "task_run.completed", "task_run.failed"]
}
Use "events": ["*"] to subscribe to everything.

​
Deliveries and retries

Each event is delivered independently to every subscribed destination. For webhooks, return a 2xx within 5 seconds to acknowledge. For cloud destinations, delivery is handled natively. Failed deliveries retry up to 3 times with exponential backoff. If all attempts fail, the destination is set to inactive.

​
Retention

Events are stored for 30 days.

Events reference

Full list of event types by resource.

Destinations & deliveries

Configure destinations, verify webhook signatures, and track delivery status.

Webhook best practices

Build reliable, idempotent event consumers.

API reference

Events, destinations, and deliveries endpoints.