The Integration Center is used to quickly and easily create custom integrations between Paradox and other applications.

Configuration

The Integration Center can be enabled from the Integrations section of Client Setup. It will be enabled for you by a Paradox Admin. Click here to learn more about these settings.

Navigation

Navigate to the Integration Center by clicking the All Apps button in the top left corner of the header and then Integrations in its drop-down menu.

Integration Center details

The Integration Center has several functions that can be taken from their associated sections, which are listed in the left panel. From this panel, select the desired section to view and complete your tasks. These sections include the following.

• Requests – This is where all of your requests are made and stored. These include:
  • Outbound – These type of requests allow you to take information from Paradox and push it out to a third party system's endpoint. 
  • Inbound – These type of requests are where a custom inbound endpoints are created for clients or vendors. Essentially, this allows Paradox to receive information from a vendor, transform it into a standard payload for our public API, and then call upon that API to take the necessary action(s).
  • Authentication – These type of requests call into a token endpoint and take action on it.
  • Productized integrations – This was built for SAP SuccessFactors, Workday, and UKG, and calls into the provider in order to install all of the integrations needed for Dynamic Chat-to-Apply.
  • Dynamic Component – This allows you to attach an integration to a dynamic list select on a form so that the system can call out to a third party system to return a dynamic list. These requests can be made consistently to pull information regularly via an index.
• Audit Logs – This list stores all of the audit logs associated with the different types of requests.d
• Global Values – This allows you to store data for a single source that then reflects the value wherever it is used in the system. Oftentimes, we may have a single URL that is referenced in the Integration Center that is used throughout the system for an integration. Updating in the Integration Center allows that value to be updated everywhere it lives.
• Mapped Values – This allows you to map values in our system to an integration's values so that the correct values are placed in an outbound system while also making the experience more user friendly on our end (e.g., instead of showing pass / fail values to a candidate, which is the integration's values, we show the candidate true / false).
• Authentications – This allows you to store a token, or data stored for authentication, as an object.
• Certificates – This is where you store client certificates, such as a x.509 or PGP encryption certificate.
• Indexes – These are used to store responses from a Dynamic Component request and are time-based.
• Connected Apps – This is where our productized integrations credentials are stored.
• Integration Settings – This is where feature flags for our backend tooling are stored. This will not be available to System Implementors initially.