Overview
Connect Lever with Flows360
Lever is a modern, collaborative recruiting platform that powers a more human approach to hiring.
Use the Lever connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 6 actions and no declared triggers.
Available actions
- Get opportunity
- Update opportunity stage
- List opportunity forms
- List opportunity feedback
- Add feedback to opportunity
- Custom API Call
Available triggers
- No triggers are declared in this pinned package.
The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.
Technical guide
Technical reference
Package identity
- Connector: Lever
- Package:
@activepieces/piece-lever@0.2.0 - Exact artifact digest:
sha256:19bffd8dbaf35ba8ebff4e0f021999fab9266116659d6019fdfbc435b7377e93 - Runtime: Activepieces-compatible deterministic worker
- Source: the exact reviewed Activepieces source
Authentication
CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.
Action contracts
- Get opportunity (
getOpportunity), Retrieve a single opportunity, i.e. an individual's unique candidacy or journey for a given job position Classification: read. - Update opportunity stage (
updateOpportunityStage), Change an Opportunity's current stage Classification: read. - List opportunity forms (
listOpportunityForms), Get all forms for a given opportunity, optionally for a given form template Classification: read. - List opportunity feedback (
listOpportunityFeedback), Get all feedback for a given opportunity, optionally for a given template Classification: read. - Add feedback to opportunity (
addFeedbackToOpportunity), Provide feedback to a candidate after an interview Classification: read. - Custom API Call (
custom_api_call), Make a custom API call to a specific endpoint Classification: read.
Trigger contracts
- No trigger delivery contracts are declared.
Verification
Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.
Capability summary
Authentication
Authentication method: custom
Authentication profiles
connection · custom
- API key Required · protected credential
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Get opportunity | Yes | No | Retrieve a single opportunity, i.e. an individual's unique candidacy or journey for a given job position |
| Update opportunity stage | Yes | No | Change an Opportunity's current stage |
| List opportunity forms | Yes | No | Get all forms for a given opportunity, optionally for a given form template |
| List opportunity feedback | Yes | No | Get all feedback for a given opportunity, optionally for a given template |
| Add feedback to opportunity | Yes | No | Provide feedback to a candidate after an interview |
| Custom API Call | Yes | No | Make a custom API call to a specific endpoint |
Supported actions
Get opportunity · Read
Retrieve a single opportunity, i.e. an individual's unique candidacy or journey for a given job position
get_opportunity · Risk: low · Retry: safe
Inputs
opportunityId· string · Requiredexpand· array · Optional
Update opportunity stage · Read
Change an Opportunity's current stage
update_opportunity_stage · Risk: low · Retry: safe
Inputs
opportunityId· string · Requiredstage· string · Required
List opportunity forms · Read
Get all forms for a given opportunity, optionally for a given form template
list_opportunity_forms · Risk: low · Retry: safe
Inputs
opportunityId· string · Requiredtemplate· string · Optional
List opportunity feedback · Read
Get all feedback for a given opportunity, optionally for a given template
list_opportunity_feedback · Risk: low · Retry: safe
Inputs
opportunityId· string · Requiredtemplate· string · Optional
Add feedback to opportunity · Read
Provide feedback to a candidate after an interview
add_feedback_to_opportunity · Risk: low · Retry: safe
Inputs
performAs· string · RequiredopportunityId· string · RequiredpanelId· string · Optional, If you select one, you must select an interview toointerviewId· string · Optional, Mandatory is you select an interview panelfeedbackTemplateId· string · Optional, Ignored if you select an interview panel and an interviewfeedbackFields· object · Required
Custom API Call · Read
Make a custom API call to a specific endpoint
custom_api_call · Risk: low · Retry: safe
Inputs
url· object · Requiredmethod· string · Requiredheaders· object · Optional, Authorization headers are injected automatically from your connection.queryParams· object · Optional, Appended to the URL as ?key=value.body_type· string · Optionalbody· object · Optionalresponse_is_binary· boolean · Optional, Enable for files like PDFs, images, etc.failsafe· boolean · Optional, On a failed request, output the error instead of failing the step.timeout· number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).followRedirects· boolean · Optional, Follow 3xx redirects instead of returning them as the response.
Setup
Setup
- Add the Lever connector to the workflow in the target Flows360 Studio instance.
- Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
- Provide the connection fields declared by the pinned package:
- API key (
apiKey), required; stored as a sensitive connection value.
- Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
- Test the workflow in the appropriate environment before enabling production scheduling or event delivery.
Limitations
Limitations and operational notes
- This content describes
@activepieces/piece-lever@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes. - Only the 6 actions and 0 triggers declared by this pinned package are represented here.
- Tenant credentials and connection values are not stored in the public connector record.
- Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
- Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.
Troubleshooting
Why canu2019t the connector authenticate?
Check the tenant connection in Studio and confirm every required Lever connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.
Why is an action or trigger unavailable?
Confirm that the workflow is using @activepieces/piece-lever@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.
What should I check after a provider-side change?
Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.