Short answer: You can get rippling employee in Rippling by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Rippling Get Rippling Employee action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Employee ID employee_id | string | Required | The Employee ID assigned by Rippling. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
{"employee_id": "{{trigger.employee_id}}"}
{"id": "abc","manager": {"id": "mgr_abc"},"lastName": "Doe","firstName": "Jane","workEmail": "jane@acme.com"}
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.