Resources · Make integration

ActiveMerge Make integrationAutomate ActiveMerge with Make.

Can Make produce your ActiveMerge documents for you? The ActiveMerge Make integration gives you 3 action modules and no trigger. This guide is for teams that already use ActiveMerge: connect the account, then build a first scenario that generates a document.

Try the ActiveMerge integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the ActiveMerge Make integration do?

The ActiveMerge Make integration lets a Make scenario (the automation you build in Make, a chain of modules) ask ActiveMerge to generate a document or a workflow, without writing code. ActiveMerge has no trigger in Make, so something else starts the scenario: another app, or a schedule you set.

A document built from data you already have. Put the trigger of another app first, for example a form tool, then add Generate Document. The data from the first module is mapped into the ActiveMerge step, so nobody copies it by hand.

A workflow started from outside ActiveMerge. Going by its name, Generate Workflow lets an event in another tool kick off a workflow on the ActiveMerge side. The official docs give no field list for it, so open the module once your account is connected and read what it asks for.

Anything the two named modules skip. Make an API Call reaches any endpoint of the ActiveMerge API with the same connection. It is the way out when you need a call the other modules do not cover.

Keep one limit in mind: the Make documentation page for this app is marked as AI-generated from ActiveMerge's own docs and may contain mistakes, so check important details with ActiveMerge. For a wider view of the tool, read our Make review, and if you are weighing another platform, the n8n vs Make comparison lays out the differences. Credits and plans are covered in Make pricing.

Connect

How do you connect ActiveMerge to Make?

  1. 01

    Add an ActiveMerge module

    Log in to Make, open your scenario and add any ActiveMerge module, then click Create a connection. A connection is your ActiveMerge account linked to Make once and reused by every ActiveMerge module.

  2. 02

    Name the connection

    The Connection name field is optional. A clear name still helps when you manage several ActiveMerge accounts, for instance one for testing and one for production work.

  3. 03

    Enter your ActiveMerge credentials

    Paste the authentication credentials you copied from your ActiveMerge account, or follow the instructions Make shows on screen. Save, and the connection is ready for every module of the scenario.

First scenario

Your first scenario with ActiveMerge

GoalWhen new data arrives in another app, Make asks ActiveMerge to generate a document from it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Pick the app that holds your data, such as a form or a spreadsheet.

  2. 02

    Add Generate Document

    Click the + on the right of that first module, search for ActiveMerge and choose Generate Document. Select your connection, or create it with the three steps above.

  3. 03

    Map the incoming data

    Fill the module fields with values from the first module. Each bundle, meaning one item passed from one module to the next, becomes the data behind one document.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bundles each module received and confirm that ActiveMerge returned the document you expected.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Each module execution counts as one operation on your Make plan.

Modules

What the ActiveMerge modules do

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

ActiveMerge1

Generate Document

ActionIn the docs only

You get a document out of ActiveMerge without opening it: the scenario hands over the data and ActiveMerge does the generating. This is the module to place right after the app where your information lives.

When to use it
a new entry lands in a form or a sheet and should turn into a document without anyone copying fields across.
Watch out
the official docs list no fields for this module, so open it after connecting and check what ActiveMerge expects.
ActiveMerge2

Generate Workflow

ActionIn the docs only

Its name says it: it asks ActiveMerge for a workflow, so a process starts from your scenario instead of by hand. Choose it over Generate Document when the goal is a process in ActiveMerge rather than a single file.

When to use it
a deal closes in your CRM and the matching ActiveMerge workflow should start without anyone launching it.
Watch out
the docs describe nothing about its inputs, so test it with Run once before you switch the scenario on.
ActiveMerge3

Make an API Call

ActionIn the docs only

Reach any endpoint of the ActiveMerge API from your scenario, with the connection you already set up. It covers whatever the two named modules leave aside, so you are not stuck when a need goes beyond generating.

When to use it
the ActiveMerge API offers a call you need and no dedicated module exists for it.
Watch out
you write the request yourself, so know which ActiveMerge endpoint you want before you open the module.
Need help

Need help automating ActiveMerge with Make?

A person reads every message.

FAQ

Questions about the ActiveMerge Make integration

01Is the ActiveMerge Make integration free?
Yes, on the Make side. ActiveMerge is a standard app, so it is available from the Free plan. That plan allows 2 active scenarios, 15 minutes minimum 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 and Enterprise) drop the interval to 1 minute and allow 40 minutes per execution, with usage counted in credits per month. Your ActiveMerge subscription is separate and depends on ActiveMerge's own pricing, which this page does not cover.
02What do you need to connect ActiveMerge to Make?
An active ActiveMerge account and a Make account. In the scenario, add any ActiveMerge module and click Create a connection. You can give the connection a name, which is optional, then enter the authentication credentials copied from your ActiveMerge account or follow the instructions Make displays. Once saved, the same connection serves all three ActiveMerge modules, so you only do this once per account. If you do not have an ActiveMerge account yet, create it first and pick a subscription on their side.
03Does the ActiveMerge Make integration react in real time?
No, because ActiveMerge has no trigger module in Make. All three of its modules are actions, so the scenario has to start from something else. The usual route is the trigger of another app, placed first, with ActiveMerge after it. Another route is to rely on the schedule of the first module, which runs a new scenario every 15 minutes by default. On the Free plan, 15 minutes is also the shortest gap between scheduled runs, while paid plans go down to 1 minute.
04What if the ActiveMerge module you need is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the ActiveMerge API through the connection you already created, so anything the API offers stays within reach even without a dedicated module. The catch is that you build the request yourself, so you need to know which endpoint does the job. Also keep in mind that the Make documentation for this app is flagged as AI-generated from ActiveMerge material and may contain mistakes, so confirm important details with ActiveMerge directly.
05Should you use Make or n8n for ActiveMerge?
It depends on where the rest of your automations already run. In Make, ActiveMerge comes with three action modules, Generate Document, Generate Workflow and Make an API Call, available from the Free plan. Many apps also have an n8n node, but this page does not confirm one for ActiveMerge, so check the n8n side before you decide. Compare the modules each tool offers for your exact use case rather than the tool's reputation, and test one real document on each before committing.
Same platform

Other docs you might need on this stack.

Browse all integrations