Ramp · Arazzo Workflow

Ramp Map Users To Departments

Version 1.0.0

Pull the user, department, and location directories to build an org spend map.

1 workflow 3 source APIs 1 provider
View Spec View on GitHub FinanceSpend ManagementCorporate CardsExpense ManagementAccounts PayableBill PayAccountingReimbursementArazzoWorkflows

Provider

ramp

Workflows

map-users-to-departments
List users and the department and location directories to resolve their references.
Lists users and then the department and location directories so each user's department_id and location_id can be resolved to names.
3 steps inputs: accessToken outputs: departments, locations, users
1
listUsers
List the organization's users and capture each user's department and location references.
2
listDepartments
List the organization's departments so user department_id references can be resolved to department names.
3
listLocations
List the organization's locations so user location_id references can be resolved to location names.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Ramp Map Users To Departments
  summary: Pull the user, department, and location directories to build an org spend map.
  description: >-
    Assembles the reference data needed to roll spend up by organizational
    unit. The workflow lists users, then lists departments and locations so a
    caller can join each user's department_id and location_id against the
    department and location directories. This produces the lookup tables that
    let reporting attribute card and reimbursement spend to the right
    department and location. 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: departmentsApi
  url: ../openapi/ramp-departments-api-openapi.yml
  type: openapi
- name: locationsApi
  url: ../openapi/ramp-locations-api-openapi.yml
  type: openapi
- name: usersApi
  url: ../openapi/ramp-users-api-openapi.yml
  type: openapi
workflows:
- workflowId: map-users-to-departments
  summary: List users and the department and location directories to resolve their references.
  description: >-
    Lists users and then the department and location directories so each
    user's department_id and location_id can be resolved to names.
  inputs:
    type: object
    properties:
      accessToken:
        type: string
        description: OAuth2 client-credentials bearer token with users:read, departments:read, and locations:read scopes.
  steps:
  - stepId: listUsers
    description: >-
      List the organization's users and capture each user's department and
      location references.
    operationId: listUsers
    parameters:
    - name: Authorization
      in: header
      value: Bearer $inputs.accessToken
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      users: $response.body#/data
  - stepId: listDepartments
    description: >-
      List the organization's departments so user department_id references can
      be resolved to department names.
    operationId: listDepartments
    parameters:
    - name: Authorization
      in: header
      value: Bearer $inputs.accessToken
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      departments: $response.body#/data
  - stepId: listLocations
    description: >-
      List the organization's locations so user location_id references can be
      resolved to location names.
    operationId: listLocations
    parameters:
    - name: Authorization
      in: header
      value: Bearer $inputs.accessToken
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      locations: $response.body#/data
  outputs:
    users: $steps.listUsers.outputs.users
    departments: $steps.listDepartments.outputs.departments
    locations: $steps.listLocations.outputs.locations

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/ramp-map-users-to-departments-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.