List Time-Off Requests: Gusto action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Company ID company_id	string	Required	—

Sample request

{
  "company_id": "{{trigger.company_id}}"
}

Returns

[
  {
    "id": "to_abc",
    "days": [
      {
        "date": "2026-05-15"
      }
    ],
    "status": "approved",
    "employee": {
      "id": "emp_abc"
    },
    "request_type": "vacation"
  }
]

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List Time-Off Requests.

What does the List Time-Off Requests action do in Gusto?

Returns vacation/sick/PTO requests with status, dates, type, approver. For "team capacity this week" planning workflows or for "alert when key person is out" coverage automation.

What inputs does List Time-Off Requests require?

Required: Company ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Gusto returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Time-Off Requests support batch operations?

Yes. Run List Time-Off Requests inside a Loop node to process arrays. Tiny Command handles Gusto's rate limits automatically so you don't have to throttle manually.

More actions