OnRamp · HR workflows
In this article we’ll show how to pull employee time-off requests from HiBob into OnRamp, land them in your service collection as records you can query, and then use them for routing, assignment and validation.
Before assigning, check the candidate assignee's active time-off record. If it covers today, assign to the backup.
Block or reroute an approval when the approver is out, so requests do not sit in a queue nobody is watching.
In OnRamp, select Anysource Connection and add a new connection.
Reference API docs: apidocs.hibob.com/reference/time-off
HiBob uses a service user for API access. In the connection’s authentication section:
|
Setting
|
Value
|
|---|---|
|
Type
|
Bearer Token |
|
Header name
|
Basic |
|
Token
|
your HiBob service user ID and token combined into a single string, separated by a colon (:) |
The token is the HiBob service user ID and token joined as SERVICE-USER-ID:TOKEN.
For creating the service user and generating the token, see HiBob’s authorization docs: https://apidocs.hibob.com/reference/authorization
The endpoint we want is GET /v1/timeoff/whosout, documented at https://apidocs.hibob.com/reference/get_timeoff-whosout. It returns time off information for a given date range, limited to the users the service user can access.
|
Setting
|
Value
|
|---|---|
|
Method
|
GET |
|
URL
|
|
|
Query Params
|
from={created_date}&to={last_successful_date} |
|
Response data
|
outs |
The {created_date} and {last_successful_date} tokens let the connection run incrementally: each poll picks up where the last successful run left off, rather than re-pulling the same window every time.
Save the connection and hit Run Test to see results.
{
"outs": [
{
"date": "2025-08-04",
"policyTypeDisplayName": "Holiday",
"visibility": "Public",
"requestId": 42016823,
"minutes": 30,
"policyType": "type6",
"employeeId": "2911111434173677987",
"employeeDisplayName": "TestRequest User",
"hoursOnDate": 5,
"type": "hours",
"status": "approved"
},
{
"policyTypeDisplayName": "Holiday",
"visibility": "Public",
"endDate": "2025-08-06",
"requestId": 42016838,
"policyType": "type43",
"startPortion": "all_day",
"employeeId": "2911111434173677987",
"employeeDisplayName": "TestRequest User",
"endPortion": "morning",
"type": "days",
"startDate": "2025-08-05",
"status": "approved"
}
]
}
Create a Flow and set Anysource Records as the event trigger. Every record the connection returns will now fire the flow.
Refer to https://apidocs.hibob.com/reference/get_timeoff-whosout for the full list of API response fields.
The time-off details are now on a ticket, which means they’re available to every workflow, automation and validation rule in your service collection. Some concrete starting points:
before assigning, look up the candidate assignee's active time-off record. If one exists and covers today, assign to the backup.
block or reroute an approval transition when the approver has an approved absence overlapping the request date.
when a requester follows up on a ticket whose assignee is out, post the expected return date instead of leaving them guessing.
a simple "who's out this week, by team" view built from the same records, next to the queue it affects.

From HiBob time off to a JSM leave request, start to finish.
If you use HiBob, set this up and tell us how it goes. OnRamp is available in the Atlassian Marketplace.
Whatever range you ask for. The from and to query parameters define the window, so pointing them at past dates returns past absences. Using {created_date} and {last_successful_date} as we’ve done here gives you an incremental forward-looking pull, which is what you want for operational routing. If you need history for reporting, run a one-off connection with a fixed backdated range.
HiBob’s API expects an HTTP Basic authorization header built from SERVICE-USER-ID:TOKEN. Setting the type to Bearer Token in OnRamp with the header name Basic produces exactly that header shape. Follow the configuration as written — it’s the combination that works, even though the two labels look like they’re in tension.
Almost always permissions, not configuration. The Who’s Out endpoint only returns time off for employees the service user is allowed to see, and it covers active users. Check the service user’s permission group in HiBob. Also confirm whether the missing records are private (includePrivate), pending (includePending) or hourly (includeHourly) — all three are excluded by default.
Yes. The pattern here — Anysource connection, incremental date-range pull, Anysource Records trigger, field mapping onto custom fields — isn’t specific to absences. Any HiBob endpoint that returns a list you can key by employee works the same way: employment changes, org structure, custom table entries. Time off is just the one with the most immediate payoff for a service desk.
Yes. The Anysource connection in OnRamp works with any REST endpoint that returns JSON, so point it at your HRIS’s time-off or absence API, map the fields, and reuse the same flow. The same HR connections also feed JSM Assets and Teamwork Graph through OnLink.
Absence data next to your tickets
OnRamp pulls HiBob time off into Jira Service Management and uses it for routing and approvals. Try it free on the Atlassian Marketplace.
If you use HiBob, set this up and tell us how it goes. OnRamp is available in the Atlassian Marketplace. Onboarding and offboarding templates, Anysource connections and 100+ HR integrations.
With time-off data in your service collection:
RELATED