Resources · Make integration

Recommand Make integrationAutomate Recommand with Make.

Can Make keep your Recommand companies and documents in order without you clicking through them? The Recommand Make integration gives you 12 modules: 10 actions and 2 searches. This guide shows how to link your account, build a first scenario and pick the right module for each job.

Try the Recommand integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Recommand Make integration do for you?

The Recommand Make integration lets a Make scenario, the automation you build in Make, read and change what lives in your Recommand account: companies on one side, documents on the other. Each step of that scenario is a module, one brick that does one thing, such as creating a company or sending a document.

A company record that follows your CRM. When a new customer appears in the tool your sales team uses, Create a company adds it to Recommand, and Update a company keeps the details aligned when they change on the other side.

Documents that leave on their own. Once a file or a record is ready in another app, Send a document pushes it through Recommand without anyone opening the dashboard.

An inbox you actually process. List documents brings back what is stored, Get a document reads one in detail, and Mark document as (un)read flags what your scenario already handled.

Make's own documentation for Recommand is labeled as limited, because little public information exists about the app. So the notes below stick to what each module name tells you, and anything the modules miss goes through Make an API call. Before choosing a platform, the n8n vs Make comparison lays out the criteria, the Make pricing page explains how operations are counted, and the Make training helps if scenarios are new to you.

Connect

How do you connect your Recommand account to Make?

  1. 01

    Add a Recommand module

    Open a scenario, click the +, search for Recommand and pick any module, for example List companies. Then click Create a connection. A connection is your Recommand account linked to Make once and reused by every Recommand module.

  2. 02

    Name it and authorize Make

    Give the connection a name if you plan to link several accounts, such as one per client. Then either approve access on the Recommand page that opens or paste the key Recommand gives you, depending on what the window asks for.

  3. 03

    Save and check the module

    Click Save. Back in the module, Make can now read your account, so the fields it can fill from Recommand become available. If the module opens without an error, the connection works.

First scenario

Your first scenario with Recommand and Make

GoalWhen a new customer lands in another app, Make creates the matching company in Recommand.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Since Recommand has no trigger, start with the app where new customers first appear, such as your CRM or a form tool.

  2. 02

    Set up the starting module

    Pick that app's trigger, create its connection and fill its fields. Make lists the objects it can read once the account is linked, so you choose from a menu instead of typing names.

  3. 03

    Add Create a company

    Click the + on the right of the first module, search for Recommand and choose Create a company. Connect your account, then map the customer data from the first module into its fields.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, a bundle being one item passed along, here one customer. Check the new company in Recommand.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, and the Free plan cannot go below that. Adjust if needed, then switch the scenario on.

Modules

What each Recommand module does in Make

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

Recommand1

Create a company

ActionIn the docs only

Adds a new company to your Recommand account from data your scenario already holds, so nobody has to type the same customer twice.

When to use it
right after a deal is won or a signup form is submitted in another app, to open the matching record in Recommand.
Watch out
it creates a record every time it runs, so search with List companies first if the customer might already exist.
Recommand2

Delete a company

ActionIn the docs only

Removes a company from Recommand for good, which keeps your account free of customers you no longer work with.

When to use it
when a contract ends or a duplicate was spotted and your team confirmed it should go.
Watch out
a deletion cannot be undone from Make. Test the scenario with Run once on a dummy company before pointing it at real customers.
Recommand3

Delete a document

ActionIn the docs only

Clears one document out of Recommand, useful to get rid of a test file or a document created by mistake.

When to use it
at the end of a cleanup scenario that first used List documents to find what should disappear.
Watch out
a deletion is final. Run the scenario once in test and read the bundle before letting it delete anything.
Recommand4

Get a company

ActionIn the docs only

Fetches the full record of one company you already know, so the next modules can reuse its details without asking anyone.

When to use it
when an earlier step gave you the company's identifier and you need the rest of its information to fill a document or another app.
Watch out
it expects one precise company. If you only have a name, start with List companies instead.
Recommand5

Get a document

ActionIn the docs only

Pulls the details of a single document stored in Recommand, ready to be copied into a spreadsheet, a chat message or a storage tool.

When to use it
after List documents or Inbox returned documents and you want the complete content of one of them.
Watch out
each call reads one document and counts as one operation, the unit Make bills on your plan.
Recommand6

Inbox

ActionIn the docs only

Going by its name, this module opens the inbox of your Recommand account: the place to look when your scenario handles what arrives rather than what you send.

When to use it
as the first Recommand step of a scenario that processes incoming items, before Get a document or Mark document as (un)read.
Watch out
Make's documentation gives no detail on this module, so test it with Run once and read exactly what it returns.
Recommand7

List companies

SearchIn the docs only

Brings back the companies saved in Recommand, which lets your scenario check who is already there before acting.

When to use it
ahead of Create a company, to avoid duplicates, or to loop through your customers for a sync with another tool.
Watch out
as a search, it can return zero, one or several bundles, and every following module runs once per bundle.
Recommand8

List documents

SearchIn the docs only

Returns the documents held in your account so a scenario can sort, copy or archive them in one pass.

When to use it
when you want a record of your documents in a spreadsheet or need to find the ones a later step will send, read or delete.
Watch out
every document returned becomes a bundle, and each one costs operations in the modules placed after it.
Recommand9

Make an API call

ActionIn the docs only

Calls any endpoint of the Recommand API with the connection you already set up, which covers what the eleven other modules leave out.

When to use it
when you need an action Recommand offers but that has no dedicated module in Make.
Watch out
you write the request yourself, so you need the Recommand API reference, which the Make documentation does not provide.
Recommand10

Mark document as (un)read

ActionIn the docs only

Changes the read status of a document, so your team sees at a glance what the scenario already processed and what still needs a human.

When to use it
as the last step after a document was copied or forwarded, to flag it as handled.
Watch out
the name suggests one module for both states. Check which one you picked before activating, or everything ends up flagged the wrong way.
Recommand11

Send a document

ActionIn the docs only

Sends a document through Recommand straight from your scenario, without anyone opening the app to do it by hand.

When to use it
once the data behind the document is final in your billing or sales tool, typically after an approval step.
Watch out
a sent document goes out for real. Keep Run once tests on a test company until the result looks right.
Recommand12

Update a company

ActionIn the docs only

Edits an existing company in Recommand so its details match the latest version held in your other tools.

When to use it
when a customer changes address or contact in your CRM and Recommand should follow without a copy and paste.
Watch out
it needs to know which company to change, so feed it the identifier from Get a company or List companies.
Need help

Need help automating Recommand with Make?

A person reads every message.

FAQ

Recommand and Make: common questions

01Is the Recommand Make integration free?
Yes, Recommand is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one per module run on one bundle. Your Recommand subscription is a separate matter.
02What do you need to connect Recommand to Make?
A working Recommand account and a Make account. Make's documentation lists no prerequisite and no dedicated steps for this app, so the generic flow applies: add a Recommand module, click Create a connection, optionally name it, then authorize Make on the Recommand page or paste the key Recommand provides, and click Save. The connection is then reused by all 12 modules, so you only do this once per account, whatever the scenario.
03Can Recommand start a Make scenario in real time?
No, not on its own. Recommand has no trigger module in Make, neither scheduled nor instant, so it cannot launch a scenario when something changes in your account. Two ways around it: start the scenario with a trigger from another app, or let the schedule on the first module run it, every 15 minutes by default. A scheduled scenario can then call Inbox or List documents to see what your account holds at that moment.
04What if a Recommand module is missing in Make?
Use Make an API call. It reaches any endpoint of the Recommand API with the same connection, so an action without a dedicated module is still within reach. You will need the Recommand API reference, since Make's documentation for this app is marked as limited and says little about each module. When a module behaves unexpectedly, test it with Run once and read the bundles it returns before building on it.
05Should you use Make or n8n for Recommand?
It depends on what your team already runs. Make gives Recommand 12 ready modules, including a generic API call, and a visual editor where each step is tested with Run once. Many apps also have an n8n node, but the Make documentation says nothing about one for Recommand, so check n8n's node list before deciding. If both exist, compare the modules each side covers for your actual use case rather than the brand.
Same platform

Other docs you might need on this stack.

Browse all integrations