Resources · Make integration

Idiligo Make integrationAutomate Idiligo with Make.

Can Make create Idiligo meetings for you without a line of code? The Idiligo Make integration gives you 7 action modules around meetings, participants and documents. This guide shows how to link your account, build a first scenario and pick the right module.

Try the Idiligo integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Idiligo Make integration do for you?

The Idiligo Make integration links your Idiligo account to Make, a no-code tool where you build a scenario (the automation itself, a chain of modules). Each module is one brick: here, all 7 are actions that create or fetch something in Idiligo when the scenario reaches them.

Meetings that set themselves up. When a request lands in your CRM or a form, Create a Meeting opens the meeting in Idiligo and Create a Participant for Meeting adds the person who asked, with the details mapped from the previous module.

A personal link for every guest. Generate Participant URL produces an address for one participant, which a mail or chat module sent next in the scenario can deliver. Connect a Participant covers the case where the person must be tied to an existing record.

Files where they belong. Add a Document pushes a file into Idiligo, and Get Documents reads back what is already there so another app can store or share it.

Know the limits before you start. Idiligo has no trigger in Make, so a scenario starts from another app or from the schedule. Make also warns that its documentation for this app is limited, so test each module with Run once before relying on it. If a module you need is missing, Make an API Call reaches the rest of the API with the same connection. Idiligo may also have a node in n8n; the n8n vs Make comparison lays out the two tools side by side. For the basics of the editor, the Make training is a good start, and the Make pricing page explains how operations are counted.

Connect

How do you connect Idiligo to Make?

  1. 01

    Add an Idiligo module

    In your scenario, click the + and search for Idiligo, then pick any of its modules. Make asks for a connection, which is your Idiligo account linked to Make once and reused by every Idiligo module. Click Create a connection.

  2. 02

    Name it and authorize

    Give the connection a name you will recognize later, such as the workspace it belongs to; this is optional. Then authorize Make on the Idiligo page that opens, or paste the key Idiligo gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. The connection now appears in the module's drop-down, and every other Idiligo module in your scenarios can pick it without asking you to sign in again.

First scenario

Build your first scenario with Idiligo

GoalWhen a new request arrives in another app, Make creates an Idiligo meeting and adds that person as a participant.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since Idiligo has no trigger, this first module comes from the app where requests arrive, such as your form or CRM.

  2. 02

    Add Create a Meeting

    Click the + on the right of that first module, search for Idiligo and choose Create a Meeting. Pick your connection, then fill the fields by mapping values from the first module instead of typing them.

  3. 03

    Add the participant

    Add Create a Participant for Meeting after it. Map the meeting it should join from the output of Create a Meeting, and the person's details from the first module, so each run handles one request.

  4. 04

    Test with Run once

    Click Run once and trigger one real request in the first app. Open the bubble above each module to read the bundles it received, one bundle being one item passed along, and check the meeting in Idiligo.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, or use its instant option if that app has one. Then switch the scenario on. Each module run counts as an operation on your plan.

Modules

What each Idiligo module does

Idiligo gives you 7 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Idiligo1

Add a Document

ActionIn the docs only

Add a Document sends a file into Idiligo, so the paperwork that arrives elsewhere ends up where your meetings live, without a manual upload.

When to use it
a signed file lands in cloud storage or an email attachment and belongs next to the related Idiligo record.
Watch out
Make lists no details for this module, so run it once and check in Idiligo where the file went.
Idiligo2

Connect a Participant

ActionIn the docs only

Going by its name, Connect a Participant links a person in Idiligo: reach for it when the participant already exists and needs linking, not creating again.

When to use it
a contact already known in your CRM should be attached to an Idiligo session instead of duplicated.
Watch out
the documentation does not say how it differs from Create a Participant for Meeting, so compare both with Run once.
Idiligo3

Create a Meeting

ActionIn the docs only

You get a new Idiligo meeting as soon as the scenario reaches this module, filled with the details you map from earlier steps, and it is usually the first Idiligo step of a flow.

When to use it
a booking form or a won deal should turn into a meeting with no copy and paste.
Watch out
every run creates a new meeting, so filter duplicate requests upstream before this module.
Idiligo4

Create a Participant for Meeting

ActionIn the docs only

This module adds a fresh participant to a given meeting, which saves you from entering each guest by hand once the meeting exists.

When to use it
right after Create a Meeting, mapping the new meeting and the name of the person who asked for it.
Watch out
one run adds one participant; for a list of guests, an iterator must split it into one bundle per person first.
Idiligo5

Generate Participant URL

ActionIn the docs only

With Generate Participant URL, each participant gets their own address, ready to drop into an email, a text message or a chat notification sent by the next module.

When to use it
after adding a participant, when the invitation should leave from your usual mail tool instead of Idiligo.
Watch out
by its name, the module produces the link without sending it; that takes another module placed after it.
Idiligo6

Get Documents

ActionIn the docs only

Get Documents reads the files already stored in Idiligo and hands them to the rest of your scenario, so another app can archive, share or log them.

When to use it
once a meeting ends, to copy its documents to shared storage for the team.
Watch out
the plural name suggests several documents can come back; read the bundles after Run once before mapping them into the next module.
Idiligo7

Make an API Call

ActionIn the docs only

Make an API Call covers whatever the six other modules leave out: it calls any endpoint of the Idiligo API while reusing the connection you already made.

When to use it
you need an Idiligo action that no listed module offers.
Watch out
you write the request yourself, and Make gives no Idiligo API reference, so ask Idiligo for it first.
Need help

Need help automating Idiligo with Make?

A person reads every message.

FAQ

Questions about Idiligo and Make

01Is the Idiligo Make integration free?
Yes, Idiligo is a standard app, so its modules work on the Free plan of Make. That plan has 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. Paid plans lower the interval to one minute, remove the cap on active scenarios and count usage in operations per month. What Idiligo itself costs is a separate question to check with Idiligo.
02What do you need to connect Idiligo to Make?
You need an Idiligo account and a Make account. The Make documentation lists no other prerequisite for this app. Add any Idiligo module, click Create a connection, optionally name it, then authorize Make on the Idiligo page or paste the key Idiligo gives you, and save. Since Make says its documentation for Idiligo is limited, follow what the connection window asks and test one module with Run once before building the full scenario.
03Does the Idiligo Make integration react in real time?
Not on its own, because Idiligo has no trigger module in Make: all 7 modules are actions. A scenario therefore starts somewhere else. You can open it with a trigger from another app, such as a form or a CRM, which may be instant if that app supports it. You can also start it on the schedule of Make, which runs every 15 minutes by default and at the interval you choose on a paid plan. The Idiligo modules then run in the order you placed them.
04What if the Idiligo module you need is missing?
Use Make an API Call. It is part of the Idiligo app in Make and lets a scenario reach any endpoint of the Idiligo API with the connection you already set up, so you are not limited to the six ready-made modules. You write the request yourself, so ask Idiligo for its API documentation, since Make does not provide it. Make also warns that its documentation for this app is limited, so testing each module with Run once is the safest way to confirm what it does before going live.
05Should you use Make or n8n for Idiligo?
It depends on the tool your team already builds in, since the choice is about the platform more than about Idiligo. In Make, Idiligo offers 7 action modules, including Make an API Call for anything not covered, and no trigger. The same app often has a node in n8n as well, so check what that node covers before deciding. Compare the modules you actually need on each side, then build a small test scenario in the tool that fits your habits.
Same platform

Other docs you might need on this stack.

Browse all integrations