Resources · Make integration

Peliqan Make integrationAutomate Peliqan with Make.

Can your Peliqan tables stay current without anyone typing into them? The Peliqan Make integration gives you 5 modules: 3 actions that write or call the API, and 2 searches that read databases and rows. This page is for data and ops teams, and it walks you from connection to a working first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Peliqan Make integration do?

The Peliqan Make integration links your Peliqan account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules. Each module is one brick of that chain. With Peliqan you get modules that edit a table cell or a whole row, list your databases and pull every row of a table.

A table that follows your other tools. Start the scenario from another app, for instance a new deal in your CRM, and let Update a Row write the new status into the matching Peliqan row. Nobody copies values by hand anymore.

A single figure kept correct. When only one value moves, such as a stock level or an approval flag, Update a Cell touches that one cell and leaves the rest of the row alone.

Rows sent where people read them. List Table Rows reads a table and hands each row to the next module, so you can post a summary to a chat tool or fill a spreadsheet for someone who never opens Peliqan. Pair it with List Databases when you first need to see what exists.

What Make will not do here: Peliqan has no trigger module, so nothing in Peliqan can start a scenario by itself. You start it from another app or from the Make schedule. For anything the four named modules skip, Make an API Call reaches the rest of the Peliqan API. New to the editor? The Make training covers the basics, Make pricing explains plans, and if you are also weighing n8n, read n8n vs Make.

Connect

How do you connect your Peliqan account to Make?

  1. 01

    Copy your API token in Peliqan

    In Peliqan, open Admin in the main menu, then Security settings, then API token. Copy the token shown on screen. You need an active Peliqan account to see this menu.

  2. 02

    Add a Peliqan module in Make

    In your scenario, add any Peliqan module and click Create a connection. The connection is your Peliqan account linked to Make once, then reused by every Peliqan module you add later.

  3. 03

    Paste the token and save

    Give it a label in Connection name if you like, something like the workspace name, then paste the token you copied and confirm. Make can now read and write your Peliqan data.

First scenario

Build your first scenario with Peliqan

GoalWhen a record changes in another app, Make updates the matching row in your Peliqan table.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Since Peliqan has no trigger, this first bubble belongs to the app where the change happens.

  2. 02

    Pick the starting app

    Search that app, choose its module and connect your account. Each item it passes along is a bundle: one record, one contact, one line, handed to the next module.

  3. 03

    Add Update a Row

    Click the + on the right, search Peliqan and pick Update a Row. Select your connection, then map values from the first module into the row you want to change.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can check that Peliqan got the right values before going live.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set Scheduling; a new scenario runs every 15 minutes by default. Then flip the scenario on and let it work.

Modules

What can the Peliqan modules do in Make?

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

Peliqan1

Make an API Call

Action

In Make“Performs an arbitrary authorised API call to get/manage data in Peliqan.”

This module sends a request of your choice to the Peliqan API through the connection you already set up, so there is no second login. It covers whatever the four named modules leave out.

When to use it
you need a Peliqan action that has no ready-made module and the API offers it.
Watch out
you write the request yourself, so keep the Peliqan API documentation open while you set it up.
Peliqan2

Update a Cell

Action

In Make“Updates one cell in a table.”

Changes exactly one cell in a Peliqan table and nothing else, which keeps the rest of the row safe from accidental overwrites. Think of a single status, amount or flag.

When to use it
only one value moves, such as an approval turning to yes after a manager signs off in another tool.
Watch out
when several columns change together, one Update a Row costs fewer operations than a string of cell updates.
Peliqan3

Update a Row

Action

In Make“Updates a row in a table.”

Updates a row of a Peliqan table in one step, so several values of a record that changed elsewhere follow together. It fits best when another app holds the reference version of that record.

When to use it
a customer, order or ticket was edited in another app and several of its values must follow.
Watch out
it edits an existing row; run a test with Run once and check that the scenario targets the row you expect.
Peliqan4

List Databases

Search

In Make“Lists all databases.”

Returns every database your Peliqan account can see, each one as a separate bundle. That gives you a quick inventory without leaving the scenario editor.

When to use it
you are building a scenario that must work across several databases, or you simply want to confirm which ones the connection reaches.
Watch out
each database becomes its own bundle, so every module placed after it runs once per database and uses operations accordingly.
Peliqan5

List Table Rows

Search

In Make“Gets all the rows from a table.”

Pulls all the rows of one Peliqan table and passes them on one by one, ready to be sent, filtered or copied into another tool. A search in Make can return zero, one or many items.

When to use it
a colleague needs the table in a spreadsheet or a chat message and will never log into Peliqan.
Watch out
a large table means many bundles, and each module after this one counts an operation for every row.
Need help

Need help automating Peliqan with Make?

A person reads every message.

FAQ

Peliqan and Make: common questions

01Is the Peliqan Make integration free?
Yes, on the Make side. Peliqan is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, a scheduled run no more often than every 15 minutes, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. You still need your own active Peliqan account, which Peliqan bills separately.
02What do you need to connect Peliqan to Make?
An active Peliqan account and its API token. In Peliqan, go to Admin, then Security settings, then API token, and copy the value. In Make, add a Peliqan module, click Create a connection, optionally name it, and paste the token. The same connection then serves all five Peliqan modules, including Make an API Call. If the Admin menu is missing, ask a workspace admin for the token. Nothing else is required on the Make side.
03Can a Peliqan scenario in Make run in real time?
Not from Peliqan itself. The app has no trigger module, so Peliqan cannot tell Make that something changed. You have two ways to start. Open the scenario with another app's trigger, and it reacts when that app reports an event, instantly if that trigger is an instant one. Or begin with a Peliqan search such as List Table Rows and let the Make schedule run it, every 15 minutes by default.
04What if the Peliqan module you need is missing in Make?
Use Make an API Call. It sends any request the Peliqan API supports, using your existing connection, so you are not limited to updating cells and rows or listing databases and tables. You write the request yourself, which means reading the Peliqan API documentation first. The Make documentation for this app is AI-generated from Peliqan's own docs, so double-check anything critical with Peliqan. Test each new call with Run once before switching the scenario on.
05Should you use Make or n8n for Peliqan?
It depends on the tool your team already runs. In Make, Peliqan comes with five modules: two to update data, two to list it, and a general API call for the rest. If that covers your need and your other scenarios live in Make, stay there. Many apps also have an n8n node, so check what exists on the n8n side against the same list before deciding. The n8n vs Make comparison on this site lays out the differences.