Hookdeck · Arazzo Workflow

Hookdeck Retry a Failed Event

Version 1.0.0

Find the most recent failed event, inspect it, and retry delivery.

1 workflow 1 source API 1 provider
View Spec View on GitHub WebhookEvent GatewaysGatewaysEventEvent InfrastructureEvent-DrivenMessagingQueuesRetriesTransformationObservabilityArazzoWorkflows

Provider

hookdeck

Workflows

retry-failed-event
Locate a failed event and trigger a fresh delivery attempt.
Lists failed events, branches when none exist, otherwise reads the first failed event and retries it, capturing the new attempt id.
3 steps inputs: limit, webhookId outputs: retriedEventId, retriedEventStatus
1
listFailedEvents
List events with a FAILED status, optionally scoped to a single connection, ordered so the most recent failure is first.
2
readEvent
Retrieve the failed event to capture its connection, destination, and current attempt count before retrying.
3
retryEvent
Retry the event, causing Hookdeck to make a new delivery attempt to the destination.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Hookdeck Retry a Failed Event
  summary: Find the most recent failed event, inspect it, and retry delivery.
  description: >-
    A core operations flow for recovering from a failed webhook delivery. The
    workflow lists events filtered to the FAILED status, branches on whether any
    were found, reads the top failed event to capture its delivery context, then
    retries it so a new delivery attempt is made to the destination. Every step
    spells out its request inline so the flow can be read and executed without
    opening the underlying OpenAPI description.
  version: 1.0.0
  x-realizes-capability-ids:
  - BC-4270.80
  x-capability-derivation:
    method: 'deterministic join: sourceDescriptions -> per-tag OpenAPI -> tag/capability edge. No classification at this step.'
    min_confidence: 0.7
    sources:
    - capability_id: BC-4270.80
      capability_name: Webhook & Event Subscription Management
      spec: hookdeck-events-api-openapi.yml
      confidence: 0.7
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: eventsApi
  url: ../openapi/hookdeck-events-api-openapi.yml
  type: openapi
workflows:
- workflowId: retry-failed-event
  summary: Locate a failed event and trigger a fresh delivery attempt.
  description: >-
    Lists failed events, branches when none exist, otherwise reads the first
    failed event and retries it, capturing the new attempt id.
  inputs:
    type: object
    properties:
      webhookId:
        type: string
        description: Optional connection (webhook) id to scope the failed-event search.
      limit:
        type: integer
        description: Maximum number of failed events to retrieve.
        default: 1
  steps:
  - stepId: listFailedEvents
    description: >-
      List events with a FAILED status, optionally scoped to a single
      connection, ordered so the most recent failure is first.
    operationId: getEvents
    parameters:
    - name: status
      in: query
      value: FAILED
    - name: webhook_id
      in: query
      value: $inputs.webhookId
    - name: limit
      in: query
      value: $inputs.limit
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      failedEventId: $response.body#/models/0/id
    onSuccess:
    - name: hasFailures
      type: goto
      stepId: readEvent
      criteria:
      - context: $response.body
        condition: $.models.length > 0
        type: jsonpath
    - name: noFailures
      type: end
      criteria:
      - context: $response.body
        condition: $.models.length == 0
        type: jsonpath
  - stepId: readEvent
    description: >-
      Retrieve the failed event to capture its connection, destination, and
      current attempt count before retrying.
    operationId: getEvent
    parameters:
    - name: id
      in: path
      value: $steps.listFailedEvents.outputs.failedEventId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      eventId: $response.body#/id
      webhookId: $response.body#/webhook_id
      destinationId: $response.body#/destination_id
      attempts: $response.body#/attempts
  - stepId: retryEvent
    description: >-
      Retry the event, causing Hookdeck to make a new delivery attempt to the
      destination.
    operationId: retryEvent
    parameters:
    - name: id
      in: path
      value: $steps.readEvent.outputs.eventId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      eventId: $response.body#/id
      newStatus: $response.body#/status
  outputs:
    retriedEventId: $steps.retryEvent.outputs.eventId
    retriedEventStatus: $steps.retryEvent.outputs.newStatus

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/hookdeck-retry-failed-event-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.