Resources · Make integration

Cambrion Make integrationAutomate Cambrion with Make.

Can Make pass your Cambrion documents along without a line of code? The Cambrion Make integration gives you 6 modules: 1 scheduled trigger and 5 actions. This guide is for teams who already use Cambrion, and it walks you from the API key to a first working scenario.

Try the Cambrion integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Cambrion Make integration automate?

The Cambrion Make integration links your Cambrion account to Make, a visual tool where you build a scenario: an automation made of modules, each one a single brick such as a trigger or an action. You connect Cambrion once, then Make can start executions, send it files and pick up the results for your other tools.

Results that reach your other tools. Put Watch completed Executions at the start of a scenario, then Fetch a JSON Result right after it. Each finished execution becomes a bundle, one item passed from module to module, that you can hand to a spreadsheet, a CRM or a chat app.

Documents sent in from elsewhere. When a file lands in another app, the actions Create an Execution and Upload a File to Execution let a scenario pass it to Cambrion. Going by its name, Process a Document (Asynchronously) handles a document without holding the scenario while Cambrion works; the doc gives no further detail, so test it with your own files.

Anything the list does not cover. Make an API Call reaches any endpoint of the Cambrion API with the connection you already set up.

The Make documentation for Cambrion states no numbered limit, so this page quotes none. Before you pick a plan, the Make pricing page explains how operations are counted. If you are weighing Make against n8n for this kind of work, read n8n vs Make, and for guided practice the Make training starts from zero.

Connect

How do you connect Cambrion to Make?

  1. 01

    Copy your API key in Cambrion

    Log in to Cambrion, click your user name in the left sidebar, then Settings. Unhide the API key, copy it and keep it somewhere safe. Your account needs API access for this key to exist.

  2. 02

    Open a connection in Make

    In your scenario, add any Cambrion module and click Create a connection. A connection is your Cambrion account linked to Make once, then reused by every Cambrion module. The Connection name field is optional.

  3. 03

    Paste the key and save

    Paste the key into the API Key field and click Save. If Make asks you to authenticate and confirm access, accept, and the connection appears in the module, ready to use.

First scenario

Your first scenario with Cambrion

GoalWhen an execution finishes in Cambrion, Make fetches its JSON result so you can send it to another app.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the editor. This first slot holds the module that starts everything.

  2. 02

    Add the trigger

    Search for Cambrion, pick Watch completed Executions and select the connection you made earlier, or click Create a connection if this is your first Cambrion module.

  3. 03

    Fetch the result

    Click the + on the right of the trigger, add Fetch a JSON Result and map the execution coming from the trigger into it, so Make knows which result to pull.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time; open the bubble above each module to read the bundles it received and check that the result looks right.

  5. 05

    Schedule and switch on

    Set the schedule on the trigger with the clock icon. A new scenario checks every 15 minutes by default, and the Free plan does not go below that. Then switch the scenario on.

Triggers

What starts a Cambrion scenario

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

Cambrion1Watch completed Executions

Watch completed Executions

triggerIn the docs only

This trigger gives your scenario a starting point each time Cambrion has finished an execution, so the rest of the chain works on finished output instead of a job still in progress. The doc lists it under Triggers without detail, so its scheduled type is read from its name: check for the clock badge in the editor.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default; it is not real time.
When to use it
as the first module whenever the result, not the upload, is what should set things in motion downstream.
Watch out
an execution that finishes just after a check waits for the next one, and the result waits in Cambrion until then.
Modules

What the Cambrion modules do

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

Cambrion1

Create an Execution

ActionIn the docs only

Starts a new execution in Cambrion from inside a scenario, so the work kicks off without you opening Cambrion. The doc lists it by name only, so open it once to see which fields it asks for.

When to use it
when an event in another app, such as a new file, should open a job in Cambrion.
Cambrion2

Fetch a JSON Result

ActionIn the docs only

Pulls the result of an execution back into Make as JSON, which later modules can map field by field into a sheet, a CRM or a message.

When to use it
right after Watch completed Executions, to turn a finished job into data your other tools read.
Watch out
the doc does not describe the JSON, so run the scenario once and inspect the bundle before mapping anything.
Cambrion3

Make an API Call

ActionIn the docs only

Opens the whole Cambrion API to your scenario, reusing the connection you already created, so you are not stuck when no ready module fits.

When to use it
for any request the other four actions and the trigger do not cover.
Watch out
you write the endpoint and the request yourself, which asks for more care than a ready module with its own form.
Cambrion4

Process a Document (Asynchronously)

ActionIn the docs only

Hands a document to Cambrion for processing. Going by its name, the module does not wait for the processing to end, and the doc adds nothing more, so treat that reading as a guess to confirm with Run once.

When to use it
when the result can come back later, for instance picked up by a second scenario that starts on Watch completed Executions.
Cambrion5

Upload a File to Execution

ActionIn the docs only

Attaches a file to an execution in Cambrion, so a scenario can feed it the document it should work on, taken from an email, a drive or a form.

When to use it
after Create an Execution, mapping the file that the earlier module delivered.
Watch out
on the Free plan, Make handles files up to 5 MB, so check your plan before sending larger scans.
Need help

Need help automating Cambrion with Make?

A person reads every message.

FAQ

Cambrion and Make: common questions

01Is the Cambrion Make integration free?
Yes, on the Make side. Cambrion is a standard app, so its modules are available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes of execution and files up to 5 MB. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute and remove the cap on active scenarios. Access to Cambrion itself is a separate matter: its team activates a free trial during onboarding, and this page does not cover its prices.
02What is needed to connect Cambrion to Make?
A Cambrion account with API access and its API key. To get that access, book an onboarding session through the Cambrion website or write to support@cambrion.ai; the team sets up the account, activates a free trial and provides the credentials. Then find the key under your user name and Settings in Cambrion, paste it in the API Key field when Make asks you to create a connection, and click Save. The connection then serves all 6 Cambrion modules in your scenarios.
03Does the Cambrion trigger react in real time?
No. Watch completed Executions is a scheduled trigger, not an instant one. Make checks Cambrion on the scenario's schedule, which is every 15 minutes by default for a new scenario. On a paid plan you can bring the interval down to 1 minute, while the Free plan stays at 15 minutes minimum. A finished execution therefore reaches your scenario at the next check, not the second it completes. Keep that delay in mind if a person is waiting on the result.
04What if a Cambrion module is missing in Make?
Use Make an API Call. This module can call any endpoint of the Cambrion API from your scenario, with the same connection as the other modules, so you are not limited to the 5 ready actions and the trigger. You write the request yourself, which is less guided than a ready module. The Make documentation for Cambrion gives no numbered limit, so if something blocks you, check your Make plan first, for instance the 5 MB file ceiling on the Free plan.
05Should Cambrion be automated with Make or n8n?
It depends on the tool your team already knows. On Make, Cambrion offers 6 modules, a scheduled trigger and Make an API Call for anything else, all built visually from a single connection. Many apps also have an n8n node, so check whether Cambrion has one before choosing. Base the decision on what each tool actually offers for this app and on who will maintain the scenarios, rather than on a general preference for one platform.
Same platform

Other docs you might need on this stack.

Browse all integrations