> ## Documentation Index
> Fetch the complete documentation index at: https://docs.inploi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Application Workflow Sync

> A custom, inploi-managed integration that pulls each job's application workflow from your ATS and renders it on your inploi-hosted careers site.

Most ATS integrations expose a single application form per job. **Application Workflow Sync** is a custom integration that retrieves the full **application workflow** your ATS defines for each job — its steps, fields, and question types — and recreates it inside the application on your inploi-hosted careers site.

This is not a self-serve feature. It is a **custom, inploi-managed integration** built per ATS, because every ATS models and exposes its workflows differently. inploi designs, builds, and maintains the integration on your behalf.

Application Workflow Sync is **ATS → inploi**. Your ATS remains the system of record for what a candidate is asked; inploi mirrors that workflow so the careers-site application matches it.

## What it does

* **Retrieves** the application workflow your ATS defines for each job, rather than a single fixed form.
* **Parses** the workflow into a structure inploi can render — steps, fields, and supported question types.
* **Presents** the matching workflow inside the application on your inploi-hosted careers site, job by job.
* **Validates** candidate answers against the workflow so submissions are accepted when they reach your ATS via [Submitting Applications](/integrations/ats/application-submissions).

## How it works

<Steps>
  <Step title="Your ATS exposes workflows via API">
    As a prerequisite, your ATS must make each job's application workflow available through its API, so inploi can read it programmatically.
  </Step>

  <Step title="inploi builds a custom integration">
    inploi builds and maintains an integration against your ATS that retrieves the workflow for each job.
  </Step>

  <Step title="The workflow is parsed and mapped">
    inploi parses the workflow data from your ATS and maps it onto inploi's supported field and question types, so it renders correctly on the careers site.
  </Step>

  <Step title="Candidates complete the matching workflow">
    The application on your inploi-hosted careers site reflects the ATS workflow for that job. Answers are validated as the candidate progresses.
  </Step>

  <Step title="The application is submitted to your ATS">
    On completion, the application is posted back through [Submitting Applications](/integrations/ats/application-submissions), already shaped to match what your ATS expects.
  </Step>
</Steps>

## Supported question types

inploi maps each question in your ATS workflow onto a supported field type. The types inploi can render and validate include:

| Type                          | Used for                                                               |
| ----------------------------- | ---------------------------------------------------------------------- |
| **Text**                      | Short or long free text, including email, phone, date, and URL formats |
| **Number**                    | Numeric answers, with optional minimum and maximum                     |
| **Yes / No**                  | Simple boolean questions                                               |
| **Single or multiple choice** | Select one or several options, with optional limits on how many        |
| **File upload**               | CVs and other documents, restricted to allowed file types              |
| **Address**                   | Structured address capture                                             |

Where your ATS uses a question type inploi does not yet support, inploi works with you on how it should be handled during the integration build.

## Prerequisites

| Requirement                       | Why it matters                                                                                                                                                   |
| --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **ATS exposes workflows via API** | inploi can only mirror a workflow it can read. If your ATS does not make workflows available programmatically, this integration cannot be built.                 |
| **Custom integration build**      | Each ATS is different, so inploi builds and maintains a bespoke integration rather than a generic one.                                                           |
| **Compatible question types**     | The workflow needs to use [question types inploi supports](#supported-question-types), or types inploi can map onto them, so it renders and validates correctly. |

## Why it is more involved

Unlike a standard application form, a synced workflow is generated from your ATS's own configuration. That means inploi has to interpret the ATS's question types and validation rules and translate them into something that both renders correctly for candidates and passes validation when the application is submitted back to your ATS. Because this parsing and mapping is ATS-specific, the integration is scoped and built per customer.

## What to expect

* The application a candidate sees should reflect the workflow defined for that job in your ATS.
* Submissions are shaped to match your ATS's expectations, so they are accepted by [Submitting Applications](/integrations/ats/application-submissions).
* If you change a job's workflow or introduce new question types in your ATS, tell your inploi contact — the integration may need to be updated so workflows continue to render and validate correctly.

<Snippet file="ats-managed-integration.mdx" />

## Getting this configured

Application Workflow Sync is set up by inploi as a custom integration. To explore whether your ATS can support it and what would be involved, **speak to your Customer Success Manager**.

<Snippet file="contact-support.mdx" />