Resources · Make integration

EasyCSV Make integrationAutomate EasyCSV with Make.

Can Make feed EasyCSV and react to its imports without a line of code? The EasyCSV Make integration gives you 2 modules: one trigger and one action. This guide shows what each does, how to link your account and how to build a first working scenario.

Try the EasyCSV integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the EasyCSV Make integration do for you?

The EasyCSV Make integration links your EasyCSV account to Make, a tool where you chain apps together without code. A scenario is the automation you build there: a chain of modules, each one a brick of one app. EasyCSV brings two of them, one that notices new data imports and one that adds data.

Data that lands in EasyCSV by itself. When another app collects records, such as a signup form or an order tool, the Add Data module sends each record to EasyCSV. Nobody copies rows by hand anymore.

A reaction every time an import arrives. Watch New Data Import opens a scenario when Make's next scheduled check finds fresh data in EasyCSV, so the next app in your flow hears about it: a message to a teammate, a line in a report.

One place for scattered sources. Several scenarios, each starting from a different app, can end on Add Data and fill the same EasyCSV account.

Keep expectations simple: the documentation lists no search, no update and no delete module, and no universal API call module for this app. It also warns that its own text may contain mistakes, so check details with EasyCSV. If you weigh other tools, the n8n vs Make comparison lays out the differences. To learn the editor properly, see Make training, and when a run fails, Make troubleshooting is the place to start.

Connect

How do you connect EasyCSV to Make?

  1. 01

    Copy your API key from EasyCSV

    In EasyCSV, click your username in the top bar, open Business Info and copy the API key shown on screen. You need an active EasyCSV account for this key to exist.

  2. 02

    Open the connection window in Make

    Add any EasyCSV module to your scenario and click Create a connection. A connection is your EasyCSV account linked to Make once, then reused by both modules. The Connection name field is optional.

  3. 03

    Paste the credentials and save

    Paste what you copied from EasyCSV, or follow the instructions Make shows on screen, then confirm. Once the connection works, Make can read your EasyCSV data when you fill the module fields.

First scenario

Build your first scenario with EasyCSV

GoalWhen a new record appears in another app, Make adds it to EasyCSV.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Pick the trigger of the app where your data starts, a form tool for instance.

  2. 02

    Add the EasyCSV action

    Click the + on the right of that first module, search for EasyCSV and choose Add Data. Select your connection or create it with Create a connection.

  3. 03

    Map the incoming data

    Fill the fields of Add Data by mapping values from the first module. Each bundle, one item passing from module to module, becomes one entry sent to EasyCSV.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubbles above each module to read the bundles they received and confirm the data reached EasyCSV.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. Each module run on one bundle is an operation, the unit Make counts on your plan.

Triggers

What starts an EasyCSV scenario

1 module starts a scenario when something happens in EasyCSV. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by EasyCSV as soon as it happens.

EasyCSV1Watch New Data Import

Watch New Data Import

triggerIn the docs only

This trigger opens your scenario with each new data import it finds in EasyCSV, so every import can reach the rest of your tools without you checking the app.

How it fires
going by its name, since the directory entry was unavailable, it behaves as a scheduled trigger: Make checks the app on the scenario's schedule, every 15 minutes by default, 1 minute at the lowest on paid plans.
When to use it
a teammate or a client imports a file into EasyCSV and someone else needs to know, or the data must go on to a report or a CRM.
Watch out
do not end the same scenario on Add Data, or the data you add could come back in as a new import.
Modules

What the EasyCSV action does

EasyCSV gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

EasyCSV1

Add Data

ActionIn the docs only

Records collected somewhere else end up in your EasyCSV account with this action, one entry for each bundle it receives, with no manual copy and paste along the way.

When to use it
a form, a shop or a spreadsheet produces new rows and you want EasyCSV to hold them as they arrive.
Watch out
the documentation gives no field list or limit for this module, so check the result with Run once before you switch the scenario on.
Need help

Need help automating EasyCSV with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the EasyCSV Make integration free?
Yes, on the Make side. EasyCSV is a standard app, available from the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between 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 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module per bundle. EasyCSV itself needs an active account, and its own pricing page covers that subscription.
02What do you need to connect EasyCSV to Make?
An active EasyCSV account and its API key. In EasyCSV, click your username in the top navigation bar, choose Business Info and copy the key. In Make, add an EasyCSV module, click Create a connection, give it a name if you like, and paste the credentials. The documentation also mentions a webhook URL under Sheets, then Import Sheet Details, so keep EasyCSV open in another tab while you set things up.
03Does the EasyCSV trigger in Make react in real time?
No, as far as the available information goes. Watch New Data Import is treated as a scheduled trigger, a type inferred from its name because the directory entry was missing. Make checks EasyCSV on the scenario's schedule: every 15 minutes by default, never below 15 minutes on the Free plan, and down to 1 minute on paid plans. A new import therefore reaches your scenario at the next check, not the moment it happens.
04What if the EasyCSV module you need is missing in Make?
It depends on the task. EasyCSV has only two modules in Make, Watch New Data Import and Add Data, and no Make an API Call module to reach other parts of its API. For anything else, such as reading or removing existing data, look at whether another app in your flow covers the step, or ask the team for help designing a workaround. The documentation lists no other limit, and it warns that its own text may contain mistakes.
05Make or n8n for EasyCSV?
It depends on the tool your team already uses. On Make, EasyCSV offers one trigger and one action, with a guided connection and a visual editor where each module is a bubble. The same app often has an n8n node too, so check what that node covers before choosing. Pick the platform where your other scenarios already run, since keeping every automation in one place makes them easier to follow and to fix.
Same platform

Other docs you might need on this stack.

Browse all integrations