Resources · Make integration

journy.io Make integrationAutomate journy.io with Make.

Want the people who sign up in your other tools to show up in journy.io on their own? The journy.io Make integration gives you 4 action modules and no trigger. This guide is for growth and ops teams: connect the account, then build a first scenario that feeds it.

Try the journy.io integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the journy.io Make integration do for you?

It lets Make write into journy.io for you. A scenario (the automation you build in Make, a chain of bricks called modules) picks up data in another app, then uses one of the 4 journy.io modules to identify a person, tie them to a company account or log something they did. journy.io only receives data here: it never starts the scenario itself.

Every signup lands in journy.io. A form tool or your product database catches a new user, and Identify a User sends that person over, so nobody copies profiles by hand.

People sit under the right company. When a contact is attached to a client in your CRM, Associate a User with an Account makes the same link in journy.io, which keeps account-level views honest.

Key moments become events. A paid invoice in your billing tool or a booked demo can reach journy.io through Track an Event. For anything the three named modules do not cover, Make an API Call reaches the rest of the journy.io API with the same connection.

Be aware of one limit: Make itself flags the journy.io documentation as limited, with no field list and no official connection guide. Expect to open each module and read what it asks. If you are still weighing tools, the n8n vs Make comparison lays out the criteria, and the Make review covers the editor in depth. Stuck on a run? The Make troubleshooting guide walks through the usual errors.

Connect

How do you connect journy.io to Make?

  1. 01

    Open a journy.io module

    In your scenario, add any journy.io module, for example Identify a User, then click Create a connection. A connection is your journy.io account linked to Make once and reused by every journy.io module afterwards.

  2. 02

    Name it and authorize

    Give the connection a name you will recognize later, such as the team or project it serves. Then either approve Make on the journy.io page that opens or paste the key journy.io gives you, depending on what the window asks for.

  3. 03

    Save and check the fields

    Click Save. The module now shows its own fields, and Make can list what it reads from your account. If nothing appears, open the connection again and confirm you approved the right journy.io account.

First scenario

Your first scenario: journy.io in Make

GoalWhen someone signs up in another app, Make identifies them in journy.io and logs the signup as an event.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. The first module has to come from another app, since journy.io has no trigger: your form tool or your signup database.

  2. 02

    Pick the starting app

    Choose the module of that app that spots a new signup and connect its account. Each new person it finds becomes a bundle, meaning one item passed from one module to the next.

  3. 03

    Add Identify a User

    Click the + on the right, search journy.io and pick Identify a User. Create the connection, then map the email or ID coming from the first module into its fields.

  4. 04

    Log the signup with Track an Event

    Add Track an Event after it and map the same person, so journy.io records that this user just signed up. Give the event a name your team will recognize in reports.

  5. 05

    Test with Run once

    Click Run once and create a test signup. Open the bubble above each module to read the bundles it received; that is the quickest way to spot a field mapped in the wrong place.

  6. 06

    Schedule and switch on

    Set the clock on the first module, every 15 minutes by default, then switch the scenario on. Each module run on each bundle counts as one operation on your Make plan.

Modules

What the journy.io modules do

journy.io gives you 4 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

journy.io1

Associate a User with an Account

ActionIn the docs only

This one links a person to a company inside journy.io, so their activity counts for that account and not only for themselves. It is the module that turns a flat list of users into customers grouped by organization.

When to use it
right after a contact gets attached to a client in your CRM, or when a new teammate joins an existing customer.
Watch out
as a precaution, place Identify a User before it in the same scenario, so journy.io knows the person you tie to an account.
journy.io2

Identify a User

ActionIn the docs only

As its name suggests, it sends journy.io a person described by data another app hands you. You get a profile that other modules and your team can rely on, without typing anyone in by hand.

When to use it
as the first journy.io step of almost any scenario, typically when a signup form or product database reports someone new.
Watch out
Make publishes no field list for it, so open the module after connecting and map the identifier it asks for carefully.
journy.io3

Make an API Call

ActionIn the docs only

With this module you reach any endpoint of the journy.io API while keeping the connection you already made. It covers what the three named modules leave out, without a separate login.

When to use it
when the task you have in mind does not match identifying a user, linking an account or tracking an event.
Watch out
you write the request yourself, so keep the journy.io API reference open and test with Run once before switching anything on.
journy.io4

Track an Event

ActionIn the docs only

Use it to record that something happened, such as a signup, a payment or a booked call, so the moment appears in journy.io next to the person or account concerned.

When to use it
whenever an app outside journy.io knows about an action your team wants to see in the customer timeline, like an invoice marked as paid.
Watch out
pick one naming rule for events before you build several scenarios, or the same action will show up under different names.
Need help

Need help automating journy.io with Make?

A person reads every message.

FAQ

Questions about journy.io and Make

01Is the journy.io Make integration free?
Yes. journy.io is a standard app in Make, so its modules work on the Free plan. That plan has its own limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Every module run on one bundle counts as one operation against your monthly credits. Paid plans such as Core, Pro and Teams lift the active scenario cap and let you schedule every minute. This answer covers Make only; what journy.io charges on its side is a separate question.
02What do you need to connect journy.io to Make?
A journy.io account and a Make account. The Make documentation lists no extra prerequisite and no dedicated connection steps for journy.io, so the generic flow applies: add a journy.io module, click Create a connection, name it if you like, then authorize Make on the journy.io page or paste the key journy.io provides, and click Save. The same connection then serves all 4 modules, including Make an API Call. If you manage more than one journy.io account, create one connection for each and name them clearly.
03Can journy.io start a Make scenario in real time?
No. journy.io has no trigger in Make, neither scheduled nor instant, so it cannot start a scenario on its own. The scenario has to begin with another app: its trigger decides when things run. If that app offers an instant trigger, meaning it calls Make through a webhook as soon as something happens, your journy.io modules run right after. Otherwise the scenario follows its schedule, set on the first module and every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval allowed.
04What if a journy.io module you need is missing in Make?
Use Make an API Call. It is the fourth journy.io module, and it reaches any endpoint of the journy.io API with the connection you already set up, so you are not limited to identifying users, linking accounts and tracking events. Keep in mind that Make describes its own journy.io documentation as limited, with no field lists or troubleshooting notes. Plan to read the journy.io API reference for the exact request, and test each call with Run once before activating the scenario.
05Should you use Make or n8n for journy.io?
It depends on what you need to build. On the Make side, the facts are clear: 4 action modules, no trigger, a generic API module for the rest, and access from the Free plan. Many apps also have an n8n node, so check whether one exists for journy.io and which actions it offers before choosing. Compare the modules each tool gives you for your actual use case, and pick the one your team already knows how to maintain. Neither choice is better by default.
Same platform

Other docs you might need on this stack.

Browse all integrations