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.
  • 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 a name for each table (which will contain the fetched data) and the type of sync.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix 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 determine when to execute a 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:
  • id - Unique identifier for the job
  • name - Name of the job
  • status - Current status of the job (e.g., active, archived)
  • area - Business area of the job
  • userId - Identifier of the user responsible for the job
  • recruiterId - Identifier of the recruiter assigned to the job
  • managerId - Identifier of the hiring manager
  • createdAt - When the job was created
  • updatedAt - When the job was last updated
Stream containing full job details for each job from the Jobs stream.Key Fields:
  • id - Unique identifier for the job
  • name - Name of the job
  • status - Current status of the job
  • seniority - Seniority level associated with the job
  • salaryMin - Minimum salary for the position
  • salaryTarget - Target salary for the position
  • salaryMax - Maximum salary for the position
  • talentsCount - Total number of talents associated with the job
  • customFields - Custom fields configured for the job
  • stages - Hiring stages configured for the job
  • statusHistory - Historical status changes of the job
  • postingPage - Public posting page settings and metadata
Stream containing candidates (talents) associated with each job.Key Fields:
  • id - Unique identifier for the job-talent relationship
  • talentId - ID of the talent
  • userId - ID of the user responsible for the candidate in the process
  • status - Current status of the talent in the hiring process
  • stage - Detailed information about the current stage of the talent
  • source - The source from where the talent was acquired
  • targetSalary - Candidate salary expectations
  • talent - Candidate profile information (email, phone, location, LinkedIn, and attributes)
  • createdAt - When the talent was associated with the job
  • updatedAt - When the job-talent relationship was last updated
Stream containing evaluation scorecards for each job-talent relationship.Key Fields:
  • jobTalentId - ID of the associated job-talent relationship
  • userId - ID of the user who submitted the scorecard
  • userName - Name of the user who submitted the scorecard
  • evaluationsFeedbacks - Interview feedback entries with comments and proceed recommendations
  • skillComments - Qualitative comments grouped by skill
  • skillsScore - Skill-level score breakdowns for each interview step
Stream containing metadata definitions for custom fields in the JOB_TALENTS entity.Key Fields:
  • id - Unique identifier of the custom field
  • name - Name of the custom field
  • type - Field type (e.g., text, select)
  • entity - Entity where the custom field applies (JOB_TALENTS)
  • required - Whether the field is required
  • options - Available options for option-based fields
  • showIn - Contexts where the field is displayed
  • requiredIn - Contexts where the field becomes mandatory
Stream containing job position records linked to each job, including approval and hiring dates.Key Fields:
  • id - Unique identifier of the position
  • jobId - Identifier of the associated job
  • requisitionId - Identifier of the requisition linked to the position
  • reason - Reason associated with creating the position
  • approvedAt - Timestamp when the position was approved
  • hiredAt - Timestamp when the position was filled
  • createdAt - Timestamp when the position was created
  • updatedAt - Timestamp when the position was last updated
Stream containing InHire user records (team members and recruiters).Key Fields:
  • id - Unique identifier of the user
  • name - Name of the user
  • email - Email of the user
  • tenantId - Identifier of the tenant
  • roleId - Identifier of the role
  • roleName - Name of the role
  • position - Position/job title of the user
  • teams - Teams associated with the user
  • active - Whether the user is active
  • createdAt - Timestamp when the user was created
  • updatedAt - Timestamp when the user was last updated

​
Skills for agents

Download Inhire skills file

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