Short answer: You can get lever opportunity in Lever by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Lever Get Lever Opportunity 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 |
|---|---|---|---|
Opportunity ID opportunity_id | string | Required | – |
{"opportunity_id": "{{trigger.opportunity_id}}"}
{"data": {"id": "abc","name": "Jane Doe","owner": {"name": "Recruiter"},"stage": {"text": "Phone Screen"},"emails": ["jane@x.com"],"phones": [{"value": "+1888"}]}}
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.