Start free
ActionPersonioUpdated June 2026

How do I list Personio time-off requests?

Short answer: You can list personio absences in Personio by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Personio List Personio Absences action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Personio Absences in Personio — start free All 2 Personio actions
List Personio Absences in Personio — start free
Inputs

The fields this action accepts.

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

FieldTypeRequiredDescription
Start Date (YYYY-MM-DD)
start_date
stringRequired–
End Date
end_date
stringRequired–
Sample request
{
  "start_date": "{{trigger.start_date}}",
  "end_date": "{{trigger.end_date}}"
}
Returns
{
  "data": [
    {
      "type": "TimeOffPeriod",
      "attributes": {
        "id": 1,
        "status": "approved",
        "employee": {
          "attributes": {
            "id": {
              "value": 42
            }
          }
        },
        "days_count": 5
      }
    }
  ],
  "success": true
}

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

Triggered by

Apps that pair well as the trigger for List Personio Absences.

Any of these apps can fire this action as part of a workflow.

Gmail → Personio
1 Gmail triggers
Slack → Personio
13 Slack triggers
Google Sheets → Personio
2 Google Sheets triggers
HubSpot → Personio
18 HubSpot triggers
FAQ

Questions about List Personio Absences.

What does the List Personio Absences action do in Personio?
Returns absence records — vacation, sick leave, parental leave. For team-capacity workflows and for "who is out this week" alerting.
What inputs does List Personio Absences require?
Required: Start Date (YYYY-MM-DD), End Date. 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 Personio 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 Personio Absences support batch operations?
Yes. Run List Personio Absences inside a Loop node to process arrays. TinyCommand handles Personio's rate limits automatically so you don't have to throttle manually.
More actions

Other Personio actions.

Action
List Personio Employees
Paginated employee records with field-scoping. For sync workflows that mirror Personio HRIS to other directories.
List Personio Absences in Personio — start free