Resources · Zapier integration

leadtributor.cloud Zapier integrationAutomate leadtributor.cloud with Zapier.

The leadtributor.cloud Zapier integration gives you 8 triggers, 9 actions and 4 searches. Every trigger is instant, so new leads, closed leads and partner changes reach your Zap straight away. Here is what each step does, what it costs and the partner rules that trip people.

See the 21 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the leadtributor.cloud Zapier integration is for

leadtributor.cloud is B2B software for companies that sell through distribution partners: it routes leads to those partners and lets you follow the forecast with them. Connected to Zapier, it can start an automation when a lead or a partnership changes, and it can create leads, hand them to partners and manage partner records from your other apps.

Three outcomes people build first. Leads that reach a partner without a manual step: LeadCreated fires and Offer Lead puts the lead on a market, where your distribution rules pick the partners. A closing report outside the platform: LeadClosed starts the Zap, Get Lead pulls the prospect's contact data and interest fields, and a spreadsheet keeps the record. A partner list that stays tidy: SalesPartnerInvitationAccepted and SalesPartnerEnded tell your other tools who joined and who left.

What the integration does not do. There is no action to edit or delete a lead once it exists, and leads created through Zapier always use the company's default form. Partner deletion only works on partners whose status is ENDED, PENDING or DECLINED, and the end customer rating only works when that option is switched on in the partner settings. And no Zap catches up on events that happened before you published it.

The upside is speed: all eight triggers are instant, so the interval grid of the free plan does not slow anything down. For a wider look at the tool, read the Zapier review; if you would rather have the partner flows built for you, see the Zapier agency page.

Vocabulary

Zapier vocabulary in one minute

Eight terms come back throughout this page. Here they are, in everyday words.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for that event and reacts to nothing else.
Action
What the Zap does once it has started: the step that creates, sends or changes something for you in an app.
Task
The unit Zapier bills: one action that completes successfully. Your plan's allowance is simply a count of those.
Polling vs instant
Polling: Zapier asks the app for news on a timer. Instant: the app calls Zapier itself the moment the event happens.
Filter
A step that lets the Zap continue only when the incoming data meets a condition you set, and stops it otherwise.
Search step
A step that looks up something already in an app, such as a lead or a partner, so later steps can use what it found.
Multi-step Zap
Any Zap beyond one trigger and one action. A filter, a search or a second action turns it into one, and it needs a paid plan.
Cost

What a leadtributor.cloud Zap costs

leadtributor.cloud is not a premium app, so it works on the free plan. Only the actions that succeed after the trigger use tasks.

  • Premium appNo, works on the free plan
  • Free plan100 tasks a month, two-step Zaps
  • Trigger cost0 tasks
  • leadtributor.cloud triggersAll 8 instant, no waiting interval

The trigger never costs a task, and neither does Zapier waiting for leadtributor.cloud to call. Each action that succeeds counts as one task; an action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps per Zap: one trigger, one action. LeadCreated followed by Offer Lead fits. Add Get Lead, a filter or a second action and the Zap becomes multi-step, which needs a paid plan. The interval grid below only concerns polling triggers; leadtributor.cloud has none.

Connect

Connect leadtributor.cloud to Zapier

  1. 01

    Go to Apps

    In your Zapier account, open Apps and click + Add connection. A connection is your leadtributor.cloud account linked once, then reused by every Zap that works with it.

  2. 02

    Pick leadtributor.cloud

    Search for leadtributor.cloud in the dialog, select it and click Add connection. A new browser tab then opens on the leadtributor.cloud side to finish the link.

  3. 03

    Sign in and grant access

    Log in to leadtributor.cloud in that tab and allow Zapier into the account. You need your own account, plus access to any leads or partner records owned by others that the Zap should touch.

First Zap

Your first leadtributor.cloud Zap

GoalCopy the contact data of every closed lead into a reporting spreadsheet

  1. 01

    Build: the trigger

    Create a Zap, choose leadtributor.cloud as the app and LeadClosed as the event, then select the leadtributor.cloud connection you just added.

  2. 02

    Test on a real lead

    Run the test. Zapier brings back the three most recent closed leads from your account, so you map fields on real data instead of an empty template.

  3. 03

    Add the search

    Click the plus icon and pick Get Lead under SEARCH. Map the lead ID that the trigger returned: it is the one required field, and it unlocks the contact data.

  4. 04

    Add the spreadsheet

    Add your spreadsheet as the action, choose the event that adds a row, and map the contact data and interest fields to their columns. Test it once and read what came back.

  5. 05

    Publish

    Click Publish to switch the Zap on. With a search in the middle, this is a multi-step Zap, so it runs on a paid plan only.

Triggers

leadtributor.cloud triggers

8 events start a Zap when something happens in leadtributor.cloud, and 8 of them are instant: the app calls Zapier straight away, whatever your plan.

1

BrokerageFailed

Instant trigger

In Zapier“Triggers when a brokerage fails.”

Starts the Zap when a brokerage fails (a brokerage being what Offer Lead starts on a market), and passes that failed brokerage on to the next steps.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a lead that no partner picked up should land in front of someone on your side quickly, before it goes cold.
Watch out
if the same Zap offers the lead again on that market, a second failure can restart it in a loop.
2

LeadAssignedDirectly

Instant trigger

In Zapier“Triggers when a lead was assigned directly.”

Fires when a lead is assigned straight to a partner, without going through a market, and hands that assignment to the next steps.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
direct assignments should be logged or announced somewhere your team looks, so nobody loses track of who got which lead.
Watch out
an Assign Lead to Partner step inside the same Zap would set this trigger off again.
3

LeadClosed

Instant trigger

In Zapier“Triggers when a lead is closed.”

Goes off when a lead is closed in leadtributor.cloud, which makes it the natural starting point for any report on finished leads.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
every closed lead should leave a trace in a spreadsheet or another tool used for reporting.
Watch out
leads closed before the Zap was published are not sent; the report only starts on the day you switch it on.
4

LeadCreated

Instant trigger

In Zapier“Triggers when a new lead is created.”

Runs as soon as a new lead is created in leadtributor.cloud, and carries it into the Zap so the following steps can route or record it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
each new lead should go on a market or get a duplicate check before anyone works on it.
Watch out
a Create Lead step in the same Zap creates a lead, which fires this trigger again and can loop.
5

LeadDeleted

Instant trigger

In Zapier“Triggers when a lead is deleted.”

Reacts when a lead is deleted, so the tools that kept a copy of it can learn that it is gone.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a spreadsheet or another tool mirrors your leads, and deleted ones should be flagged there too.
Watch out
the lead no longer exists afterwards, so a Get Lead step placed after this trigger has nothing left to fetch.
6

LeadOfferAccepted

Instant trigger

In Zapier“Triggers when a lead offer is accepted.”

Reports the moment a partner accepts a lead offered on a market, and passes the accepted offer to the next steps of the Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your team wants to know which partner took which lead, the moment the offer is taken.
Watch out
offers accepted before publishing are not replayed, so test it with a fresh offer once the Zap is on.
7

SalesPartnerEnded

Instant trigger

In Zapier“Triggers when a sales partnership has ended.”

Kicks in once a sales partnership has ended, and carries that partner's details along to the next steps.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a partner who leaves should disappear from the lists and tools where your team still sees them.
Watch out
an End Sales Partner Relationship step in the same Zap ends a partnership too, and fires this trigger once more.
8

SalesPartnerInvitationAccepted

Instant trigger

In Zapier“Triggers when a salespartner has accepted your invitation.”

Wakes the Zap up as soon as a sales partner accepts the invitation you sent, and hands the new partner to the following steps.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
each new partner should be added to your partner sheet or tagged right away, without anyone watching the inbox.
Watch out
invitations accepted before the Zap was published never come through; only new acceptances count.
Actions

leadtributor.cloud actions

leadtributor.cloud gives you 9 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Note to Lead

Action

In Zapier“Adds a note to the journal of a lead.”

Writes a note in a lead's journal, either shared beyond your company or kept internal to it.

When to use it
something learned in another tool belongs in the lead's history where everyone handling it can read it.
Watch out
the lead ID and the text are required; tick Internal when the note must stay on your side.
2

Assign Lead to Partner

Action

In Zapier“Assign a lead to a partner. It results in a direct commission to the given partner using the provided sales pipeline (or using the default if left empty).”

Hands a lead to one named partner, which creates a direct commission through the sales pipeline you give, or the default one.

When to use it
you already know which partner should get this lead and a market would only slow things down.
Watch out
both the lead ID and the partner ID are required, and a Zap built on LeadAssignedDirectly may then run.
3

Create Lead

Action

In Zapier“Creates a new lead using the default form of the company.”

Creates a new lead in leadtributor.cloud through the company's default form.

When to use it
requests collected in another tool should enter the partner process without being typed in again.
Watch out
the default form is always used, so the fields you can fill are the ones that form holds.
4

Delete Sales Partner

Action

In Zapier“Permanently removes a sales partner record. Only allowed when the partner status is ENDED, PENDING, or DECLINED.”

Removes a sales partner record for good.

When to use it
cleaning out partners who never joined or whose relationship is over, so the list stays readable.
Watch out
it only works when the partner status is ENDED, PENDING or DECLINED; an active partner has to be ended first.
5

End Sales Partner Relationship

Action

In Zapier“Ends an active sales partner relationship. The partner status changes to ENDED.”

Ends an active sales partner relationship and switches the partner's status to ENDED.

When to use it
a decision recorded in another tool should close the partnership on the platform too.
Watch out
the partner ID is required, and a Zap built on SalesPartnerEnded may then run.
6

Invite Sales Partner

Action

In Zapier“Sends an email invitation to a potential sales partner.”

Sends an email invitation to someone you want as a sales partner.

When to use it
a form or a list in another tool collects candidate partners and each one should get an invitation automatically.
Watch out
the email address is required; the partnership only starts once the person accepts, which the invitation trigger then reports.
7

Offer Lead

Action

In Zapier“Offer a lead on a market. It results in a brokerage which offers the lead to possible sales partners according to the distribution rules configured on the market.”

Puts a lead on a market, which starts a brokerage: the lead is offered to possible partners following that market's distribution rules.

When to use it
new leads should reach the partner network without anyone choosing a partner by hand.
Watch out
the market ID and the lead ID are both required, so the market must already exist.
8

Submit End Customer Rating

Action

In Zapier“Submits or updates the rating an end customer gives for the sales partner who processed their lead. Requires the end customer rating to be enabled in the sales partner settings.”

Records or updates the rating an end customer gives the partner who processed their lead, from 1 star (worst) to 5 (best).

When to use it
feedback collected in another tool should feed partner ratings back into leadtributor.cloud.
Watch out
it needs the commission ID and the stars, and fails unless end customer rating is enabled in the partner settings.
9

Update Sales Partner

Action

In Zapier“Updates the tags and attributes of a sales partner.”

Changes the tags and attributes of an existing sales partner record.

When to use it
information about a partner changes in another tool and the partner record should follow.
Watch out
the partner ID is required; put a List Sales Partners or Get Sales Partner step first when you do not have it.
Searches

leadtributor.cloud searches

4 search steps look for data that already exists in leadtributor.cloud, so a later step can use it.

A search step reads a lead or a partner already in leadtributor.cloud and hands it to the next steps. In the editor, the four searches sit at the bottom of the Action event list, under SEARCH. None of them has a find-or-create variant.

1

Get Lead

Search

In Zapier“Gets a lead by ID, including the contact data of the prospect and the interest fields.”

Fetches a lead by its ID, with the prospect's contact data and the interest fields, so later steps get the whole record.

When to use it
right after LeadClosed, to send the full lead to a report.
Watch out
the lead ID is required, typically taken from a lead trigger.
2

Get Lead Duplicates

Search

In Zapier“Returns a list of potential duplicate leads for a given lead, each with a confidence score and the matching criteria that triggered duplicate detection.”

Returns the leads that might duplicate a given one, each with a confidence score and the criteria that matched.

When to use it
before offering a fresh lead, to spot the ones already in the system.
Watch out
several results are normal here; set the multiple-results option to pass them all if you need the full list.
3

Get Sales Partner

Search

In Zapier“Gets a sales partner by ID.”

Pulls one sales partner record from its ID, so later steps can use the partner's details.

When to use it
an earlier step hands you a partner ID, and the next step needs more than that number.
Watch out
the partner ID is required and must come from an earlier step.
4

List Sales Partners

Search

In Zapier“Returns a list of your sales partners, optionally filtered by status.”

Returns your sales partners, and can narrow the list down to one status.

When to use it
you need to pick partners in a given status, such as ended ones before a clean-up with Delete Sales Partner.
Watch out
by default only the first match goes on; choose to pass all of them when the whole list matters.

The three settings every search exposes

  1. Successful if no search results are found?
    On its default, a search that finds nothing stops the Zap there and the steps that depend on it are skipped. Switch it on and the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. No leadtributor.cloud search offers it, so a missing lead is created with Create Lead instead.
  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 all of them on at once.
When it breaks

When a leadtributor.cloud Zap breaks

Zapier links no help article to leadtributor.cloud. The cases below mix the general failures of any Zap with the conditions the app sets on some of its own actions.

Most of them fail quietly: the Zap stops at one step, or runs more than planned. If something still looks wrong after these checks, the Zapier troubleshooting guide takes over.

  • Past leads never arrive

    A Zap only reacts to what happens after you switch it on. Leads and partner changes from before stay where they are; moving them is a separate job.

  • The Zap that sets itself off

    Create Lead under LeadCreated, or End Sales Partner Relationship under SalesPartnerEnded: a Zap writing where its trigger watches loops and burns tasks.

  • A bulk import held back

    When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold it back.

  • Deleting an active partner

    Delete Sales Partner refuses any partner whose status is not ENDED, PENDING or DECLINED. End the relationship first, then delete.

  • Rating switched off

    Submit End Customer Rating fails as long as end customer rating is not enabled in the sales partner settings of leadtributor.cloud.

  • A missing ID

    Most actions want a lead, partner, market or commission ID. Map each one from the trigger or from a search placed earlier in the Zap.
Need help

Need help automating leadtributor.cloud with Zapier?

A person reads every message.

FAQ

leadtributor.cloud Zapier integration: common questions

01Is the leadtributor.cloud Zapier integration free?
Yes. leadtributor.cloud is not a premium app, so it runs on Zapier's free plan, which gives 100 tasks a month and unlimited Zaps. The limit people miss is the two-step rule: on the free plan, a Zap holds one trigger and one action, nothing more. LeadCreated followed by Offer Lead fits. Add Get Lead, a filter or a second action and the Zap turns multi-step, which needs a paid plan.
02How many tasks does a leadtributor.cloud Zap use?
One task for each action that succeeds, and nothing for the trigger. A Zap that offers every new lead on a market spends one task per lead. If it also adds a note to the lead, it spends two. Actions that fail, such as a rating submitted while the option is off, are not counted. Zapier waiting for leadtributor.cloud to report an event costs nothing at all, and a few apps or actions take more than one task.
03Is leadtributor.cloud real time on Zapier?
Yes, for all eight triggers. leadtributor.cloud tells Zapier the moment a lead is created, assigned, closed or deleted, an offer is accepted, a brokerage fails or a partnership starts or ends, and the Zap runs at once. The polling interval grid of the plans does not apply, so the free plan reacts as fast as Enterprise here. The type is set on the app's side and cannot be changed in the editor, where these Zaps show a lightning bolt.
04What does it take to connect leadtributor.cloud to Zapier?
Your own leadtributor.cloud account, plus access to any leads or partner records owned by others that the Zap should touch. In Zapier, open Apps, click + Add connection, search for leadtributor.cloud and confirm with Add connection, then sign in in the new tab and grant access. Before building, check the settings your steps depend on: a market for Offer Lead, and end customer rating switched on if you plan to submit ratings.
05Why does Delete Sales Partner fail on some partners?
Because leadtributor.cloud only allows it when the partner's status is ENDED, PENDING or DECLINED. An active partner cannot be deleted directly. The way through is two steps: End Sales Partner Relationship first, which switches the status to ENDED, then Delete Sales Partner. Keep in mind that ending the relationship can also set off any Zap built on the SalesPartnerEnded trigger. Deletion is permanent, so test it on a single partner first.
06What if the leadtributor.cloud action you need is not there?
Then the integration does not cover it as it stands. Zapier offers nine leadtributor.cloud actions, from creating and offering leads to inviting, updating, ending and deleting partners, plus four searches that only read. There is no step to edit or delete a lead, for example. A filter or a search can reshape what reaches those actions, but it cannot add a new one. For anything beyond the list, the request has to go to leadtributor.cloud or run another way.
07Zapier, Make or n8n for leadtributor.cloud?
It comes down to your criteria, not a ranking. Zapier is quick to learn, and with eight instant triggers even the free plan reacts at once, as long as each Zap stays at two steps. Partner flows often need a search before an action, though, and that makes them multi-step, so the paid plan and the task count become the real cost. Make and n8n bill and chain steps differently, so compare them on your volume and the steps you need.
Same platform

Other docs you might need on this stack.

Browse all integrations