Resources · Zapier integration

MadKudu Zapier integrationAutomate MadKudu with Zapier.

The MadKudu Zapier integration gives you 0 triggers, 0 actions and 1 search. It cannot start a Zap or write anything back. What it does is answer one question for any email address that reaches your Zap: who is this person, which company, and how qualified.

See the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MadKudu Zapier integration is for

The integration links MadKudu, a tool built to score your leads, to Zapier, the service that chains apps together without you copying data by hand. On Zapier, MadKudu is a lookup: you hand it an email address picked up by another app, and it returns person data, company data and a qualification the next steps can use.

Three outcomes come up again and again, and all three rest on the same operation, Find Person and Company Information. The first is an enriched sign-up sheet: a form submission arrives, the search runs on the email, and the row written to your spreadsheet already carries the company and the qualification, so nobody has to research the name later.

The second is a sorted inbox. The search sits between a new contact and a message to your team, and a filter only lets the message through when the qualification matches what you chose. The third is a cleaner contact base: the lookup feeds the company data into the record your other tool keeps, instead of a bare address.

Now the limits, because they shape everything. MadKudu has no trigger on Zapier, so a Zap never starts from it: another app always goes first. It has no action either, so nothing you do in Zapier writes into MadKudu. And the one search works from an email address only. If you are weighing platforms before you commit, see our n8n vs Zapier and Make vs Zapier comparisons.

Vocabulary

Zapier words, in one minute

Seven terms are enough to read the rest of this page. Each one is used exactly as defined here.

Zap
The automation you build on Zapier: one starting event, then one or more steps that run every time that event happens.
Trigger
The event in an app that opens the Zap. With MadKudu, it always comes from another app, since MadKudu offers none.
Action
A step that does the work once the Zap has started: it writes, sends or moves something in an app for you.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance is a count of those.
Polling vs instant
A polling trigger is checked by Zapier on a timer; an instant trigger is reported by the app the moment the event happens.
Filter
A step that lets the Zap go on only when the incoming data meets a condition you set, and stops it otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can reuse what it found.
Cost

What a MadKudu Zap really costs

The catch here is not the price of a task. It is the size of the Zap the lookup forces on you.

  • TriggerNever billed
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo
  • Zap with a searchMulti-step, paid plan

The trigger never costs a task, and Zapier checking for new data is free too. Each action that succeeds counts once; one that fails is not billed. MadKudu is not a premium app, but a Zap with a search is a multi-step Zap, and the free plan stops at one trigger plus one action. In practice the MadKudu search needs a paid plan. The interval grid below applies to the polling trigger of the app that starts your Zap.

Connect

Connect MadKudu to Zapier in three steps

  1. 01

    Open your connections

    In your Zapier account, go to the Apps page and click + Add connection. A connection is your MadKudu account linked once, then reused by every step that calls MadKudu.

  2. 02

    Pick MadKudu

    Type MadKudu in the search box of the dialog, select it, then click Add connection. You need an existing MadKudu account for this; Zapier only links to it.

  3. 03

    Sign in and allow access

    A new tab opens. Sign in to MadKudu there and grant Zapier access to the account. Back in Zapier, the connection shows in your list, ready for the search step.

First Zap

Your first Zap: a form sign-up that arrives already qualified

GoalEach new form submission is looked up in MadKudu, and a row with the person, the company and the qualification lands in your spreadsheet.

  1. 01

    Start from the form

    Create a Zap and choose your form tool with its new submission event as the trigger. MadKudu cannot fill this slot, so the Zap always opens on another app.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent submissions from the connected account; pick one whose email field is filled in.

  3. 03

    Add the MadKudu lookup

    Add a step, choose MadKudu and pick Find Person and Company Information under the SEARCH heading. Map the form's email field into the Email box.

  4. 04

    Write the result

    Add your spreadsheet with its new row action. Map the columns from the search output, so each row carries what MadKudu returned for that address.

  5. 05

    Test, then publish

    Test each step and read what came back before moving on. When the row looks right, click Publish to switch the Zap on. It needs a paid plan, since it has three steps.

Searches

The MadKudu search

1 search step looks for data that already exists in MadKudu, so a later step can use it.

A search step sits under its own SEARCH heading at the bottom of the Action event list. Three settings decide what the Zap does when the answer is not one clean match.

1

Find Person and Company Information

Search

In Zapier“Finds person and company data and qualification based on an email address.”

Give it an email address and it returns what MadKudu knows about the person behind it, the company they belong to and how well they qualify, ready for the next steps to map.

When to use it
right after a sign-up, so the sheet or the message that follows already says who just raised a hand.
Watch out
the email is the only key it accepts, so a trigger that does not carry one leaves this step with nothing to look up.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a lookup that comes back empty stops the Zap there and the steps that relied on it are skipped. Switch it on and the Zap carries on without the data.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. MadKudu exposes no such variant on Zapier, so its search only ever reads, it never creates.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass every match along at once.
When it breaks

When a MadKudu Zap breaks

Zapier attaches no help article to MadKudu, so the failures worth knowing come from how Zaps work in general.

Four situations explain most surprises. None of them is specific to MadKudu, but each one hits a lookup Zap in its own way. See our Zapier troubleshooting page.

  • Old sign-ups are never looked up

    A Zap only reacts to what happens after it is switched on. The contacts you already had are not scored by it; moving that backlog is a separate job.

  • The Zap feeds itself

    If the last step writes into the same place the trigger watches, each new row sets the Zap off again, and the task count drains fast.

  • A bulk import holds things back

    When the starting app suddenly returns a huge batch after an import or a migration, Zapier's flood protection can hold those items back.

  • The same contact twice

    On a polling trigger, Zapier remembers the items it has already seen, so one submission does not start the Zap a second time.
Need help

Need help automating MadKudu with Zapier?

A person reads every message.

FAQ

MadKudu Zapier integration: your questions

01Is the MadKudu Zapier integration free?
MadKudu itself is not a premium app on Zapier, so the connection works on any plan, including the free one. The catch is structural. The only MadKudu operation is a search, and a Zap that holds a search counts as a multi-step Zap. The free plan only builds two-step Zaps, one trigger and one action. So a working MadKudu lookup, which needs a trigger from another app, the search, and usually a step that uses the result, calls for a paid plan.
02How many tasks does a MadKudu Zap use?
Zapier bills a task each time an action completes successfully. The trigger never costs anything, and Zapier checking the starting app for new items is free as well. In a Zap where a form submission leads to a lookup and then a new spreadsheet row, every successful action is counted on its own, so the more actions you chain after the search, the more each run consumes. An action that fails is not counted against your plan. Some apps and actions take more than one task, so check the steps you add.
03Does MadKudu work in real time with Zapier?
MadKudu has no trigger on Zapier, so the timing never depends on it. It depends on the app that starts the Zap. If that app offers an instant trigger, it reports the event to Zapier the moment it happens. If it is a polling trigger, Zapier checks it at a fixed interval set by your plan: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. Once the Zap runs, the MadKudu search simply executes as one of its steps.
04What does it take to connect MadKudu to Zapier?
Two accounts and a few clicks. You need a MadKudu account that already exists, plus a Zapier account. From the Apps page you click + Add connection, search for MadKudu, confirm with Add connection, sign in to MadKudu in the tab that opens and grant Zapier access. The connection is then reused by every step that calls MadKudu. If you want the Zap to touch anything you do not own yourself, you also need read or write access on it.
05Why does the MadKudu step stop the whole Zap?
Most of the time, because the lookup found nothing and the search is left on its default setting. In that case a search that returns no result stops the Zap at that step, and every step that depended on it is skipped. If you would rather keep going, switch on Successful if no search results are found? in the search settings, and the Zap continues without the data. Also check that the trigger really passes an email address, since it is the only input the search accepts.
06What if the MadKudu operation you need is not on Zapier?
On Zapier, MadKudu offers one lookup by email and nothing else: no event that starts a Zap, no step that writes into MadKudu. If a workflow depends on something else, Zapier cannot add it from the editor; the list is what the app publishes. The practical options are to rebuild the scenario around the lookup, to place the missing part in another app the Zap already uses, or to compare with another automation platform that may expose more of MadKudu.
07Zapier, Make or n8n for MadKudu?
Compare them on criteria, not on a ranking. First, coverage: on Zapier the app offers a single search, so check whether another platform exposes what you need from MadKudu before choosing. Second, cost logic: Zapier counts one task per successful action, and any Zap with a search needs a paid plan. Third, timing: on Zapier, how fast the lookup runs depends on the trigger of the app that starts the Zap, instant or polling. Weigh those three against your volume and your team.
Same platform

Other docs you might need on this stack.

Browse all integrations