Resources · Make integration

Mockingbyrd Make integrationAutomate Mockingbyrd with Make.

Can Make push contacts and call results into Mockingbyrd without a line of code? The Mockingbyrd Make integration gives you 4 action modules and no trigger. This page shows how to link your account, build a first scenario and pick the right module.

Try the Mockingbyrd integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Mockingbyrd Make integration do for you?

The Mockingbyrd Make integration lets a Make scenario (the automation you build, a chain of steps) write into your Mockingbyrd account. Each step is a module, one brick of the scenario. Mockingbyrd brings four of them, all actions, so the scenario always starts from another app or from a schedule.

New leads land in Mockingbyrd on their own. A form tool or a CRM starts the scenario, and Add a Contact creates the person in Mockingbyrd with the details it received. No more copy and paste between tabs.

Calls and conversations get closed out from elsewhere. Call Complete and Conversation Complete are the two modules whose names point at wrapping up an exchange. Make publishes no description for them, so open each one in the editor and read its fields before you plan around it.

Anything else goes through the API. Make an API Call reaches any endpoint of the Mockingbyrd API with the connection you already set up.

Keep one limit in mind: the Make documentation for Mockingbyrd is marked as limited, because little public information exists about the app. Expect to test more than usual. If you get stuck, the Make troubleshooting guide covers common errors, and the n8n vs Make comparison helps if you are still choosing a tool. To learn the editor itself, start with the Make training.

Connect

How do you connect Mockingbyrd to Make?

  1. 01

    Add a Mockingbyrd module

    In your scenario, click the + and search for Mockingbyrd. Pick any of its modules, then click Create a connection. A connection is your Mockingbyrd account linked to Make once and reused by every Mockingbyrd module.

  2. 02

    Name the connection

    Give it a name you will recognize later, such as the workspace or the client it belongs to. This step is optional, yet it saves confusion as soon as you run more than one account.

  3. 03

    Authorize and save

    Approve access on the Mockingbyrd page that opens, or paste the key Mockingbyrd gives you if Make asks for one. Then click Save. Every Mockingbyrd module can now use your account.

First scenario

Your first scenario with Mockingbyrd

GoalWhen a new lead shows up in another app, Make adds it to Mockingbyrd as a contact.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since Mockingbyrd has no trigger, this first module comes from the app where your leads arrive.

  2. 02

    Add Add a Contact

    Click the + on the right of that first module, search for Mockingbyrd and pick Add a Contact. Click Create a connection if you have not linked your account yet.

  3. 03

    Map the lead data

    Fill the fields Make shows by mapping values from the first module. Each lead travels as a bundle, one item passed from a module to the next, so every lead becomes its own contact.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Read the bundles each module received, then check in Mockingbyrd that the contact looks right.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. Each module run on a bundle is one operation, the unit Make counts on your plan.

Modules

What each Mockingbyrd module does

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

Mockingbyrd1

Add a Contact

ActionIn the docs only

You get a new contact in Mockingbyrd built from data another app hands over, with no manual entry. It is the natural landing spot for leads captured somewhere else.

When to use it
right after a form, a CRM or a spreadsheet step that produces one person per bundle.
Watch out
Make publishes no description of its fields, so run it once on a test record before feeding real leads.
Mockingbyrd2

Call Complete

ActionIn the docs only

This action gives your scenario a step named after a finished call in Mockingbyrd. Its name suggests an action, and Make documents nothing more, so the fields shown in the editor are your only guide to what it records.

When to use it
when another tool knows a call has ended and Mockingbyrd should hear about it.
Watch out
test it with Run once on a dummy call first and check the result in Mockingbyrd.
Mockingbyrd3

Conversation Complete

ActionIn the docs only

Here the step is named after a finished conversation rather than a call. The Make documentation stays silent on how the two differ, so compare their fields side by side in the editor before choosing.

When to use it
when your process tracks conversations, and the closing moment happens in another app.
Watch out
the docs for Mockingbyrd are marked as limited; keep a test scenario around to confirm behavior.
Mockingbyrd4

Make an API Call

ActionIn the docs only

With this module you can reach any endpoint of the Mockingbyrd API while reusing the connection you already created. It covers whatever the three other modules leave out.

When to use it
when you need an operation that has no ready made module in Make.
Watch out
you write the request yourself, so keep the Mockingbyrd API reference open while you write it.
Need help

Need help automating Mockingbyrd with Make?

A person reads every message.

FAQ

Questions people ask about Mockingbyrd and Make

01Is the Mockingbyrd Make integration free?
Yes, Mockingbyrd is a standard app in Make, available from the Free plan. The Free plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, runs of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute, lift the cap on active scenarios and allow 40 minutes per run. Usage is counted in credits, meaning operations, each month. Your Mockingbyrd subscription is a separate matter that Make does not cover.
02What do you need to connect Mockingbyrd to Make?
A Make account and access to your Mockingbyrd account. The Make documentation lists no prerequisites and no Mockingbyrd specific steps, so you follow the generic flow: add a Mockingbyrd module, click Create a connection, optionally name it, authorize Make on the Mockingbyrd page or paste the key the app provides, then click Save. That single connection then serves all four Mockingbyrd modules in every scenario you build, so you only do it once per account.
03Does Mockingbyrd trigger Make scenarios in real time?
No, Mockingbyrd has no trigger module in Make, neither scheduled nor instant, so it cannot start a scenario by itself. You start the scenario another way. Either another app provides the first module, for example the tool where your leads or calls are logged, or you rely on the schedule of the first module, which runs every 15 minutes by default on a new scenario. The Mockingbyrd modules then come after, as actions in the chain.
04What if a Mockingbyrd module is missing in Make?
Use Make an API Call. That module can reach any endpoint of the Mockingbyrd API with the same connection as the other modules, so an operation without a ready made module is still within reach. Be aware that Make marks its Mockingbyrd documentation as limited, because little public information exists about the app. You will need the Mockingbyrd API reference on hand to write the request, and a test run with Run once before you switch anything on.
05Should you use Make or n8n for Mockingbyrd?
It depends on which tool offers what you need for this app. In Make, Mockingbyrd comes with four action modules and a generic API module, and no trigger. Many apps also have an n8n node, but this page cannot confirm one exists for Mockingbyrd, so check the n8n catalog before deciding. Then compare the two on concrete points: the operations you need, how your scenario gets started, and which editor your team already knows. Neither tool is ranked above the other here.
Same platform

Other docs you might need on this stack.

Browse all integrations