---
title: "Make.com App"
canonical: "https://help.journy.io/space/journy/3137568769/Make.com%20App"
format: markdown
---
> Macro (include)

# Topics

> Macro (toc)

# What’s Make.com?

[http://Make.com](http://Make.com)  is **a powerful automation platform designed to streamline workflows and integrate various applications seamlessly**. It allows users to create custom automations without needing extensive coding knowledge, making it accessible for businesses of all sizes. Automate repetitive tasks.

## How Make works?

The role of Make is to seamlessly connect your apps/services, so you can concentrate on new tasks rather than repeating the same tasks again and again. Get back to what matters the most.

Make works by linking together your favorite apps/services by their corresponding **modules **to create a scenario that will transfer and transform your data automatically for you. All you have to do is create a scenario that will watch for new data in one app/service, set-up the proceeding modules for the desired end result and Make will execute the task for you.

## A notion of Custom Apps in Make

Custom apps are helpful when Make doesn't yet have a native integration with the application you are using; and **allow you to build a connector that would function in exactly the same way as any other app on Make** (such as Gmail or HubSpot).

# Journy.io Custom App

journy.io Team has developed a custom App for Make to easу clients integrating their tools and platforms with journy.io.  Journy has a rich set of integrations but if you are are missing smth out and want to bring some additional data feel free to use our App to make it happen.

## How to find?

[journy.io](http://journy.io) is a publicly listed verified Make App. You can find more details about the App here:

[https://www.make.com/en/integrations/journy-io](https://www.make.com/en/integrations/journy-io)

To add [journy.io](http://journy.io) App to your Make scenarios click Add Module and type “journy“

![image-20250214-143910.png](media://dc2fe0b8-2e53-4c52-ad3a-a07ca1103199)

## Connection (Specify WriteKey)

You need to specify a **WriteKey **to log Identify, Group and Track calls to your specific [journy.io](http://journy.io) workspace. 

![image-20250217-141707.png](media://f86b86df-8c72-4a24-acad-7b08c0d06f58)

**WriteKey **could be found in your [journy.io SDK integration](https://releasemanagement.atlassian.net/wiki/spaces/journy/pages/2698117122/The+API+SDK+Connector#How-to-set-up-the-SDK-connector-to-your-specific-platform).

![image-20250217-141205.png](media://02ae6b45-822e-4518-a03b-9ee58c2a3f10)

Thus, specifying **WriteKey **once you can re-use the same connection across all your [journy.io](http://journy.io) App Modules (see below).

If you have multiple [journy.io](http://journy.io) workspaces and you need to define **WriteKey **on the fly you can always use [Advanced Settings](https://www.make.com/en/help/modules/module-settings#advanced-fields) to override **WriteKey** from connection.

![image-20250217-141545.png](media://361e2b74-5a5a-4ba8-ba05-ecfd0c13c1f8)

Exception is [https://releasemanagement.atlassian.net/wiki/spaces/journy/pages/edit-v2/3137568769#Make-an-API-Call](https://releasemanagement.atlassian.net/wiki/spaces/journy/pages/edit-v2/3137568769#Make-an-API-Call) where you need to specify **WriteKey **in JSON playload for your POST API call.

## Modules

![image-20250217-142006.png](media://d49d9e65-094a-4fe1-b0aa-88984338c3a7)

### 🤙 Identify a User

> 📝 *Implements *[https://releasemanagement.atlassian.net/wiki/spaces/journy/pages/2697658372](https://releasemanagement.atlassian.net/wiki/spaces/journy/pages/2697658372)

![image-20250217-142054.png](media://d17fed58-f5f2-443f-8ec9-5ef03f0ea51f)

**Required fields: **

- Either **User ID **or **Anonymous ID **should be specified

**Advanced settings: **

- **Write Key** for [journy.io SDK integration](https://releasemanagement.atlassian.net/wiki/spaces/journy/pages/2698117122/The+API+SDK+Connector#How-to-set-up-the-SDK-connector-to-your-specific-platform)

### 🤙 Associate a User with an Account

> 📝 *Implements *[https://releasemanagement.atlassian.net/wiki/spaces/journy/pages/2697134285](https://releasemanagement.atlassian.net/wiki/spaces/journy/pages/2697134285)

![image-20250217-142455.png](media://d2fd8cac-675d-4087-96f3-d277bf81938a)

**Required fields: **

- **Account ID **be specified
- Either **User ID **or **Anonymous ID **should be specified

> ⚠️ *To update journy Account copy Account ID to Anonymous ID*

**Advanced settings: **

- **Write Key** for [journy.io SDK integration](https://releasemanagement.atlassian.net/wiki/spaces/journy/pages/2698117122/The+API+SDK+Connector#How-to-set-up-the-SDK-connector-to-your-specific-platform)

### 🤙 Track an Event

> 📝 *Implements *[https://releasemanagement.atlassian.net/wiki/spaces/journy/pages/2697068976](https://releasemanagement.atlassian.net/wiki/spaces/journy/pages/2697068976)

![image-20250217-142208.png](media://d6d058b6-d391-426c-878c-b302c775be6b)

**Required fields: **

- **Event Name **be specified
- Either **User ID **or **Anonymous ID **should be specified

> ⚠️ *To send event for journy Account copy Account ID to Anonymous ID*

**Advanced settings: **

- **Write Key** for [journy.io SDK integration](https://releasemanagement.atlassian.net/wiki/spaces/journy/pages/2698117122/The+API+SDK+Connector#How-to-set-up-the-SDK-connector-to-your-specific-platform)

### 🤙 Make an API Call

> 📝 *Suits for any *[https://releasemanagement.atlassian.net/wiki/spaces/journy/pages/2697625618](https://releasemanagement.atlassian.net/wiki/spaces/journy/pages/2697625618)

![image-20250217-142605.png](media://3d8056f6-0c8a-4e2a-9e33-14bdfacd9bf4)

**URL**

| **Call** | **URL suffix** |
| --- | --- |
| Identify | */v1/i* |
| Group | */v1/g* |
| Track | */v1/t* |

> 📝 Check the latest version of API available to change *v1* to *the newest* if required.

**Method**: POST

**Headers**

| **Headers** |  |
| --- | --- |
| `Content-Type` | `application/json` |

**Body (JSON) Required fields: **

- **“type” **be specified (identify, group, track, etc.)
- Either **“userid“ **or “**anonymousid” **should be specified
- **“writekey”** for [journy.io SDK integration](https://releasemanagement.atlassian.net/wiki/spaces/journy/pages/2698117122/The+API+SDK+Connector#How-to-set-up-the-SDK-connector-to-your-specific-platform)

# Suggested use cases

The following use cases might be considered

- **Enrich Users/Accounts with additional properties**. You might create a webhook on changes in other tool/platform (check available Make Apps) or pull for changes to update Users (Identify Call), Accounts (Group Call) or connect User to Account (Group Call). Make sure you can get/construct proper IDs for Users and Accounts. e.g.
  - Last Ticket Status
  - Last Call Sentiment
  - Last Price Upgrade
  - etc.
- **Bring additional User/Account behaviour data**. You might create a webhook on changes in other tool/platform (check available Make Apps) or pull for changes to log additional behaviour (Track Call) for  Users and Accounts. e.g.
  - Support Tickets/Cases
  - Calls Summary/Sentiments
  - Payment Transactions (if applicable)
  - etc.

## Missing smth out?

There are tons of ideas how to improve the App, namely

- Implementing Search modules to find users/accounts
- Webhooks to act upon user/account created/changed or new behaviour logged
- etc.

Please reach out to the support team below for assistance with your unique inquiries.

> Macro (include)