Resources · Make integration

Pigment Make integrationAutomate Pigment with Make.

Tired of uploading the same CSV into Pigment by hand? The Pigment Make integration gives you 3 action modules: one imports CSV data, one exports data as a CSV, one calls the Pigment API. This page shows finance and ops teams how to connect Pigment and build a first scenario.

Try the Pigment integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Pigment Make integration do for you?

The Pigment Make integration links your Pigment workspace to Make, a visual tool where you build a scenario (the automation itself, a chain of bricks) without writing code. Each brick is a module: here, three actions that push CSV data into Pigment, pull data out of it as a CSV, or call any endpoint of its API.

Feed your plan from the tools that hold the numbers. A sales tool, a form or a spreadsheet produces the rows; Import Data sends them to Pigment as CSV data. Your planners stop rebuilding the same upload, and the model gets its inputs from a scenario instead of a person.

Send Pigment results where people read them. Export Data takes data out of Pigment as a CSV, so the next module of the scenario can store the file, attach it to a message or hand it to another app. Useful when leadership wants the forecast without opening Pigment.

Reach what the two modules do not cover. Make an API Call reuses your Pigment connection to call any endpoint of the Pigment API. It asks you to read the Pigment API reference first, which is the price of that freedom.

Be aware that Make itself warns its Pigment documentation is limited, because little public information about the app exists. Test each module with real data before you rely on it. The Make review helps you judge the tool as a whole, and n8n vs Make is worth a look if Pigment also has an n8n node in your stack. For a hand with the setup, see Make training.

Connect

How do you connect Pigment to Make?

  1. 01

    Add a Pigment module

    In your scenario, click the +, search for Pigment and pick any of its modules, for example Import Data. The module opens with an empty connection field and a Create a connection button next to it.

  2. 02

    Create the connection

    Click Create a connection. A connection is your Pigment account linked to Make once, then reused by every Pigment module. You can give it a name, which helps when a workspace holds several accounts.

  3. 03

    Authorize and save

    Follow what Pigment asks for: either an authorization page where you approve Make, or a key that Pigment gives you and that you paste into the field. Then click Save, and the module can read your Pigment data.

First scenario

Your first scenario with Pigment

GoalWhen new rows appear in another app, Make imports them into Pigment as CSV data.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pigment has no trigger, so the first module comes from the app that holds your source rows.

  2. 02

    Pick the source module

    Search the source app by name, choose the module that returns your rows and link its account with Create a connection. Each row it returns is a bundle, one item passed to the next module.

  3. 03

    Add Import Data

    Click the + on the right of the first module, search Pigment and choose Import Data. Create the Pigment connection, fill the fields and map the values coming from the source module.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time and shows the bundles each module received, so you can open Pigment and check that the data landed where you expected.

  5. 05

    Schedule and switch on

    Set the schedule on the first module with the clock icon: a new scenario runs every 15 minutes by default. Adjust it if needed, then switch the scenario on so it keeps running without you.

Modules

What Pigment can do in Make

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

Pigment1

Export Data

Action

In Make“Exports Data as a CSV.”

Export Data gives you Pigment data as a CSV inside the scenario, ready for the modules that follow: store it, send it, or hand it to another tool that reads CSV files.

When to use it
a manager wants the latest Pigment figures in a shared folder or a message, without logging into Pigment.
Watch out
Make documents this module briefly, so run it once and read the bundle it returns before you pick the next module.
Pigment2

Import Data

Action

In Make“Imports CSV Data.”

Import Data loads CSV data into Pigment, so rows coming from a sales tool, a form or a spreadsheet reach your model without a manual upload.

When to use it
another app keeps the actuals your planners need, and you want them in Pigment every time the scenario runs.
Watch out
Make documents this module briefly, so test it with Run once on a small sample before switching the scenario on.
Pigment3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets you reach any endpoint of the Pigment API with the connection you already created, which covers every need the two other modules leave open.

When to use it
you need a Pigment operation that neither Import Data nor Export Data offers.
Watch out
you write the request yourself, so keep the Pigment API reference open and read the response bundle after each test.
Need help

Need help automating Pigment with Make?

A person reads every message.

FAQ

Pigment and Make: common questions

01Is the Pigment Make integration free?
Yes, on the Make side. Pigment is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs no more often than every 15 minutes, stops each run after 5 minutes, handles files up to 5 MB and includes 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and allow unlimited active scenarios. Make counts usage in operations, one execution of one module on one bundle. You still need your own Pigment account.
02What do you need to connect Pigment to Make?
A Pigment account and a Make account. Make's documentation lists no special prerequisite. You add a Pigment module, click Create a connection, optionally name it, then either approve Make on the Pigment authorization page or paste the key Pigment provides, and save. That single connection then serves Import Data, Export Data and Make an API Call alike, so you set it up only once per account and every module you add later picks it up.
03Does Pigment trigger a Make scenario in real time?
No, because Pigment has no trigger module in Make. A scenario that uses Pigment starts another way: on a schedule set on the first module, every 15 minutes by default on a new scenario, or from a trigger of another app placed before the Pigment modules. If that other app offers an instant trigger, it calls Make through a webhook as soon as something happens, and the Pigment module runs right after it.
04What if the Pigment module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Pigment API with the connection you already have, so you are not limited to importing and exporting CSV data. Keep in mind that Make says its Pigment documentation is limited, because little public information exists about the app. Plan to read the Pigment API reference yourself and test each request with Run once, reading the response bundle, before you rely on it.
05Should you use Make or n8n for Pigment?
It depends on the tool your team already works in. In Make, Pigment comes with 3 modules, Import Data, Export Data and Make an API Call, plus a visual editor and a guided connection. The same app often has a node in n8n as well. Compare what each side offers for Pigment specifically, then choose the platform where the rest of your scenarios already live, so the whole team maintains one kind of automation.
Same platform

Other docs you might need on this stack.

Browse all integrations