Onfleet · Arazzo Workflow

Onfleet Provision Delivery Task

Version 1.0.0

Create a recipient and destination, then create a delivery task and confirm it.

1 workflow 3 source APIs 1 provider
View Spec View on GitHub Last Mile DeliveryLogisticsFleet ManagementDispatchRoute OptimizationCouriersDriversTrackingGeocodingWebhookArtificial IntelligenceSoftware-as-a-ServiceArazzoWorkflows

Provider

onfleet

Workflows

provision-delivery-task
Create recipient, create destination, create task, then read it back.
Resolves the customer and address into reusable Onfleet resources and then creates and confirms a single dropoff task referencing both.
4 steps inputs: completeAfter, completeBefore, destinationNotes, recipientName, recipientNotes, recipientPhone, taskNotes, unparsedAddress outputs: destinationId, recipientId, taskId, trackingURL
1
createRecipient
Create the end customer who will receive the delivery.
2
createDestination
Geocode and store the delivery address as a reusable destination.
3
createTask
Create the dropoff task binding the recipient and destination.
4
confirmTask
Read the created task back to confirm provisioning and capture tracking.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Onfleet Provision Delivery Task
  summary: Create a recipient and destination, then create a delivery task and confirm it.
  description: >-
    The canonical Onfleet last-mile setup flow. It creates the end customer as a
    reusable recipient, geocodes and stores the delivery address as a
    destination, creates a dropoff task that binds the recipient and destination
    together with a completion window, and then re-reads the task to confirm it
    was provisioned and to capture its tracking URL. Every step spells out its
    request inline so the flow can be read and executed without opening the
    underlying OpenAPI descriptions.
  version: 1.0.0
  x-realizes-capability-ids:
  - BC-2420.40
  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-2420.40
      capability_name: Last-Mile Delivery Operations Management
      spec: onfleet-tasks-api-openapi.yml
      confidence: 0.8
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: destinationsApi
  url: ../openapi/onfleet-destinations-api-openapi.yml
  type: openapi
- name: recipientsApi
  url: ../openapi/onfleet-recipients-api-openapi.yml
  type: openapi
- name: tasksApi
  url: ../openapi/onfleet-tasks-api-openapi.yml
  type: openapi
workflows:
- workflowId: provision-delivery-task
  summary: Create recipient, create destination, create task, then read it back.
  description: >-
    Resolves the customer and address into reusable Onfleet resources and then
    creates and confirms a single dropoff task referencing both.
  inputs:
    type: object
    required:
    - recipientName
    - recipientPhone
    - unparsedAddress
    properties:
      recipientName:
        type: string
        description: The recipient's full name.
      recipientPhone:
        type: string
        description: The recipient's phone number in E.164 format.
      recipientNotes:
        type: string
        description: Optional delivery notes about the recipient.
      unparsedAddress:
        type: string
        description: A single-line street address Onfleet will geocode.
      destinationNotes:
        type: string
        description: Optional notes about the destination (gate code, etc.).
      completeAfter:
        type: integer
        description: Earliest completion time in Unix milliseconds.
      completeBefore:
        type: integer
        description: Latest completion time in Unix milliseconds.
      taskNotes:
        type: string
        description: Optional notes shown to the assigned worker.
  steps:
  - stepId: createRecipient
    description: Create the end customer who will receive the delivery.
    operationId: createRecipient
    requestBody:
      contentType: application/json
      payload:
        name: $inputs.recipientName
        phone: $inputs.recipientPhone
        notes: $inputs.recipientNotes
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      recipientId: $response.body#/id
  - stepId: createDestination
    description: Geocode and store the delivery address as a reusable destination.
    operationId: createDestination
    requestBody:
      contentType: application/json
      payload:
        address:
          unparsed: $inputs.unparsedAddress
        notes: $inputs.destinationNotes
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      destinationId: $response.body#/id
  - stepId: createTask
    description: Create the dropoff task binding the recipient and destination.
    operationId: createTask
    requestBody:
      contentType: application/json
      payload:
        destination: $steps.createDestination.outputs.destinationId
        recipients:
        - $steps.createRecipient.outputs.recipientId
        completeAfter: $inputs.completeAfter
        completeBefore: $inputs.completeBefore
        notes: $inputs.taskNotes
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      taskId: $response.body#/id
      shortId: $response.body#/shortId
  - stepId: confirmTask
    description: Read the created task back to confirm provisioning and capture tracking.
    operationId: getTask
    parameters:
    - name: taskId
      in: path
      value: $steps.createTask.outputs.taskId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      state: $response.body#/state
      trackingURL: $response.body#/trackingURL
  outputs:
    recipientId: $steps.createRecipient.outputs.recipientId
    destinationId: $steps.createDestination.outputs.destinationId
    taskId: $steps.createTask.outputs.taskId
    trackingURL: $steps.confirmTask.outputs.trackingURL

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/onfleet-provision-delivery-task-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.