Resources · Make integration

Connery Make integrationAutomate Connery with Make.

Can Make drive Connery for you? Yes, and this Connery Make integration guide shows how. Make offers 1 module for Connery, an action called Run an Action. This page explains how to link your account and build a first scenario around it, step by step.

Try the Connery integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Connery Make integration do?

The Connery Make integration lets a Make scenario (the automation you build in Make, a chain of modules) ask Connery to run one of its actions. A module is one brick of that chain. Connery brings a single one, Run an Action, so something else has to start the scenario: a trigger from another app or the schedule Make sets on the first module.

Reacting to a new record elsewhere. Put the trigger of another app first, for example a form tool or a spreadsheet, then add Run an Action. Each new item that arrives becomes a bundle (one item passed from a module to the next), and Connery acts on it without anyone copying data by hand.

Running a Connery action on a clock. A scenario can also start from its schedule alone. The default is every 15 minutes, and the Free plan does not go below that. Paid plans go down to 1 minute. Make then calls Run an Action each time the scenario runs.

Chaining Connery into a longer flow. Run an Action does not have to be the last brick. Click the + after it and add a module from another app, for example to notify a colleague once Connery has been called. Browse a neighbor page such as the 2Chat Make integration for ideas on what to plug after it.

Know the limits before you start. Make's own documentation for Connery is marked as limited, because little public information exists about the app, and there is no Make an API Call module to fall back on. If you want a view on Make as a whole, read the Make review. Connery may also exist as an n8n node; the n8n vs Make comparison lays out the differences between the two tools.

Connect

How do you connect your Connery account to Make?

  1. 01

    Add the module and open the connection

    In your scenario, add the Run an Action module, then click Create a connection. A connection is your Connery account linked to Make once, and every Connery module reuses it afterwards.

  2. 02

    Name it so you recognize it

    Giving the connection a name is optional. It helps as soon as you link more than one Connery account, for instance a test account and the live one, because you pick it from a list later.

  3. 03

    Authorize Make, then save

    Depending on what Connery asks for, either approve Make on the Connery page that opens or paste the key Connery gives you. Then click Save. Make's documentation does not spell out which of the two Connery uses.

First scenario

Your first scenario with Connery

GoalWhen a new item shows up in another app, Make runs a Connery action on it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. This first spot goes to the app where your data starts, since Connery has no trigger.

  2. 02

    Pick the starting app

    Search the app that holds your data, choose its trigger and create its connection. Make then lists the folders, sheets or objects it can read, so you point at the right place.

  3. 03

    Add Run an Action

    Click the + on the right of the first module, search Connery and pick Run an Action. Create the Connery connection, then map data from the first module into its fields.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Then read the bundles each module received and check that Connery got what you meant to send.

  5. 05

    Schedule it and switch it on

    Set the schedule on the first module. A new scenario checks every 15 minutes by default. Then switch the scenario on; each module run counts as an operation on your plan.

Modules

What Connery can do in Make

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

Connery1

Run an Action

ActionIn the docs only

This module lets your scenario ask Connery to run one of its actions, with no code on your side. As its name says, it is an action: it works on one bundle at a time, once for each item that reaches it, and each run counts as one operation.

When to use it
right after the trigger of another app, when a new record there should make Connery do something.
Watch out
Make documents Connery only partially, so test each setup with Run once before you switch the scenario on.
Need help

Need help automating Connery with Make?

A person reads every message.

FAQ

Connery and Make: common questions

01Is the Connery Make integration free?
Yes. Connery is a standard app in Make, so it works from the Free plan onward. That plan has its own limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Make counts usage in operations, one per module run on one bundle. Nothing here covers what Connery itself may charge.
02What does it take to connect Connery to Make?
A Connery account and a Make account. Make's documentation lists no specific prerequisite for Connery and gives no dedicated steps, so the generic flow applies. Add the Run an Action module, click Create a connection, optionally give the connection a name, then either authorize Make on the page Connery opens or paste the key Connery provides. Click Save and the connection stays available to every Connery module in your scenarios. If it fails, check in Connery which kind of access it expects.
03Does the Connery Make integration react in real time?
No, not on its own, because Connery has no trigger in Make. Its only module is an action, so the scenario needs something else to start it. Two options exist. You can place another app's trigger first, and Connery acts on each new item that trigger passes along. Or you can rely on the schedule of the scenario, which Make sets to every 15 minutes by default. On a paid plan that interval can drop to 1 minute, while the Free plan stays at 15 minutes minimum.
04What if a Connery module is missing in Make?
It depends on what is missing. Connery has a single module in Make, Run an Action, and no Make an API Call module that would let you reach other parts of the app. Make also flags its Connery documentation as limited, because little public information exists about the app. If Run an Action does not cover your case, look for another app in Make that handles the step, or ask the team for help, so someone looks at your case and suggests a route that fits what Make actually offers.
05Make or n8n for Connery: which one fits?
It depends on how you prefer to build. Connery may also exist as an n8n node, so both tools can be worth a look. On the Make side, the facts are simple: one action module, Run an Action, available from the Free plan, a visual editor where you test with Run once, and a schedule of every 15 minutes by default. Check what the n8n node offers for your case before choosing. There is no ranking to give between the two tools, only criteria such as the modules you need and how you like to work.
Same platform

Other docs you might need on this stack.

Browse all integrations