ATS integration apps allow you to configure and manage the flow of hiring data between ChartHop and your preferred application tracking system (ATS).

Before configuring an ATS integration app in ChartHop, you need to consider which type of data flow best serves your organization's needs. Depending on your needs, all ATS integration apps offer two types of data flows which offer distinct advantages.

An inbound job data flow brings open jobs from the ATS to ChartHop where the ATS is the source of truth. Inbound data flows support both on-demand syncs and scheduled daily syncs. In most cases, you can rely on daily syncs to pull updated hiring data from your ATS.

Data remains in and is updated within the ATS system. A daily sync pulls information from the ATS to ChartHop. You can also stream data ad-hoc through an on-demand Sync Jobs button that can be accessed within the ATS application configuration page in ChartHop.

When a hire is made in the ATS, ChartHop creates a pending new hire which starts an open job according to its assigned start date. Once the pending new hire’s information is also entered into the HRIS/payroll system, ChartHop will merge the payroll profile with the existing pending new hire using the pending new hire’s personal or work email as a unique identifier.

Inbound job data flows offer a few advantages over outbound job data flows which include:

• Recruiting teams only having to work out of the ATS.
• No changes are required to your standard hiring workflow.
• The process is often easier to start with and implement for first-time users.

Inbound job data flows are recommended if:

• You don't plan on using ChartHop as the source of truth for your hiring plan.
• You work with a team that is very comfortable with their current ATS workflow.
• You have specific data needs with your ATS that ChartHop can’t fulfill such as highly unique systems and data types.
• You do not plan to give recruiters access to ChartHop.

With an outbound job data flow, ChartHop is the source of truth and the database of record.

Hiring data is entered and updated in ChartHop, and is then sent from ChartHop to the ATS using event-based trigger flows which update the information in the ATS immediately.

In an Outbound job data flow, open job and req data flow outbound from hiring plans in ChartHop to the ATS. This helps recruiting teams using ChartHop for headcount planning to move data seamlessly from the approved headcount plan into their recruiting system. However, once a hire is made in the ATS, that new hire data flows inbound from the ATS into ChartHop.

When a hire is made in the ATS, ChartHop creates a pending new hire which starts an open job according to its assigned start date. Then, once the pending new hire’s information is also entered into the HRIS/payroll system, ChartHop will merge the payroll profile with the existing pending new hire using the pending new hire’s personal or work email as a unique identifier.

Outbound job data flows offer several advantages over inbound job data flows including:

• The immediate and real-time syncing of information.
• Allowing headcount planning and execution (for example, hiring against the headcount plan) to all take place within ChartHop.
• Allowing hiring managers (or recruiters, or even other stakeholders such as finance) to collaboratively propose and make changes to open jobs automatically without needing to access the ATS.

Outbound job data flows are recommended if:

• You utilize ChartHop for headcount planning and/or being the source of truth for the hiring plan.
• You have simple to standard ATS workflows where ChartHop can fulfill most of the data needs.
• You are looking for real-time visualization across both systems.
• You need more collaboration when managing new jobs.