Short answer: Drop the "BambooHR → Get Employee" 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 |
Fields fields | string | Optional | Comma-separated field names |
{"employeeId": "{{trigger.employeeId}}","fields": "{{trigger.fields}}"}
{"id": "123","hireDate": "2024-01-15","jobTitle": "Software Engineer","lastName": "Doe","firstName": "John","workEmail": "john@company.com","department": "Engineering"}
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.