Short answer: Drop the "BambooHR → Request Time Off" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Employee ID employeeId | string | Required | Employee ID |
Start Date start | date | Required | Start Date. (date/time) |
End Date end | date | Required | End Date. (date/time) |
Time Off Type ID timeOffTypeId | string | Required | e.g. 1 for Vacation |
Notes notes | string | Optional | Notes |
{"employeeId": "{{trigger.employeeId}}","start": "{{trigger.start}}","end": "{{trigger.end}}","timeOffTypeId": "{{trigger.timeOffTypeId}}","notes": "{{trigger.notes}}"}
{"id": 456,"status": "requested"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.