All Collections
Integrations in Journeys
Integrations in Journeys
Kristín Helga Magnúsdóttir avatar
Written by Kristín Helga Magnúsdóttir
Updated over a week ago

In Journeys, you can set up an integration with most systems yourself - if the other system has a REST API (web service) to integrate with.

After you've set up an integration, you can use these integrations as actions in your Journeys. For example to create new employees in systems, grant or remove their accesses, create tasks in task management systems, send documents to e-signing, send messages to communication platforms, update internal systems etc. You can see an example here:

You can set up your own integration in the integration builder:

Just start with adding a logo for the integration, name and some description:


You want to start with authenticating for the service, here:

You can choose from different authentication types based on what the system you're integrating with requires:

Choose the authentication type based on the credentials you get from the service you're integrating with.

For example if the other service's credentials are username and password, it's probably "Basic" authentication.

If the other service just gives you an "Access token" it's probably "Authorization header" authentication.

If the other service gives you "Client ID" And "Client Secret" then it's probably a "Bearer Token" authentication.

Add endpoints

The next thing you want to do is to add an endpoint, based on what action you want to do.

In the other systems API you should be able find the function you want to add, for example "Create employee" or "Send message" or "Update access" etc. Under that function you should see an URL and an example request.

Insert that into the endpoint:

Now you should see the integration. Make sure to check that the "Type" is correct and update it if it's not. Now you're able to test it with some test values:

It should give you a success response, similar to this:

These response values are now listed in the "Response values" list below. You can delete the responses that you won't need and keep them you want to use. For example you might want to know the employee ID in the system if you're creating a new user (in case you want to update that user later in the journey). Or you might want to use response as a variable in other actions, for example if you're making a request to ChatGPT, you want to use the answer in another action in the journey you are building.

Now you're ready to use this integration in Journeys 🎉

P.s. you might want to add a List to select the variable from, you can read more about lists here.

Did this answer your question?