Carerix integration

With the Carerix integration you connect your Intractive story directly to your Carerix environment. As soon as someone fills in a form in your story, their details are sent straight to Carerix. You can:

• Create a candidate in Carerix from any form in your story.
• Register a full application; the candidate plus a match on the vacancy they applied for.
• Create a match on an existing publication, so the applicant lands in the right pipeline.
• Let Carerix check for existing candidates instead of creating duplicates.
• Record AVG/GDPR consent automatically, straight from the opt-in in your form.

Everything is configured per story, so different campaigns can feed different vacancies, use different field mappings and carry their own settings.

Before you start

Make sure you have:

• An active Intractive account with a story you can edit.
• A Carerix user with permission to open the Identity Access menu (typically an administrator). If you don't have this, ask a Carerix administrator in your organisation.
• Access to the Carerix GraphQL API in your environment.
• At least one published vacancy in Carerix, if you want applicants to be linked to a publication automatically.

Step 1: Create a client in Carerix

Before Intractive can talk to Carerix, you create a client in Carerix that Intractive will use to identify itself. We also highly recommend to check out the documentation of Carerix:

1.1 Open the Identity Access menu

This is a copy of the documentation of Carerix, for more info check :

1. Log in to Carerix as a user with permission to access the Identity Access menu (typically an administrator).
2. In the left-hand menu, go to the Maintenance section and open Identity Access.
3. Select the Clients tab.

1.2 Create a new client

1. Click New.
2. Choose whether you want a public client or a confidential client. For a regular integration that posts jobs and processes applications — which is what Intractive does — a confidential client is the right choice.

1.3 Configure the confidential client

Fill in the following fields:

• Name: you need to provide a name for your client. You can typically choose the name of the service that is going to connect with the GraphQL through this client. It makes it transparent in the future to see to whom or what was given access with this client.
• Code: Code is a user-defined unique identifier. It can be used to query the client via the API. It also acts as a prefix for client’s resources, permissions and scopes if such client is a resource server. Format: Use the format urn:{vendor}/{unique name}.
• Default scopes: scopes define what an application is allowed to call. They are included in the token, and if a scope needed for a specific endpoint is missing from the token, the request is rejected with a 403. Every request takes the default scopes into account. For the Intractive integration add: urn:cx/cx5Wrapper:data:manage
• Optional Scopes: optional scopes appear in a token only if explicitly requested from identity server during token obtaining.
• Active YES/NO: indicates whether the client can be used (YES) or not (NO).
• Permissions: With permissions you can grant granular access (none, owner, office, all) for operations (create, read, update, delete) on entities. Not applicable to CR-prefixed GraphQL queries and mutations.

1.4 Find your token URL

1. Click OpenID Configuration. This opens a page of configuration values for your Carerix environment.
2. Click Pretty print ✅ in the top-left corner so the values are displayed readably.
3. Look for the token endpoint and copy that URL. This is the Token URL you'll paste into Intractive.

Step 2: Connect Carerix to Intractive

1. Log in to Intractive:
2. Go to your Story.
3. Open Integrations.
4. Click Carerix. You'll see three fields: Client ID, Client secret and Token URL.
5. Paste in the Client ID, Client secret and Token URL you copied from Carerix.
6. Click Test connection.

If the test succeeds, the Carerix integration opens up and you can start configuring what should happen. If you get an error message, please let us now. We are happy to help.

Step 3: Collect candidate details in your story

The integration sends data that your story has collected, so first you need a form and variables to hold the answers.

1. In your story, add a form so viewers can leave their details.
2. Add the fields you want to collect. In this example the form has two fields: name and email.
3. Click Logic to link each filled-in field to a variable.

Those variables can be used in two ways:

• Inside the story itself: you can show an answer back to the viewer later on. To insert a variable, use the format {{@variable}} in any text field. In this example we created two variables, name and email, so we can reuse them in later story blocks. Once the viewer has filled in the form, adding {{@name}} or {{@email}} to a text field will display the value they entered.
• Inside an integration: the value is passed on to a system like Carerix.

Step 4: Choose what should happen in Carerix

Once the connection is live, you decide what the integration does. Before that you need to set up the general settings of the integration.

4.1 General settings

In the general settings you can choose an integration name and set up the trigger conditions. Here you can find the variables you created in your Intractive story. In this example we have created 2 variables: name and email.
A trigger condition tells the integration when to fire. When one of the variables you tick is filled in, the action runs. This is what makes sure a candidate is sent to Carerix once someone has actually completed the form.

• Select which variables you would like to use in the integration. You can do this by selecting them and a checkmark will appear next to the variable.

You'll see the variables your story collects, and three actions you can start from them:

• Apply (candidate + match): creates the candidate and immediately links them to the vacancy they applied for. This is the full application flow and the option most customers use.
• Create candidate: creates a candidate profile only, without linking them to a vacancy.
• Create match: creates a match, linking a candidate to a publication

4.2 Action: Apply (candidate + match)

This action creates the candidate and the match in one go. In the mapping you connect each story variable to the matching Carerix field. Whatever you ask for in your story can be sent through to Carerix, and you can add data in Carerix afterwards to complete the candidate profile.
The available fields are:

• Publication ID
• Match Source
• First Name
• Last Name
• Email Address
• Phone Number
• Mobile Number
• City
• Street
• Zip Code
• Country
• Birth Date
• Gender
• Initials
• Prefix
• Candidate Source
• Custom field name…

Beyond this list you can add custom fields, so anything specific to your Carerix setup can be filled from the story as well.

In this case we use our publication ID or Job ID, First name and email address. After someone fills out a form in the intractive story, this will trigger the apply step in the integration. This means a candidate profile is created and directly linked to the job.

The publication ID can be found in Carerix - Jobs - number. Every job has a number so the integration knows where to send the created candidate. In our case the number is 531.

Two options are worth setting deliberately:

• Deduplicate: When this is enabled, Carerix first checks whether the person submitting already exists as a candidate before creating a new one. If a match is found, the existing candidate is updated with the new information instead of a second record being created. This is useful when the same person goes through multiple stories, or comes back later to apply again — their history stays together on one candidate profile rather than being spread across duplicates.

When it's disabled, every submission creates a new candidate in Carerix, even if that person is already in the system.

• Record consent (AVG/GDPR): when enabled, the candidate's consent is recorded in Carerix from the form's opt-in. The approval date is taken from the moment of consent.

4.3 Action: Create candidate

Use this when you want the candidate in your database but not linked to a specific vacancy, for example an open application or a talent pool story.
Map your story variables to the Carerix candidate fields in the same way as above.
Note: in Carerix the name is stored as first name and last name. If your story only asks for "name", people will often type their full name into that one field, and it will all land in one Carerix field. It's worth deciding upfront whether to create two separate variables and map them separately.

4.4 Action: Create match

This action creates the match directly in Carerix. Linking a candidate to a publication so they appear in the right pipeline for that vacancy.

Step 5: Test your integration

You can check straight away whether the connection is working.

1. After you have saved the integration, refresh your Intractive platform page. This is easy to forget and is the most common reason a test seems to fail.
2. Publish your story and open the link or refresh the story page if the story was already published.
3. Fill in the form as a candidate would and submit it.
4. In Intractive, click Integration activity. Here you can see which calls were made and what was sent. A call that arrived correctly gets the label Delivered. A call that failed gets the label Failed. You can click on it to see what went wrong and where the problem is.
5. Open Carerix and check that the candidate is added to the system and, if you used Apply or Create match, that they are linked to the right vacancy.

Troubleshooting

Updated on: 23/09/2026