CDK Global · Arazzo Workflow

CDK Global Relay Appointment Event

Version 1.0.0

Read a service appointment, then relay it as an event to an event sink.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub AutomotiveDealer ManagementDMSAuto RetailF&IFixed OperationsPartsCRMDigital RetailMarketplaceDeveloper PlatformEventWebhookAsyncAPIArazzoWorkflows

Provider

cdk-global

Workflows

relay-appointment-event
Read an appointment and publish it to an event relay channel.
Loads a service appointment by identifier and posts its key fields as an event onto the supplied relay channel for downstream sinks.
2 steps inputs: appointmentId, authorization, channel, dataOwnerId, fortellisEventId, requestId, sinkAuthorization, subscriptionId outputs: relayStatus, relayedAppointmentId
1
loadAppointment
Read the service appointment that will be relayed as an event.
2
relayEvent
Post the appointment payload as an event onto the relay channel for the event sink to process asynchronously.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: CDK Global Relay Appointment Event
  summary: Read a service appointment, then relay it as an event to an event sink.
  description: >-
    Bridges the service appointments API and the Fortellis Event Relay webhook.
    The workflow reads a service appointment by its identifier and then posts the
    appointment payload as an event onto a relay channel for an event sink to
    consume asynchronously. The event payload is a free-form object per the relay
    contract, so the appointment fields are carried as-is. 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
sourceDescriptions:
- name: eventsApi
  url: ../openapi/cdk-global-events-api-openapi.yml
  type: openapi
- name: queryApi
  url: ../openapi/cdk-global-query-api-openapi.yml
  type: openapi
workflows:
- workflowId: relay-appointment-event
  summary: Read an appointment and publish it to an event relay channel.
  description: >-
    Loads a service appointment by identifier and posts its key fields as an
    event onto the supplied relay channel for downstream sinks.
  inputs:
    type: object
    required:
    - subscriptionId
    - requestId
    - authorization
    - appointmentId
    - channel
    - fortellisEventId
    - sinkAuthorization
    properties:
      subscriptionId:
        type: string
        description: The Fortellis Marketplace subscription identifier.
      requestId:
        type: string
        description: A correlation GUID echoed back across systems.
      authorization:
        type: string
        description: The Fortellis token for the appointments API.
      appointmentId:
        type: string
        description: The identifier of the appointment to relay.
      channel:
        type: integer
        description: The relay channel the event was posted on.
      fortellisEventId:
        type: string
        description: The unique Fortellis-assigned event identifier (UUID).
      sinkAuthorization:
        type: string
        description: The credentials the relay uses to authenticate to the event sink.
      dataOwnerId:
        type: string
        description: The Fortellis Organization Id the event represents (UUID).
  steps:
  - stepId: loadAppointment
    description: >-
      Read the service appointment that will be relayed as an event.
    operationId: queryAppointment
    parameters:
    - name: appointmentId
      in: path
      value: $inputs.appointmentId
    - name: Request-Id
      in: header
      value: $inputs.requestId
    - name: Subscription-Id
      in: header
      value: $inputs.subscriptionId
    - name: Authorization
      in: header
      value: $inputs.authorization
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      appointmentId: $response.body#/appointmentId
      dateTime: $response.body#/dateTime
      customerHref: $response.body#/customerHref
      vehicleHref: $response.body#/vehicleHref
  - stepId: relayEvent
    description: >-
      Post the appointment payload as an event onto the relay channel for the
      event sink to process asynchronously.
    operationId: postEvent
    parameters:
    - name: channel
      in: path
      value: $inputs.channel
    - name: X-Request-Id
      in: header
      value: $inputs.requestId
    - name: Fortellis-Event-Id
      in: header
      value: $inputs.fortellisEventId
    - name: Authorization
      in: header
      value: $inputs.sinkAuthorization
    - name: Data-Owner-Id
      in: header
      value: $inputs.dataOwnerId
    requestBody:
      contentType: application/json
      payload:
        appointmentId: $steps.loadAppointment.outputs.appointmentId
        dateTime: $steps.loadAppointment.outputs.dateTime
        customerHref: $steps.loadAppointment.outputs.customerHref
        vehicleHref: $steps.loadAppointment.outputs.vehicleHref
    successCriteria:
    - condition: $statusCode == 202
    outputs:
      statusCode: $statusCode
  outputs:
    relayedAppointmentId: $steps.loadAppointment.outputs.appointmentId
    relayStatus: $steps.relayEvent.outputs.statusCode

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/cdk-global-relay-appointment-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.