Remote · Arazzo Workflow

Remote Review A Timesheet

Version 1.0.0

Find a submitted timesheet for an employment and approve it or send it back.

1 workflow 1 source API 1 provider
View Spec View on GitHub Global PayrollEORContractor ManagementContractor of RecordPEOHRISRecruitingBenefitsEmploymentHRComplianceWorkforceMCPAI AgentsArazzoWorkflows

Provider

remote-com

Workflows

review-timesheet
Locate a submitted timesheet and approve or send it back.
Lists submitted timesheets for an employment, confirms the first match, and routes to approval or send-back based on the supplied decision.
4 steps inputs: accessToken, decision, employmentId, sendBackReason outputs: approvedStatus, sentBackStatus, timesheetId
1
listTimesheets
List submitted timesheets for the employment.
2
confirmTimesheet
Read the matched timesheet back and branch on the caller's decision.
3
approveTimesheet
Approve the timesheet.
4
sendBackTimesheet
Send the timesheet back for revision with the supplied reason.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Remote Review A Timesheet
  summary: Find a submitted timesheet for an employment and approve it or send it back.
  description: >-
    Routes a submitted timesheet through manager review. The workflow lists the
    employment's submitted timesheets, reads the first match back to confirm its
    period and hours, and then branches on a caller decision flag: an approval
    calls the approve endpoint while a rejection sends the timesheet back for
    revision with a reason. 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-300.70
  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-300.70
      capability_name: HR Operations Management
      spec: remote-com-timesheets-api-openapi.yml
      confidence: 0.75
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: timesheetsApi
  url: ../openapi/remote-com-timesheets-api-openapi.yml
  type: openapi
workflows:
- workflowId: review-timesheet
  summary: Locate a submitted timesheet and approve or send it back.
  description: >-
    Lists submitted timesheets for an employment, confirms the first match, and
    routes to approval or send-back based on the supplied decision.
  inputs:
    type: object
    required:
    - accessToken
    - employmentId
    - decision
    properties:
      accessToken:
        type: string
        description: Company-scoped bearer access token.
      employmentId:
        type: string
        description: The employment whose timesheet is being reviewed.
      decision:
        type: string
        description: Either approve or send_back.
      sendBackReason:
        type: string
        description: Reason used when the decision is send_back.
  steps:
  - stepId: listTimesheets
    description: List submitted timesheets for the employment.
    operationId: listTimesheets
    parameters:
    - name: Authorization
      in: header
      value: "Bearer $inputs.accessToken"
    - name: employment_id
      in: query
      value: $inputs.employmentId
    - name: status
      in: query
      value: submitted
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      timesheetId: $response.body#/data/timesheets/0/id
    onSuccess:
    - name: hasMatch
      type: goto
      stepId: confirmTimesheet
      criteria:
      - context: $response.body
        condition: $.data.timesheets.length > 0
        type: jsonpath
    - name: noMatch
      type: end
      criteria:
      - context: $response.body
        condition: $.data.timesheets.length == 0
        type: jsonpath
  - stepId: confirmTimesheet
    description: Read the matched timesheet back and branch on the caller's decision.
    operationId: showTimesheet
    parameters:
    - name: Authorization
      in: header
      value: "Bearer $inputs.accessToken"
    - name: timesheet_id
      in: path
      value: $steps.listTimesheets.outputs.timesheetId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      status: $response.body#/data/timesheet/status
      totalHours: $response.body#/data/timesheet/total_hours
    onSuccess:
    - name: approveBranch
      type: goto
      stepId: approveTimesheet
      criteria:
      - condition: $inputs.decision == "approve"
    - name: sendBackBranch
      type: goto
      stepId: sendBackTimesheet
      criteria:
      - condition: $inputs.decision == "send_back"
  - stepId: approveTimesheet
    description: Approve the timesheet.
    operationId: approveTimesheet
    parameters:
    - name: Authorization
      in: header
      value: "Bearer $inputs.accessToken"
    - name: timesheet_id
      in: path
      value: $steps.listTimesheets.outputs.timesheetId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      status: $response.body#/data/timesheet/status
    onSuccess:
    - name: approved
      type: end
  - stepId: sendBackTimesheet
    description: Send the timesheet back for revision with the supplied reason.
    operationId: sendTimesheetBack
    parameters:
    - name: Authorization
      in: header
      value: "Bearer $inputs.accessToken"
    - name: timesheet_id
      in: path
      value: $steps.listTimesheets.outputs.timesheetId
    requestBody:
      contentType: application/json
      payload:
        reason: $inputs.sendBackReason
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      status: $response.body#/data/timesheet/status
  outputs:
    timesheetId: $steps.listTimesheets.outputs.timesheetId
    approvedStatus: $steps.approveTimesheet.outputs.status
    sentBackStatus: $steps.sendBackTimesheet.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/remote-com-review-timesheet-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.