Short answer: Drop the "Lever → List Lever Opportunities" 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 |
|---|---|---|---|
Limit limit | string | Optional | — |
Stage ID filter stage_id | string | Optional | — |
Posting ID filter posting_id | string | Optional | The Posting ID filter assigned by Lever. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
{"limit": "{{trigger.limit}}","stage_id": "{{trigger.stage_id}}","posting_id": "{{trigger.posting_id}}"}
{"data": [{"id": "abc","name": "Jane Doe","stage": {"text": "Phone Screen"},"emails": ["jane@x.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.
Triggered by anything in the catalog. Free tier available. No credit card.