Skip to main content
Inhire is a recruitment and talent acquisition platform that helps businesses find, attract, and hire qualified candidates. It provides tools for job posting, candidate screening, interview management, and recruitment analytics to streamline the hiring process.

​
Configuring Inhire as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Inhire option from the list of connectors. Click Next and you’ll be prompted to add your access.

​
1. Add account access

You’ll need your Inhire account credentials for this connection. The following configurations are available:
  • Email: The email associated with your Inhire account.
  • Password: The password associated with your Inhire account. This value is stored securely and is never displayed after saving.
  • Tenant ID: The ID of the subdomain used in your Inhire URL. For example, if your URL is https://my_app.inhire.app, your tenant ID is my_app.
  • Filter Job Talent Status: (Optional) A list of job talent statuses to filter for. When this is set, the JobTalentScorecard stream will only be extracted for talents matching these statuses. This can significantly speed up extraction by skipping irrelevant scorecards (e.g., for rejected or hired candidates).
Please ensure you’re using a user account with sufficient privileges to access the account data.
Once you’re done, click Next.

​
2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

​
3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
  • Layer: Choose between the existing layers on your catalog. This is where you will find your new extracted tables once the extraction runs successfully.
  • Folder: A folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: We suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
  • Sync Type: You can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: Every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched.
    • Full table: Every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.
Once you are done configuring, click Next.

​
4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:
  • Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
  • Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
Once you are ready, click Next to finalize the setup.

​
5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

​
Streams and Fields

Below you’ll find all available data streams from Inhire and their corresponding fields:
Stream containing the lean job listing used as the parent stream for job-related child streams.Key Fields:
Stream containing full job details for each job from the Jobs stream.Key Fields:
Stream containing candidates (talents) associated with each job.Key Fields:
Stream containing evaluation scorecards for each job-talent relationship.Key Fields:
Stream containing metadata definitions for custom fields in the JOB_TALENTS entity.Key Fields:
Stream containing job position records linked to each job, including approval and hiring dates.Key Fields:
Stream containing Inhire user records (team members and recruiters).Key Fields:

​
Implementation Notes

​
Pagination & Extraction

The connector utilizes dynamic, cursor-based pagination driven directly by the API response envelope. This ensures robust and reliable extraction of large datasets (such as high volumes of Job Talents), effectively preventing missed records or broken syncs that can occur with standard page-size limits.

​
Skills for agents

Download Inhire skills file

Inhire connector documentation as plain markdown, for use in AI agent contexts.