Resources · Make integration

Anaplan Make integrationAutomate Anaplan with Make.

Tired of loading files into Anaplan by hand? The Anaplan Make integration gives you 14 modules, 11 actions and 3 searches, to feed models, run imports and pull data back out. This guide walks planning and ops teams through the connection and a first scenario.

Enterprise app This app is reserved to Make's Enterprise plan.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Anaplan Make integration do for you?

The Anaplan Make integration links your Anaplan account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick such as an action or a search. With it, files, imports, processes and cell values in your models move without anyone clicking through Anaplan.

Keep models fed with fresh data. When a sales export lands in another tool, Upload and Process a File sends it to the right model file and Run an Import loads it. For a single figure, such as a deal amount signed in the CRM, Write Cell Data sets the value directly in the grid.

Get the numbers out for reporting. Initiate a Read Request prepares an export, Download a Read Request hands it over as a CSV file, and Delete a Read Request Data clears the space afterwards. An FP&A analyst gets the file in a shared drive without opening the model.

Run and watch processes. Run a Process starts a process and waits for completion, then List Process Tasks shows the status of each task, ready to log or to alert someone.

Know the limits before you start: the Anaplan app is reserved for the Make Enterprise plan, it has no trigger, so another app or a schedule starts the scenario, and the simple upload is meant for files under 50 MB. The same app may also exist as an n8n node; the n8n vs Make page compares the two tools, Make pricing explains the plans, and Make training helps you get fluent in the editor.

Connect

How do you connect Anaplan to Make?

  1. 01

    Add an Anaplan module

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

  2. 02

    Enter your Anaplan login

    Give the connection a name in Connection name if you like, which helps when several accounts coexist. Then type the credentials of your Anaplan account in the Username and Password fields.

  3. 03

    Save and confirm access

    Click Save. If Anaplan asks you to authenticate, do it and confirm access. The module then lists what it can read from your account, so you pick models and files instead of typing them.

First scenario

Your first scenario with Anaplan

GoalWhen a new export file shows up in another tool, Make uploads it to Anaplan and runs the matching import.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Anaplan has no trigger, so the first module belongs to the tool where your export files arrive.

  2. 02

    Add the upload

    Click the + on the right of that first module, search Anaplan and pick Upload and Process a File. Create the connection with your Anaplan login when Make asks for it.

  3. 03

    Map the file

    Choose the target model file from the list Make reads in your account, then map the file coming from the first module. Keep to files under 50 MB with this module.

  4. 04

    Chain the import

    Click the + again, add Run an Import and select the import task that loads this file. Make waits for Anaplan to confirm the import completed.

  5. 05

    Test with Run once

    Click Run once and let a test file reach the source tool. Open the bundles, the items passed from one module to the next, to see what Anaplan actually received.

  6. 06

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. From now on, each new file lands in the model without you touching it.

Modules

What each Anaplan module does

Anaplan gives you 14 modules in 4 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

File Actions

5 modules
Anaplan1

Upload and Process a File

Action

In MakeUpload and Process a single file (not a chunked file). This module should only be used for file <50MBs.

Sends one complete file to Anaplan and processes it in the same step, so an export from another tool becomes model data without extra modules around it.

When to use it
a single export file comes from your ERP or a shared drive and should reach Anaplan as it is.
Watch out
this module is meant for files under 50 MB and not for chunked files; bigger ones go through the Advanced upload modules.
Anaplan2

Get Model Files

Search

In MakeGet the ID and information for the model file to upload.

Returns the model files available for upload, with the ID and details of each, so the scenario targets the right file instead of relying on a value copied by hand.

When to use it
ahead of an upload, when the scenario has to find its destination file by itself.
Watch out
a search returns zero, one or several bundles, and the modules placed after it run once for each file found.
Anaplan3

Set the Chunk Count (Advanced)

Action

In MakeNot required if using the `Upload and Prcoess a File` module. If using the (Advanced) upload modules, it's recommend setting the chunkcount metadata of an upload so that the server knows how many chunks to process during an upload.

Tells Anaplan how many chunks a large upload will arrive in, so the server knows how much to process before it starts.

When to use it
only in the Advanced upload chain, before sending the file, which the doc recommends.
Watch out
Upload and Process a File never needs it. If you set the count to -1, you will have to close the upload yourself with Mark the Upload Complete (Advanced).
Anaplan4

Upload a File (Advanced)

Action

In MakeUpload a file.

Pushes a file into Anaplan as part of the Advanced chain, where each stage of the upload is its own module and processing comes later as a separate step.

When to use it
the file is too heavy for Upload and Process a File, or you want the import launched on its own.
Watch out
nothing is imported by this module alone; Run an Import or Run a Process has to follow.
Anaplan5

Mark the Upload Complete (Advanced)

Action

In MakeIf the chunk count is set to -1, the upload must be marked as complete before processing or importing.

Closes an Advanced upload so Anaplan treats the file as finished and ready to be used by an import or a process.

When to use it
after the last Upload a File (Advanced) step, whenever the chunk count was set to -1.
Watch out
the doc makes this step mandatory before any processing or import in that case, so place it ahead of Run an Import.

Read Requests

3 modules
Anaplan6

Initiate a Read Request

Action

In MakeInitiate a read request and confirm the request completes. Use the Download Read Request module to download the results.

Asks Anaplan to prepare an export of model data and confirms the request completes, which is the first half of getting figures out of a model.

When to use it
a report, a spreadsheet or a BI tool needs the latest numbers from your plan.
Watch out
this module does not hand you the data; add Download a Read Request right after it to collect the result.
Anaplan7

Download a Read Request

Action

In MakeDownload the available pages of a read request, returned as a CSV file.

Collects the pages of a finished read request and gives them to you as a CSV file, ready to store in a drive, attach to an email or load into a database.

When to use it
directly after Initiate a Read Request, in any export scenario.
Watch out
it only works on a request started beforehand; without that first module there is simply nothing to download.
Anaplan8

Delete a Read Request Data

Action

In MakeDelete or cancel an initiated read request to make space for future exports.

Removes or cancels a read request you started, freeing room so the exports that come next have space.

When to use it
last in an export scenario, once the CSV file is stored elsewhere.
Watch out
a deleted request cannot be downloaded any more, so keep this module after Download a Read Request, never before it.

Other Actions

3 modules
Anaplan9

Run a Process

Action

In MakeRun a process and confirm the process completed.

Starts one of your Anaplan processes and reports back once it has completed, so the next module only works on finished results.

When to use it
fresh data has just landed and the model should run the process your team built around it.
Watch out
pick the process carefully; Get Model Processes lists the ones available in the model if you are unsure of the exact name.
Anaplan10

Run an Import

Action

In MakeRun an import task and confirm import task completed.

Launches an import task in your model and confirms when it is done, turning an uploaded file into values you can see inside Anaplan.

When to use it
the file already sits in Anaplan and only the import you configured there is left to run.
Watch out
after an Advanced upload with a chunk count of -1, mark the upload complete first, as the doc requires.
Anaplan11

Write Cell Data

Action

In MakeSet cell values in a module.

Sets values straight into the cells of an Anaplan module, with no file to build, which suits small updates coming from another app.

When to use it
a deal amount changes in the CRM and the sales forecast should show it.
Watch out
here the word module means the Anaplan grid, not a brick of your Make scenario; the two are easy to mix up.

Other

3 modules
Anaplan12

Get Model Processes

Search

In MakeLists the processes available for the given model.

Lists the processes available for a given model, so you see what exists before choosing which one to launch.

When to use it
while building, to check what a model offers, or ahead of Run a Process when the choice depends on data.
Watch out
each process comes out as its own bundle, so a Run a Process placed right after it would run once for every process found.
Anaplan13

List Process Tasks

Search

In MakeList all the tasks and their status for a given process.

Shows all the tasks of a process together with their status, which tells you where a run stands or where it stopped.

When to use it
after Run a Process, to log the outcome or warn the planning team when a task did not finish.
Watch out
each task is a separate bundle, so a notification placed right after it sends one message per task unless you group them with an aggregator.
Anaplan14

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Reaches any endpoint of the Anaplan API with the connection you already set up, covering what the listed modules leave out.

When to use it
you need an Anaplan action that none of the other modules offers.
Watch out
you talk to the API directly, so keep the Anaplan API documentation open to know which endpoint to call and what to send.
Need help

Need help automating Anaplan with Make?

A person reads every message.

FAQ

Anaplan and Make: common questions

01Is the Anaplan Make integration free?
No. Anaplan is an enterprise app in Make, reserved for the Enterprise plan, so the Free plan cannot use it. The Free plan does include 3,000+ standard apps, with 2 active scenarios and a minimum of 15 minutes between scheduled runs, but Anaplan is not among them. On the Anaplan side you also need a paid account, as the Make documentation states. Usage on paid Make plans is counted in credits, where one operation is one module running on one bundle. For the plan details, check the pricing page of Make before planning your scenarios.
02What do you need to connect Anaplan to Make?
Three things: a paid Anaplan account, a Make organization on the Enterprise plan, and your Anaplan username and password. The connection starts from any Anaplan module: click Create a connection, give it a name if you want, fill in the Username and Password fields, then click Save. If Anaplan asks for it, authenticate and confirm access. The connection is created once and every Anaplan module of your scenarios reuses it, so there is nothing to repeat when you add an import or an export later on.
03Does Anaplan trigger Make scenarios in real time?
No, because the Anaplan app has no trigger module at all. A scenario that uses it starts in one of two ways. Either another app opens the flow, for example the storage tool where exports land, and its trigger decides how fast things move: an instant trigger reacts as soon as the app calls Make through a webhook, a scheduled one is polled on the scenario schedule. Or the scenario runs on the clock of its first module, every 15 minutes by default, and the Anaplan modules act at each run.
04What if an Anaplan module is missing in Make?
Use Make an API Call. Anaplan has this module in Make, and it can reach any endpoint of the Anaplan API with the connection you already created, so an action missing from the 14 modules is still within reach. It asks you to know which endpoint to call, so keep the Anaplan API documentation nearby. For file size, the rule is simpler: Upload and Process a File is meant for files under 50 MB, and larger files go through the Advanced upload chain with a chunk count and a completion step.
05Make or n8n for Anaplan?
It depends on what your team already runs. On the Make side, the facts are clear: 14 Anaplan modules covering uploads, imports, processes, read requests and cell writes, plus Make an API Call, all behind the Enterprise plan. The same app may also exist as an n8n node, so check what that node offers for your use case before choosing. Compare the modules you need, the plan your company already has, and who will maintain the scenarios. No ranking applies here; the right tool is the one your team can run and keep up.