Lever: Create a candidate

🕙  7 minute read

Use this action to create a new candidate in your Lever account. You can configure all default fields in Lever. Most fields are optional, except for the Perform as field.

How to configure this action

This action requires a preconfigured Lever integration. For more information on integrating Catalytic 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.
  • Name

    • Enter the candidate full, first and last name.
  • Tags

    • Enter a tag to apply to the candidate. Only 1 tag can be added at a time.
    • If you enter a tag that does not exist, it will be created and added to the candidate.
  • Type

    • Set how this candidate was added to Lever. Can be one of the following values: mobile, home, work, skype, other.
    • Enter a contact link, such as a personal website or LinkedIn profile.
  • Owner

    • The user ID of the owner of this candidate. If not specified, candidate owner defaults to the Perform as user.
    • Here are two ways to find an Owner ID:
  • Parse

    • This field determines if data should be parsed from a relevant resume. This is not applicable at this tiem.
  • Stage

    • Enter the stage ID for the new candidate, such as lead-reached-out for Reached out, or applicant-new for New Applicant. If left blank, the candidate is placed into the “New Lead” stage.
    • Here are two ways to find a Stage ID:
  • Value

    • Enter the candidate phone number. The number must be formatted as (123) 456-7891.
  • Emails

    • Enter an email for the candidate, such as Art@Vandelay.com
  • Origin

    • Set how this candidate was added to Lever. Can be one of the following values: agency, applied, internal, referred, sourced, university.
  • Reason

    • Enter a reason ID if you would like the created candidate to be archived. The reason ID is the ID associated with an archived stage, such as “Hired” or “Offer Declined”
    • Here are two ways to find a Reason ID:
  • Sources

    • Enter the source of where the candidate application originated from. For example, LinkedIn or Indeed.
  • Headline

    • Enter the candidate headline. This is typically a list of previous companies or universities, or other relevant credentials.
  • Location

    • Enter the candidate location, such as Oakland, CA.
  • Postings

  • Created at

    • Enter the date and time that the candidate was considered created. Leave blank to set to the current time. It’s not possible to set a time in the future.
    • This must be formatted using a Unix timestamp, such as 1595371739. unixtimestamp.com has a helpful converter for getting the correct timestamps.
  • Followers

    • Enter a user ID for any user you wish to add as a follower for the new candidate. The candidate creator will always be added as a follower.
    • Here are two ways to find a User ID:
    • Use an action
    • Find the ID manually from the URL
  • Archived at

    • Enter the date and time that the candidate was considered archived. This must be formatted using a Unix timestamp, such as 1595371739. unixtimestamp.com has a helpful converter for getting the correct timestamps.
    • Archived Reason must be set for Archived at to be recognized. If you just set the Archived at without setting Reason, it will be ignored.
  • 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. By default, the creator and the owner of this Candidate will default to the user specified in this field.
  • 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.
  • Perform as posting owner

    • All changes in Lever are said to be “performed” by a user. Set whether the associated job posting owner or the User specified in the Perform as field should be the user who performs this action in Lever.
      • Set to false or leave blank and the candidate owner will default to the user set in the Perform as field.
      • Set to true the owner of the job posting specified in the Posting field will be set as the candidate owner. If the posting does not have an owner, the candidate owner will default to the Perform as user.

What will this output?

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 application. 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.

Sorry about that. What was the most unhelpful part?









Thanks for your feedback

We update the Help Center daily, so expect changes soon.

Link Copied

Paste this URL anywhere to link straight to the section.