Resources · Make integration

Cubo CRM Make integrationAutomate Cubo CRM with Make.

New deals keep landing in other tools before anyone types them into Cubo CRM? The Cubo CRM Make integration gives you 3 action modules to open and edit negotiations without code. This guide links your account, builds a first scenario with you and explains each module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Cubo CRM Make integration do for you?

The Cubo CRM Make integration lets Make write into your CRM for you. In Make, a scenario is the automation you build: a chain of modules, where each module is one brick, such as an action in one app. With Cubo CRM, those bricks create a negotiation or update one, based on what happened elsewhere.

A negotiation for every inbound lead. When a prospect fills in a form or books a call in another app, Create a Negotiation opens the record in Cubo CRM, so sales starts from a clean pipeline instead of a copy-paste backlog.

A pipeline that follows the rest of your stack. When a quote is accepted or a contract comes back signed in another tool, Update a Negotiation changes the matching record, and the CRM tells the truth without a manual pass.

Anything else the Cubo CRM API offers. Make an API Call reuses the same connection to reach endpoints the two named modules do not cover.

Know the limits before you plan. The app has no trigger and no search module, so the scenario must start from another app or from a schedule, and the official Make doc for Cubo CRM warns that its text is AI-generated and should be checked against the vendor. If you hesitate between tools, the n8n vs Make comparison sets out the criteria. To learn the editor properly, see Make training, and when a run fails, keep Make troubleshooting close.

Connect

How do you connect Cubo CRM to Make?

  1. 01

    Generate a key in Cubo CRM

    Log in to Cubo CRM, open the API Key section and create a new key. Give it a title you will recognize later, confirm, then copy the generated value. That value is what Make asks for.

  2. 02

    Add a Cubo CRM module

    In your scenario, add any Cubo CRM module and click Create a connection. A connection is your Cubo CRM account linked to Make once, then reused by every module of the app.

  3. 03

    Paste the key and save

    Type a label in Connection name if you want one, it is optional. Paste the key you copied, save, and the module is ready to use.

First scenario

Your first scenario: turn a new lead into a Cubo CRM negotiation

GoalWhen a new lead appears in another app, Make opens a matching negotiation in Cubo CRM.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to place the first module. That first module is the trigger, and it comes from the app where your leads show up.

  2. 02

    Pick the lead source

    Search the app that collects your leads, pick its trigger and link your account. Each lead it finds becomes a bundle, one item passed on to the next module.

  3. 03

    Add Create a Negotiation

    Click the + on the right, search Cubo CRM and choose Create a Negotiation. Connect your account, then map the lead data from the first module into the fields Make shows.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received. Open Cubo CRM and check that the negotiation looks right.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run counts as one operation on your Make plan.

Modules

What each Cubo CRM module does

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

Cubo CRM1

Create a Negotiation

ActionIn the docs only

Opens a fresh negotiation in Cubo CRM from data another module hands over, so a lead or a request turns into a deal your sales team can work on without retyping anything.

When to use it
right after the step that captures a new prospect, like a form reply or a booked call.
Watch out
every bundle that reaches this module creates one record, so test with Run once before switching on to avoid duplicates.
Cubo CRM2

Make an API Call

ActionIn the docs only

Gives you access to any endpoint of the Cubo CRM API with the connection you already set up, which covers what the two negotiation modules leave out.

When to use it
when neither Create a Negotiation nor Update a Negotiation does what your process needs.
Watch out
here you work from the vendor's API documentation, not from a guided form, so check each request with Run once.
Cubo CRM3

Update a Negotiation

ActionIn the docs only

Changes a negotiation that already exists, so the pipeline in Cubo CRM keeps pace with what happens in your quotes, contracts or support tools without a manual edit.

When to use it
after an event elsewhere that moves a deal forward, like a signed quote.
Watch out
the app has no search module, so make sure the scenario can tell the module which negotiation to change, for example from data kept when it was created.
Need help

Need help automating Cubo CRM with Make?

A person reads every message.

FAQ

Cubo CRM and Make: common questions

01Is the Cubo CRM Make integration free?
Yes, on the Make side. Cubo CRM is a standard app, available from the Free plan. That plan lets you keep 2 scenarios active, with at least 15 minutes between two scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one per module run on one bundle. Your Cubo CRM subscription is separate and not covered here.
02What do you need to connect Cubo CRM to Make?
An active Cubo CRM account and an API key. You create the key in the API Key section of Cubo CRM: give it a title, confirm, and copy the generated value. In Make, add a Cubo CRM module, click Create a connection, optionally name it, then paste the key. The connection is saved once and every Cubo CRM module in your scenarios reuses it, so you do not repeat the setup for each module or each new scenario you build.
03Can a Cubo CRM scenario start automatically?
Yes, but not from Cubo CRM itself. The app has no trigger module, so nothing in Cubo CRM can launch a scenario. You have two ways around it. Start with the trigger of another app, such as the tool that collects your leads, and put the Cubo CRM module after it. Or rely on the schedule of the first module, which runs every 15 minutes by default on a new scenario, and at most every 15 minutes on the Free plan.
04What if the Cubo CRM module you need is missing?
Use Make an API Call. It reaches any endpoint of the Cubo CRM API with your existing connection, so you are not limited to creating and updating negotiations. You write the request from the Cubo CRM API documentation. Keep in mind that the official Make doc for this app states its content is AI-generated and may contain errors, so confirm important details with Cubo CRM directly before you rely on them in a live scenario.
05Should you use Make or n8n with Cubo CRM?
It depends on what you need to build. On Make, Cubo CRM offers 3 modules: two for negotiations and one open API call, with no trigger and no search. Before choosing, check whether n8n has a node for Cubo CRM, since the same app often exists on both, and compare which operations each tool covers for your process. Pick the one whose modules match the steps you actually need, and the editor your team is comfortable with.