Resources · Make integration

Merk Make integrationAutomate Merk with Make.

Can Make pull company data out of Merk for you? The Merk Make integration gives you 7 modules: 6 actions and 1 search, with no trigger of its own. This page shows what each one returns, how to link your account and how to build a first scenario.

Try the Merk integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Merk Make integration let you do?

The Merk Make integration links your Merk account to Make so a scenario, the automation you build in Make as a chain of modules, can look up companies and read your saved searches and sets in Merk. You never write code: each module is one brick you drop into the chain and fill in.

An enriched lead list. A new prospect lands in your CRM or a spreadsheet through another app. Search company finds the matching firm in Merk, then Get company info returns its record so the next module can write it back next to the lead.

A saved search that feeds your pipeline. If your team already keeps searches in Merk, Get saved searches lists them and Get results of saved search pulls the companies they contain, ready to be sent to a sheet or a CRM.

Sets turned into shared lists. Get sets shows the sets stored in your account and Get result of a set returns what one of them holds, so a sales assistant can reuse it elsewhere without exporting by hand.

Be aware of the limits. Make itself says its documentation for Merk is limited because little public information exists about the app, and Merk has no trigger, so something else has to start the scenario. The Make troubleshooting guide at Make troubleshooting helps when a run fails. The same app often has an n8n node too; n8n vs Make lays out how the two tools differ, and Make review gives the wider picture of the platform.

Connect

How do you connect Merk to Make?

  1. 01

    Add a Merk module and open the connection

    Inside a scenario, add any Merk module, such as Search company, then click Create a connection. A connection is your Merk account linked to Make once and reused by every Merk module afterwards.

  2. 02

    Give it a name you will recognize

    Naming the connection is optional, but a clear label like the account owner or the team helps later, when several people build scenarios in the same Make workspace and each picks an account from a list.

  3. 03

    Authorize Make, then save

    Depending on what Merk offers, either approve access on the Merk page that opens or paste the key Merk gives you. Click Save, and the module can now list what your account holds.

First scenario

Your first scenario with Merk and Make

GoalWhen a new company name reaches Make from another app, Make finds that company in Merk and returns its full record.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the + to place the first module. Since Merk has no trigger, start with the app where your company names come from.

  2. 02

    Add Search company

    Click the + on the right of that first module, search for Merk, pick Search company and create your connection. Map the company name received from the previous module into the search.

  3. 03

    Add Get company info

    Click the + again, choose Get company info and map the company returned by the search, so Make reads the complete record of each match rather than just the search result.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open each module to read the bundles it received, a bundle being one item passed along, here one company.

  5. 05

    Schedule and switch it on

    On the first module, set the schedule, which is every 15 minutes by default on a new scenario, then switch the scenario on so it keeps running without you opening the editor.

Modules

Every Merk module in Make

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

Merk1

Get company info

ActionIn the docs only

Returns the record Merk holds for one company, so the next module can copy it into your CRM, a sheet or an email. Make gives no description, so this reading comes from its name.

When to use it
right after Search company, once you know which firm you want and need its full details.
Watch out
Make documents no fields for this module, so run it once and read the bundle before mapping anything downstream.
Merk2

Get result of a set

ActionIn the docs only

Gives you back the content of one set saved in your Merk account, ready to flow into another tool instead of being exported by hand. That is a deduction from its name, since Make describes nothing.

When to use it
after Get sets, when you already know which set a colleague prepared and want its companies elsewhere.
Watch out
check the output with Run once, since the documentation does not say what one result contains.
Merk4

Get saved searches

ActionIn the docs only

Shows which searches are stored in your Merk account, which helps you pick the right one before asking for its results. Make adds no description, so the name is your only guide.

When to use it
as the step before Get results of saved search, especially when several people save searches and names drift.
Watch out
this module lists searches, not companies; the companies only arrive with the results module.
Merk5

Get sets

ActionIn the docs only

Lists the sets kept in your Merk account so your scenario knows which ones exist and can pick one to read. Deduced from its name: Make gives no further detail.

When to use it
ahead of Get result of a set, when you need the reference of a set before reading what it holds.
Watch out
the documentation does not describe what a set is made of, so confirm the output in the editor first.
Merk6

Search company

SearchIn the docs only

Finds companies in Merk from what you already have, a name coming from a form or a CRM for instance, and hands each match to the next module. It is the only search module of the app.

When to use it
at the start of any enrichment flow, before Get company info.
Watch out
a search can return zero, one or several bundles, and every following module runs once per bundle, which costs operations on your plan.
Merk7

Vocative

ActionIn the docs only

This action is listed in Make under the name Vocative, and neither the directory nor the documentation says what it returns, so treat it as a module to explore on a test record before trusting it with real data.

When to use it
only after you have tested it with Run once on a sample input and read the bundle it produces.
Watch out
do not build a live scenario on it before that test.
Need help

Need help automating Merk with Make?

A person reads every message.

FAQ

Merk and Make: frequent questions

01Is the Merk Make integration free?
Yes, Merk is a standard app in Make, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 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, lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one execution of one module on one bundle. Your own Merk subscription is a separate matter this page does not cover.
02What is needed to connect Merk to Make?
A Merk account and a Make account. Make's documentation lists no specific prerequisite for Merk and no dedicated connection steps, so the generic flow applies: add a Merk module, click Create a connection, optionally name it, then authorize Make on Merk's page or paste the key Merk provides, and click Save. The connection is then reused by all 7 Merk modules. If authorization does not go through, check inside Merk which access method your account offers.
03Does Merk trigger Make scenarios in real time?
No, Merk has no trigger at all, neither scheduled nor instant, so it cannot start a scenario by itself. You start the flow in another way: with a trigger from another app, such as a new row in a sheet or a new contact in a CRM, or by setting a schedule on the first module, every 15 minutes by default. The Merk modules then run as steps inside the scenario, each time it executes.
04What if a Merk module is missing in Make?
It depends on what you need. Merk has no Make an API Call module in Make, so you cannot reach an unlisted feature through a custom request here. Make also warns that its Merk documentation is limited because little public information exists about the app. If one of the 7 modules does not cover your case, look at whether another app holds the same data, or ask the team for help on the specific flow.
05Should Merk be automated with Make or n8n?
It depends on your criteria, not on a ranking. Make gives you 7 ready modules for Merk, 6 actions and 1 search, in a visual editor where you test with Run once before switching a scenario on. The same app often exists as an n8n node, so check whether that node covers the operations you need before choosing. Compare the modules each tool offers for Merk, the tool your team already uses, and how you prefer to build.
Same platform

Other docs you might need on this stack.

Browse all integrations