Lever: Update a candidates archived state

Use this action to change the archived reason for a candidate. A archive reason is one of the seven default reasons for archiving a candidate, such as Offer declined or Withdrew. This will replace the existing stage.

How to configure this action

This action requires a preconfigured Lever integration. For more information on integrating PagerDuty Workflow Automation with other systems, please refer to the Integrations section of our help documentation.

Fields for this action

• Integration

  • Select your Lever integration from the options. You may have multiple integrations configured.

• Reason

  • Enter the reason ID to update the candidate’s reason to.
    • If a single reason is set, results will only include candidates associated with that specific reason.
    • If multiple reasons are set, results will only include any candidate in at least one of the specified reasons.
  • Here are two ways to find a Reason ID:
  • Use an action
    • Use the Lever: List all archive reasons in your Lever account action to list all archive reasons in your Lever account. The action outputs a List of candidates data table field with all reasons and reason IDs.
  • Find the ID manually from the URL
    • You can find the ID when viewing the archived stages on the candidates screen in Lever. See How to manually retrieve a Reason ID for more information.

• Candidate

  • Enter the User ID for the candidate you wish to retrieve.
  • Here are two ways to find a User ID:
  • Use an action
    • Use the Lever: Lists all pipeline candidates in your Lever account action to list all candidates in your Lever account. The action outputs a List of candidates data table field with all candidates and their Lever information.
  • Find the ID manually from the URL
    • You can find the ID when viewing the a user’s profile in Lever. See How to manually retrieve a User ID for more information.

• Perform as

  • All changes in Lever are said to be “performed” by a user. Enter a User ID for the user you wish to appear as performing this action.

• Clean interviews

  • Set whether to remove pending interviews from candidate after candidate is archived.
    • Select true to remove pending interviews.
    • Select false or leave blank to leave interviews as is.

• Output Field Prefix

  • To help keep output fields organized, choose an output field prefix to add to the beginning of each output field name as this action may output more than one field.
  • The step’s name is used as the prefix by default.

What will this output?

This action outputs many additional fields depending on the information available for the candidate. The fields below are the standard fields Lever returns, but extra fields may also be available. Test the action to see what fields are available to you.

This action may generate multiple fields. To help keep output fields organized, the prefix above will be added to the beginning of each of the output field names, separated by two dashes. Each field will result as:{{output-field-prefix--output-field}}

Output fields for this action

• Candidate application

  • The ID for the candidates. This is related to the posting specified during configuration.

• Archived

  • True or false for whether the candidate is archived.

• Contact

  • The contact ID is an ID created by Lever to identify an individual person, even if that person is a candidate in multiple postings or opportunities.

• Data protection

  • Contains the candidate’s data protection status, if this is enabled. If there is no policy, this will be blank.

• Email

  • A data table field with a list of candidate emails.

• Followers

  • A data table field with a list of assigned follower user IDs.

• Headline

  • The candidate’s headline, if any.

• Candidate ID

  • The candidate’s user ID.

• Is anonymized?

  • Indicates whether the candidates data is anonymized. This is not controllable using this action so this will always be false.

• Profile URLs on other sites

  • A data table field with a list of candidate profile URLs.

• Location

  • The candidate’s location, if any.

• Name

  • The candidate’s full name.

• Origin

  • The candidate’s origin, if any.

• Owner

  • The user ID of the owner assigned to the candidate.

• Phones

  • A data table field with a list of phone numbers for the candidate.

• Sources

  • The candidate’s sources, if any.

• Stage

  • The candidate’s current stage ID.

• Stage changes

  • A table summarizing the stage the candidate was assigned to. The table lists the stage ID, a stage index number, the time Unix time the stage was set, and the candidate owner ID.

• Tags

  • A data table field with a list of tags associated with the candidate.

• Lever Candidate URL

  • The full URL to access the candidates account page.