Workday Finance · Arazzo Workflow

Workday Finance Onboard Supplier and Raise Purchase Order

Version 1.0.0

Resolve a supplier, confirm it is active, then raise a purchase order against it.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub AccountingCloudEnterpriseERPFinanceFinancial ManagementArazzoWorkflows

Provider

workday-finance

Workflows

onboard-supplier-purchase-order
Confirm a supplier then raise and verify a purchase order against it.
Looks up the supplier, branches on its active status, creates a purchase order referencing the supplier, and reads the new purchase order back to confirm it was recorded.
3 steps inputs: lines, orderDate, supplierId, token outputs: purchaseOrderId, purchaseOrderStatus, supplierId
1
getSupplier
Read the supplier account to confirm it exists before raising an order against it.
2
createPurchaseOrder
Create a purchase order that references the confirmed supplier and the supplied order lines.
3
confirmPurchaseOrder
Read the newly created purchase order back to confirm it was persisted and capture its current status.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Workday Finance Onboard Supplier and Raise Purchase Order
  summary: Resolve a supplier, confirm it is active, then raise a purchase order against it.
  description: >-
    A procure-to-pay starter flow. The workflow reads a supplier account to
    confirm it exists and is active, then creates a purchase order that
    references that supplier with one or more order lines, and finally reads the
    created purchase order back to confirm its status. 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: purchaseOrdersApi
  url: ../openapi/workday-finance-purchase-orders-api-openapi.yml
  type: openapi
- name: suppliersApi
  url: ../openapi/workday-finance-suppliers-api-openapi.yml
  type: openapi
workflows:
- workflowId: onboard-supplier-purchase-order
  summary: Confirm a supplier then raise and verify a purchase order against it.
  description: >-
    Looks up the supplier, branches on its active status, creates a purchase
    order referencing the supplier, and reads the new purchase order back to
    confirm it was recorded.
  inputs:
    type: object
    required:
    - token
    - supplierId
    - orderDate
    - lines
    properties:
      token:
        type: string
        description: OAuth 2.0 bearer access token for the Workday tenant.
      supplierId:
        type: string
        description: The unique identifier of the supplier to order from.
      orderDate:
        type: string
        description: The order date for the purchase order (YYYY-MM-DD).
      lines:
        type: array
        description: The order lines (item, quantity, unitCost) for the purchase order.
  steps:
  - stepId: getSupplier
    description: >-
      Read the supplier account to confirm it exists before raising an order
      against it.
    operationId: getSupplier
    parameters:
    - name: Authorization
      in: header
      value: Bearer $inputs.token
    - name: supplierId
      in: path
      value: $inputs.supplierId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      supplierId: $response.body#/id
      status: $response.body#/status
    onSuccess:
    - name: supplierActive
      type: goto
      stepId: createPurchaseOrder
      criteria:
      - context: $response.body
        condition: $.status == "active"
        type: jsonpath
    - name: supplierInactive
      type: end
      criteria:
      - context: $response.body
        condition: $.status != "active"
        type: jsonpath
  - stepId: createPurchaseOrder
    description: >-
      Create a purchase order that references the confirmed supplier and the
      supplied order lines.
    operationId: createPurchaseOrder
    parameters:
    - name: Authorization
      in: header
      value: Bearer $inputs.token
    requestBody:
      contentType: application/json
      payload:
        supplier: $steps.getSupplier.outputs.supplierId
        orderDate: $inputs.orderDate
        lines: $inputs.lines
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      purchaseOrderId: $response.body#/id
      purchaseOrderNumber: $response.body#/purchaseOrderNumber
      status: $response.body#/status
  - stepId: confirmPurchaseOrder
    description: >-
      Read the newly created purchase order back to confirm it was persisted
      and capture its current status.
    operationId: getPurchaseOrder
    parameters:
    - name: Authorization
      in: header
      value: Bearer $inputs.token
    - name: purchaseOrderId
      in: path
      value: $steps.createPurchaseOrder.outputs.purchaseOrderId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      purchaseOrderId: $response.body#/id
      status: $response.body#/status
      totalAmount: $response.body#/totalAmount
  outputs:
    supplierId: $steps.getSupplier.outputs.supplierId
    purchaseOrderId: $steps.confirmPurchaseOrder.outputs.purchaseOrderId
    purchaseOrderStatus: $steps.confirmPurchaseOrder.outputs.status

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/workday-finance-onboard-supplier-purchase-order-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.