Lever: Lists all pipeline candidates in your Lever account

🕙  11 minute read

Use this action to list all candidates in your Lever account, based on different filter criteria. This action outputs a table with a list of Catalytic tables for each candidate, with many related tables with additional information.

This action outputs a table with a row for each candidate, and includes details like when they were created, whether the candidate is archived, or more. This table does not include all candidate details like each phone number, or all the associated tags, but does includes an data table ID for a unique table where more information is stored.

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.
  • Tag

    • Enter a tag to filter candidates by.
      • If a single tag is set, results will only include candidates with the matching tag.
      • If multiple tags are set, results will only include any candidate with at least one of the tags.
  • Email

    • Enter an email address to filter candidates by. If an email is set, results will include candidates with a matching email address.
  • Expand

    • Enter applications, stage, owner, followers, sourcedBy to add additional information about each candidate to the primary data table. Leave blank to omit this additional information.
      • For example, if you enter stage, the primary data table will include additional columns for the stage name and stage last changed.
  • Origin

    • Enter an origin to filter candidates by. The origin is how a candidate was added to Lever. The origin can be one of the following values: agency, applied, internal, referred, sourced, university.
      • If a single origin is set, results will only include candidates with the matching origin.
      • If multiple origins are set, results will only include any candidate with at least one of the origins.
  • Source

    • Enter a source to filter candidates by. The Source is where the candidate originated from. For example, LinkedIn or Indeed.
      • If a single source is set, results will only include candidates with the matching source.
      • If multiple sources are set, results will only include any candidate with at least one of the sources.
  • Include

    • Enter followers to include any candidate followers in the list results. Leave blank to omit these users.
  • Snoozed

    • Select whether to filter candidates based on snoozed status.
      • Set to true to only include snoozed candidates.
      • Set to false or leave blank to include both snoozed and unsnoozed candidates.
  • Archived

    • Select whether to filter candidates based on archived status.
      • Set to true to only include archived candidates.
      • Set to false to exclude archived candidates and only include active candidates.
  • Stage ID

    • Enter a stage ID to filter candidates by a specific stage. If set, only candidates in a specific stage are included, such as lead-reached-out or applicant-new.
      • If a single stage is set, results will only include candidates within that specific stage.
      • If multiple sources are set, results will only include any candidate in at least one of the specified stages.
    • Here are two ways to find a Stage ID:
  • Contact ID

    • Enter a contact ID to filter candidates to a specific 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.
      • If a single contact is set, results will only include candidates with that contact ID.
      • If multiple sources are set, results will only include any candidate with at least one of the contact IDs.
  • Posting ID

    • Select a posting ID to filter candidates by a specific posting. If set, only candidates in a specific posting are included.
      • If a single posting is set, results will only include candidates associated with that specific posting.
      • If multiple postings are set, results will only include any candidate in at least one of the specified postings.
    • Here are two ways to find a Posting ID:
  • Archive reason

    • Select an reason ID to filter candidates by a specific archive reason. If set, only candidates with a specific reason are included. The reason ID is the ID associated with an archived stage, such as Hired or Offer Declined
      • 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:
  • Created at end

    • Enter a time to filter candidates by the timestamps for when they were created. This must be formatted using a Unix timestamp, such as 1595371739. unixtimestamp.com has a helpful converter for getting the correct timestamps.
      • Set just this field, Created at end to include only candidates created from that time and earlier.
      • Set this field, and Created at start to include only candidates created between the start and end times.
  • Updated at end

    • Enter a time to filter candidates by the timestamps for when they were last updated. This must be formatted using a Unix timestamp, such as 1595371739. unixtimestamp.com has a helpful converter for getting the correct timestamps.
      • Set just this field, Updated at end to include only candidates last updated from that time and earlier.
      • Set this field, and Updated at start to include only candidates last updated between the start and end times.
  • Advanced at end

    • Enter a time to filter candidates by the timestamps for when they advanced to their latest stage. This must be formatted using a Unix timestamp, such as 1595371739. unixtimestamp.com has a helpful converter for getting the correct timestamps.
      • Set just this field, Advanced at end to include only candidates that updated to their latest stage from that time and earlier.
      • Set this field, and Advanced at start to include only candidates last updated to their latest stage between the start and end times.
  • Archived at end

    • Enter a time to filter candidates by the timestamps for when they advanced to an archived stage. This must be formatted using a Unix timestamp, such as 1595371739. unixtimestamp.com has a helpful converter for getting the correct timestamps.
      • Set just this field, Archived at end to include only candidates that advanced to an archived stage to from that time and earlier.
      • Set this field, and Archived at end to include only candidates that advanced to an archived stage between the start and end times.
  • Created at start

    • Enter a time to filter candidates by the timestamps for when they were created. This must be formatted using a Unix timestamp, such as 1595371739. unixtimestamp.com has a helpful converter for getting the correct timestamps.
      • Set just this field, Created at start to include only candidates created from that time to the present.
      • Set this field, and Created at end to include only candidates created between the start and end times.
  • Updated at start

    • Enter a time to filter candidates by the timestamps for when they were last updated. This must be formatted using a Unix timestamp, such as 1595371739. unixtimestamp.com has a helpful converter for getting the correct timestamps.
      • Set just this field, Updated at start to include only candidates last updated from that time to the present.
      • Set this field, and Updated at end to include only candidates last updated between the start and end times.
  • Advanced at start

    • Enter a time to filter candidates by the timestamps for when they advanced to their latest stage. This must be formatted using a Unix timestamp, such as 1595371739. unixtimestamp.com has a helpful converter for getting the correct timestamps.
      • Set just this field, Advanced at start to include only candidates that updated to their latest stage from that time to the present.
      • Set this field, and Advanced at end to include only candidates last updated to their latest stage between the start and end times.
  • Archived at start

    • Enter a time to filter candidates by the timestamps for when they advanced to an archived stage. This must be formatted using a Unix timestamp, such as 1595371739. unixtimestamp.com has a helpful converter for getting the correct timestamps.
      • Set just this field, Archived at start to include only candidates that advanced to an archived stage to from that time to the present.
      • Set this field, and Archived at end to include only candidates that advanced to an archived stage between the start and end times.
  • 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.
  • Postings

    • Select an archived posting ID to filter candidates by a specific archived posting. If set, only candidates who applied to a specific posting and then the application was archived will be included.
      • If a single stage is set, results will only include candidates within that specific stage.
      • If multiple sources are set, results will only include any candidate in at least one of the specified stages.
    • Here are two ways to find a Posting ID:

What will this output?

This action outputs a data table with a list of all matching candidates. Each row is a matching candidate, and each column is an attribute of that candidate, such as their current stage, or headline.

Many of the fields are data table IDs with extended information about the field. For example, the stageChanges column is a data table ID for a table that lists all past stage changes, the timestamp, and the stage ID. If a field is a data table ID, use the ID and add it to the end of the url https://<your-team-name>.pushbot.com/tables/61090f15-47c5-4294-8425-b781fa616815, where <your-team-name> is your team name, and 61090f15-47c5-4294-8425-b781fa616815 is the ID in the field column.

To quickly access these nested tables in an action, use an action like Tables: Look up data in a column to find the correct table ID based on the candidate name, then use other table actions to work inside that table.

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

  • List of candidates

    • A data table field with a list of candidates. Each candidate includes the following fields:
      • id: The candidate’s ID.
      • name: The candidate’s full name.
      • contact: The contact ID for the candidate.
      • headline: The candidate’s headline.
      • stage: The stage ID for the candidate’s current stage.
      • location: The candidate’s location.
      • phones: A data table ID for the data table where all the candidate’s phone numbers are listed.
      • emails: A data table ID for the data table where all the candidate’s emails are listed.
      • links: A data table ID for the data table where all the candidate’s links are listed.
      • archived: True or false for whether the candidate is archived.
      • tags: A data table ID for the data table where all the candidate’s tags are listed.
      • sources: A data table ID for the data table where all the candidate’s sources are listed.
      • stageChanges: A data table ID for the data table where a history of all the candidate’s stage changes are listed. The table has the following columns: toStageId, toStageIndex, updatedAt, and userId.
      • origin: The candidate’s origin.
      • sourcedBy:
      • owner: The user ID for the owner of the candidate.
      • followers: A data table ID for the data table where all the candidate’s followers are listed.
      • applications: A data table ID for the data table where all the candidate’s applications are listed.
      • createdAt: A Unix timecode stamp for when the candidate was created.

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.

Need more help?

If you're signed in to Catalytic Community, you can ask other users a question. You'll be redirected to Community where you can add more info.