Resources · Zapier integration

LEADGODS Zapier integrationAutomate LEADGODS with Zapier.

The LEADGODS Zapier integration gives you 3 triggers, 1 action and 0 searches. New payments, prices and publications can start a Zap (the automation you build on Zapier), and payments can be created from any other app you use.

See the 4 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the LEADGODS Zapier integration does for your sales

LEADGODS is where you sell courses, events, mentorship, webinars and other digital products, and take payment for them. The integration connects it to your other apps without code: Zapier watches for new payments, prices and publications, and it can record a payment in LEADGODS on your behalf.

A sales log that keeps itself. New Payment starts the Zap and a row lands in your spreadsheet for each payment. Your bookkeeping sees every sale without anyone exporting from LEADGODS.

A heads-up when the catalog moves. New Publication and New Price tell another app that something was added for sale, or that a new price exists, so the people who promote your offer hear about it.

Payments recorded from elsewhere. Create Payment writes a payment into LEADGODS from data another app holds, tied to a publication and a price, with the buyer's details.

What Zapier does not do here: there is no search, so a Zap cannot look up a publication or a payment, and there is no action to edit or cancel a payment. Every trigger is polling, so nothing arrives the instant it happens. If those limits weigh on your choice, see our n8n vs Zapier page, or our Zapier agency if you would rather have the team build it. Both stay options, not verdicts.

Vocabulary

Zapier vocabulary in one minute

Seven words carry this page. Here they are in plain English, once.

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 switched on, Zapier waits for that event and nothing else.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you inside an app.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant one is reported by the app itself. All LEADGODS triggers are polling.
Filter
A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it otherwise.
Connection
Your LEADGODS account linked to Zapier once, then reused by every step of every Zap that touches LEADGODS.
Cost

What a LEADGODS Zap really costs

LEADGODS is not a premium app, so it works from the free plan. The triggers never cost a task, however often Zapier checks for new payments, prices or publications.

  • Free plan100 tasks a month, unlimited Zaps
  • Free plan Zaps2 steps: one trigger, one action
  • Premium appNo, LEADGODS runs on the free plan
  • LEADGODS triggers3 polling, 0 instant

Each action that succeeds counts as one task, Create Payment included, and a failed action is not counted. The free plan gives 100 tasks a month and stops at two steps, one trigger and one action. A filter or a second action makes the Zap multi-step, which needs a paid plan. Because the three triggers are polling, your plan also sets how long a new payment can wait before Zapier sees it, as the grid below shows.

Connect

Connect LEADGODS to Zapier in three steps

  1. 01

    Open your apps

    In your Zapier account, go to the Apps page and click + Add connection. A search dialog opens. You need a LEADGODS account first, plus access to anything you do not own and want the Zap to touch.

  2. 02

    Pick LEADGODS

    Type LEADGODS in the dialog, select it, then click Add connection. A new tab opens on the LEADGODS side, and that is where you sign in, not inside the Zapier editor.

  3. 03

    Sign in and allow access

    Log in to LEADGODS in that tab and grant Zapier access to the account. The connection then appears in your apps, and every later Zap reuses it without asking you to sign in again.

First Zap

Your first LEADGODS Zap, step by step

GoalEach new LEADGODS payment that passes a filter is copied into a row of your spreadsheet.

  1. 01

    Create the Zap

    Start a new Zap and pick LEADGODS as the app that starts it. Choose New Payment as the event, then select the connection you added.

  2. 02

    Test the trigger

    Run the test: Zapier brings back the three most recent payments of the account. Pick a real one, because every later step is mapped on what it holds.

  3. 03

    Add the filter

    Click the plus icon and add Filter. In Configure & test, set the field to look at, the rule and the value to compare with. Use a number rule on amounts, a text rule on text.

  4. 04

    Add the action

    Add your spreadsheet as the next step, choose the action that adds a row, and map each column to a value from the payment. Test this step once and read the row it returns.

  5. 05

    Publish

    Click Publish to switch the Zap on. The filter makes it a three-step Zap that needs a paid plan; drop the filter and it fits the free plan.

Triggers

LEADGODS triggers on Zapier

3 events start a Zap when something happens in LEADGODS. Zapier checks for them at the interval your plan allows.

1

New Payment

Polling trigger

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

Every payment created in LEADGODS becomes the start of a Zap, with what was recorded for that sale. It is the trigger that follows your revenue, sale by sale.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
keep a running sales log in your spreadsheet for your bookkeeping.
Watch out
a Zap that answers it with Create Payment makes a payment, which the trigger then picks up again.
2

New Price

Polling trigger

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

Fires when a new price is created in LEADGODS. Since Create Payment always asks for a price, this is the trigger to watch when you add a new way to buy one of your offers.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
let the person who updates your sales pages know a new price is live.
Watch out
it reacts to creation only; editing an existing price does not start it.
3

New Publication

Polling trigger

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

Starts the Zap when a publication is created in LEADGODS, the item a payment refers to. Use it to follow your catalog as it grows, one new publication at a time.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
add each new publication to the list your team uses to plan announcements.
Watch out
publications that existed before the Zap was switched on are never picked up.
Actions

The LEADGODS action

LEADGODS gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Payment

Action

In Zapier“Creates a Payment”

Records a payment in LEADGODS from another app. It asks for the publication type, the publication and its price, then the buyer's email, first name, last name and country code, all required.

When to use it
a sale taken outside LEADGODS should still show up in it.
Watch out
one missing required value in the incoming data and the step fails, without costing a task.
When it breaks

When a LEADGODS Zap breaks

Zapier attaches no help article to LEADGODS and documents no rate limit for it. What goes wrong is what goes wrong on polling triggers in general, plus one loop that is easy to build with this app.

None of these show up as an error inside LEADGODS. You notice a payment that seems late, or a task count that climbs faster than your sales. When the cause is not obvious, our Zapier troubleshooting page is the next stop.

  • The New Payment loop

    New Payment followed by Create Payment writes into what its own trigger watches. Each new payment starts the Zap, which creates another payment, and tasks burn fast.

  • A payment that seems late

    All three triggers are polling: on the free plan, Zapier checks every 15 minutes, so a sale can wait that long. A paid plan shortens the wait, down to every minute.

  • No catch-up on past sales

    A Zap reacts only to what is created after you switch it on. Payments, prices and publications already in LEADGODS are never picked up.

  • The same payment, once only

    Zapier remembers what it has already seen on a polling trigger, so one payment never starts the Zap twice, even if the next check returns it again.
Need help

Need help automating LEADGODS with Zapier?

A person reads every message.

FAQ

LEADGODS and Zapier: common questions

01Is the LEADGODS Zapier integration free?
Yes, within the free plan's limits. LEADGODS is not a premium app, so it works on the free plan, which includes 100 tasks a month and unlimited Zaps. The catch is the shape of the Zap: one trigger and one action, nothing more. New Payment followed by one action in another app fits. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. The free plan also checks polling triggers only every 15 minutes.
02How many tasks does a LEADGODS Zap use?
One task per action that succeeds, each time the Zap runs. The three LEADGODS triggers cost nothing, and neither do Zapier's regular checks for new payments, prices or publications, however often they happen. A Zap that copies each payment into a spreadsheet uses one task per payment. Create Payment also counts as one task when it works. An action that fails, for example because a required field is empty, is not counted against your plan.
03Does LEADGODS trigger Zaps in real time?
No. All three LEADGODS triggers are polling: Zapier asks LEADGODS for new items at a fixed interval that depends on your plan. That is every 15 minutes on Free, every 2 minutes on Professional, and every minute on Team and Enterprise. On paid plans, you can also run a check by hand from the editor. The type is set by the app itself, so no Zapier setting turns these triggers into instant ones.
04What does it take to connect LEADGODS to Zapier?
A LEADGODS account, and access to anything you do not own but want the Zap to touch. From the Apps page of your Zapier account, click + Add connection, search LEADGODS, click Add connection, sign in on the tab that opens and grant access. The connection is saved once and reused by every Zap. If you plan to use Create Payment, check first that your data can fill its seven required boxes.
05Why does a LEADGODS Zap keep creating payments?
Because it probably writes where its own trigger looks. New Payment starts the Zap for every new payment. If the same Zap then runs Create Payment, that new payment is picked up on the next check and starts the Zap again, and so on. Each lap costs a task and adds a payment you did not want. Keep Create Payment in Zaps that start from another app, or put a filter in front that stops the circle.
06What if the LEADGODS action you need does not exist?
Then Zapier cannot do it with LEADGODS today. The editor offers one action, Create Payment, alongside three triggers, and no search. There is no step to edit or cancel a payment, to create a publication or a price, or to look anything up in LEADGODS. Those jobs stay inside LEADGODS. A Zap can still prepare the ground in your other apps, so the manual step takes less time when you do it.
07Zapier, Make or n8n for LEADGODS?
Judge on criteria rather than a ranking. On Zapier, LEADGODS comes with three polling triggers and one action, ready to use without code, billed per successful action. Before choosing, check whether the other platform lists LEADGODS at all, how often it can check for new payments on your budget, and how much setup your team wants to own. Since every trigger here is polling, the check interval you can afford weighs as much as the editor.
Same platform

Other docs you might need on this stack.

Browse all integrations