Resources · Make integration

Push Lap Growth Make integrationAutomate Push Lap Growth with Make.

Can your affiliate program handle its own paperwork? The Push Lap Growth Make integration gives you 22 modules: 9 scheduled triggers, 10 actions and 3 searches. This page shows how to link your account and build a first scenario, one click at a time.

Try the Push Lap Growth integration on MakeSee the 22 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Push Lap Growth Make integration do for you?

It connects your Push Lap Growth account to Make so affiliates, referrals and sales move between your tools on their own. You build a scenario, the automation Make runs for you, out of modules: each module is one brick, such as a trigger that spots a new sale or an action that creates one.

A partner sheet that fills itself. Watch Created Affiliate picks up each affiliate who joins, and the next module writes them into the spreadsheet or CRM your team already opens. Nobody exports a list by hand anymore.

Sales recorded where they happen. When your checkout or billing tool registers a payment, Create a Sale adds it to Push Lap Growth, so the program reflects what customers actually paid.

Edits that reach every tool. Watch Updated Sale or Watch Deleted Referral tell another app that a record changed, and Search Affiliates finds the right partner before Update an Affiliate edits them.

Make's own page on Push Lap Growth warns that its documentation is limited: the modules come without descriptions, and no field, format or limit is published. Test every module with Run once and read what comes back; the Make troubleshooting guide helps when a run fails. To learn the editor from scratch, the Make training starts at the very first scenario, and n8n vs Make lays out how the two tools differ.

Connect

How do you connect Push Lap Growth to Make?

  1. 01

    Add a Push Lap Growth module

    In a scenario, click the + and search for Push Lap Growth. Pick any of its modules, then click Create a connection. A connection is your Push Lap Growth account linked to Make once, and every module of the app reuses it.

  2. 02

    Name it and authorize Make

    Give the connection a name if you want to recognize it later, for example the program it belongs to. Then either approve Make on the Push Lap Growth page that opens, or paste the key the app gives you, depending on what the window asks.

  3. 03

    Save and pick your data

    Click Save. Back in the module, Make can now read your account and offer the objects it finds, so you choose from a list rather than typing identifiers you would have to look up.

First scenario

Your first scenario with Push Lap Growth

GoalWhen your checkout tool records a payment, Make creates the matching sale in Push Lap Growth.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Choose the app where your payments live: it is the one that tells Make a sale happened.

  2. 02

    Add Create a Sale

    Click the + on the right of that first module, search for Push Lap Growth and pick Create a Sale. Click Create a connection if you have not linked your account yet.

  3. 03

    Map the payment data

    Fill the fields of Create a Sale. Make shows the data the first module received, so you drag each value into the matching field instead of typing it. Each payment travels as one bundle.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario a single time and shows, above each module, the bundles it handled. Open Push Lap Growth and confirm the new sale is there.

  5. 05

    Schedule and switch it on

    Open the clock on the first module, which runs every 15 minutes by default, set the rhythm you need and turn the scenario on. Each new payment then becomes a sale without anyone stepping in.

Triggers

What can start a Push Lap Growth scenario?

9 modules start a scenario when something happens in Push Lap Growth. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Push Lap Growth as soon as it happens.

Push Lap Growth1Watch Created Affiliate

Watch Created Affiliate

triggerIn the docs only

Every affiliate who joins your Push Lap Growth program can start a scenario of their own, so a welcome email or a new row in your partner sheet happens without anyone copying names across. Each new affiliate reaches Make as one bundle.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and collects the affiliates added since the previous check.
When to use it
onboarding partners, when the first contact should go out without a manual export.
Watch out
every module after the trigger spends one operation per affiliate, so a wave of signups shows up on your plan.
Push Lap Growth2Watch Created Referral

Watch Created Referral

triggerIn the docs only

Referrals recorded in Push Lap Growth turn into fresh input for your other tools: each new referral lands in the scenario, ready to be sent to a CRM, a chat channel or a spreadsheet. Your sales team sees who came through a partner without opening the dashboard.

How it fires
scheduled. Make asks Push Lap Growth for new referrals at the rhythm set in Scheduling, the clock on the first module.
When to use it
when a lead sent by a partner needs a quick follow-up from someone on your team.
Watch out
nothing documents what a referral bundle contains, so read one after Run once before mapping it downstream.
Push Lap Growth3Watch Created Sale

Watch Created Sale

triggerIn the docs only

New sales are the clearest sign of what your affiliates bring in, and this trigger passes each one to Make when the next check finds it. From there, a scenario can log the sale in your finance tool or ping the person who manages partners.

How it fires
scheduled. Make polls the app on the scenario's schedule; on the Free plan the shortest gap between two checks is 15 minutes.
When to use it
when the revenue a partner generated has to appear somewhere other than Push Lap Growth.
Watch out
a sale created by Create a Sale in another scenario will also be picked up here, which is fine as long as the two scenarios do not feed each other.
Push Lap Growth4Watch Deleted Affiliate

Watch Deleted Affiliate

triggerIn the docs only

Removing a partner from Push Lap Growth rarely ends there: their access, their row in your CRM and their mailing list entry usually need to go too. This trigger notices the deletion and hands the affiliate to Make so the rest of the clean-up follows.

How it fires
scheduled. Make looks for removed affiliates each time the scenario runs, following its schedule.
When to use it
when leaving the program should close every door the affiliate had.
Watch out
the affiliate no longer exists in the app, so do not expect Search Affiliates or Update an Affiliate to find them afterwards; use what the trigger delivered.
Push Lap Growth5Watch Deleted Referral

Watch Deleted Referral

triggerIn the docs only

A referral that disappears from Push Lap Growth can leave a stale lead behind in your CRM or pipeline. With this trigger, Make learns about each deleted referral and lets a following module remove or flag the copy elsewhere.

How it fires
scheduled. On every scheduled run, Make checks Push Lap Growth for referrals that were removed since the last one.
When to use it
keeping your CRM honest when referrals get cleaned out of the program.
Watch out
deleting in your CRM is as final as deleting in Push Lap Growth, so run the scenario once on a test record before switching it on.
Push Lap Growth6Watch Deleted Sale

Watch Deleted Sale

triggerIn the docs only

Cancelled or corrected sales matter as much as new ones when you report on what affiliates earned. This trigger reports each sale removed from Push Lap Growth, so your spreadsheet or accounting tool can drop or mark the same line.

How it fires
scheduled. Make checks the app for deleted sales when the scenario's schedule comes around, never on its own.
When to use it
when a refund or a mistake leads someone to remove a sale and your figures elsewhere must match.
Watch out
the sale is gone from the app by the time Make sees it, so Search Sales will not return it; keep the identifier from the trigger's bundle.
Push Lap Growth7Watch Updated Affiliate

Watch Updated Affiliate

triggerIn the docs only

Partner details change: a new email, a different status, an edited profile. Watch Updated Affiliate sends each changed affiliate to Make, so the copy in your CRM or newsletter tool stays identical to the one in Push Lap Growth.

How it fires
scheduled. Make reads Push Lap Growth at the interval chosen in Scheduling and returns the affiliates modified since the previous run.
When to use it
whenever another tool keeps its own list of your partners.
Watch out
if the same scenario ends with Update an Affiliate, your own edit counts as a change at the next check and the scenario can loop on itself.
Push Lap Growth8Watch Updated Referral

Watch Updated Referral

triggerIn the docs only

Referrals move forward over time, and this trigger lets Make follow them: each referral edited in Push Lap Growth comes back as a bundle you can push to the deal or task that tracks it elsewhere.

How it fires
scheduled. Make queries the app on the scenario's schedule, every 15 minutes unless you change it, and catches the referrals modified in between.
When to use it
when your sales team works from a CRM and needs to see a referral's progress there.
Watch out
the documentation does not say which edits count as an update, so change a test referral and check with Run once what arrives.
Push Lap Growth9Watch Updated Sale

Watch Updated Sale

triggerIn the docs only

When a sale changes in Push Lap Growth, the numbers in your reporting sheet should change with it. This trigger delivers each modified sale to Make, ready for a module that rewrites the matching line in another app.

How it fires
scheduled. Make checks Push Lap Growth each time the schedule on the first module comes due, not the moment the edit happens.
When to use it
keeping a finance or reporting tool in line with sale corrections made in the program.
Watch out
pairing it with Update a Sale in the same scenario can trigger a loop, since your update is itself a change the next check will see.
Modules

What else can Make do in Push Lap Growth?

Push Lap Growth gives you 13 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Push Lap Growth1

Create a Referral

ActionIn the docs only

Registers a referral in Push Lap Growth from data another tool collected, such as a form answer or a new CRM contact, so the partner who sent that person gets the credit.

When to use it
when leads reach you outside the program's own tracking and still need to count for an affiliate.
Watch out
run it once on a test contact, since the fields it expects are not documented.
Push Lap Growth2

Create a Sale

ActionIn the docs only

Adds a sale to Push Lap Growth from a payment recorded elsewhere, which keeps the program's figures tied to what your billing tool actually collected.

When to use it
right after a checkout or invoice module, when payments do not reach Push Lap Growth by themselves.
Watch out
a Watch Created Sale scenario will see these sales too; make sure it does not send them back here.
Push Lap Growth3

Create an Affiliate

ActionIn the docs only

Opens a new affiliate account in Push Lap Growth from someone who applied through another channel, so partners signed up in a form or a CRM join the program without retyping.

When to use it
after an application form, once the person is approved on your side.
Watch out
put Search Affiliates before it if the same person might apply twice, or you may end up with duplicates.
Push Lap Growth4

Delete a Referral

ActionIn the docs only

Removes a referral from Push Lap Growth, which helps when a test entry, a duplicate or a lead flagged elsewhere as invalid should not count for an affiliate.

When to use it
as the last step of a clean-up scenario, after Search Referrals found the exact record.
Watch out
a deletion cannot be undone from Make, so filter carefully before this module runs on every bundle.
Push Lap Growth5

Delete a Sale

ActionIn the docs only

Takes a sale out of Push Lap Growth, for example when the matching order was cancelled in your shop, so the affiliate's results stop including revenue that never came in.

When to use it
when a refund or cancellation in another tool should cancel the sale in the program too.
Watch out
Make cannot bring the sale back afterwards; test on a dummy sale first.
Push Lap Growth6

Delete an Affiliate

ActionIn the docs only

Deletes an affiliate from Push Lap Growth, which closes the loop when a partnership ends in your contract or CRM tool and the account should disappear from the program as well.

When to use it
offboarding, once everything the affiliate is owed has been handled.
Watch out
it is final, and a Watch Deleted Affiliate scenario will react to it, so check both scenarios together.
Push Lap Growth7

Make an API Call

ActionIn the docs only

Reaches any endpoint of the Push Lap Growth API with the connection you already set up, which covers whatever the dedicated modules of this page leave out, such as a request none of them offers.

When to use it
when the operation you need has no dedicated module in this list.
Watch out
you have to know the endpoint and its parameters yourself, and Make's documentation for this app gives none, so look in Push Lap Growth's own material.
Push Lap Growth8

Search Affiliates

SearchIn the docs only

Looks up affiliates in Push Lap Growth and returns the ones that match, which is how a scenario finds the partner to update, credit or notify.

When to use it
before Update an Affiliate or Create an Affiliate, when you only know something like a name or email from another tool.
Watch out
a search can return zero, one or several bundles, and each one runs the modules that follow.
Push Lap Growth9

Search Referrals

SearchIn the docs only

Finds referrals already stored in Push Lap Growth, handy for checking whether a lead is known before creating it again or for pulling the list behind a report.

When to use it
in front of Create a Referral to avoid duplicates, or before Update a Referral to get the right record.
Watch out
when nothing matches, the modules after it do not run at all, which can look like a silent failure.
Push Lap Growth10

Search Sales

SearchIn the docs only

Returns the sales in Push Lap Growth that match what you look for, which gives a reporting scenario the raw lines it needs or an update scenario the sale to fix.

When to use it
when a sheet or dashboard should list sales, or before Update a Sale or Delete a Sale.
Watch out
many results mean many bundles and as many operations for each module downstream.
Push Lap Growth11

Update a Referral

ActionIn the docs only

Edits a referral that already exists in Push Lap Growth, so progress recorded in your CRM, such as a lead that turned into a customer, shows up in the program as well.

When to use it
when the stage of a lead changes in the tool your sales team works in.
Watch out
avoid running it in a scenario started by Watch Updated Referral, or each edit will start the scenario again.
Push Lap Growth12

Update a Sale

ActionIn the docs only

Corrects a sale already in Push Lap Growth, for instance after a partial refund in your billing tool, so the affiliate's results match the amount you really kept.

When to use it
when an order changes after the sale was recorded and deleting it would be too drastic.
Watch out
the module needs the right sale, so place Search Sales before it when the identifier is not in the bundle.
Push Lap Growth13

Update an Affiliate

ActionIn the docs only

Changes the details of an existing affiliate in Push Lap Growth from another source of truth, like your CRM or partner contract tool, so nobody has to edit the same profile twice.

When to use it
when a partner's contact details or status change outside the program.
Watch out
without Search Affiliates first, the scenario may not know which affiliate to edit.
Need help

Need help automating Push Lap Growth with Make?

A person reads every message.

FAQ

Push Lap Growth and Make: common questions

01Is the Push Lap Growth Make integration free?
Yes, you can start for free. Push Lap Growth is a standard app in Make, available from the Free plan. That plan keeps 2 scenarios active, runs scheduled scenarios no more often than every 15 minutes, stops an execution after 5 minutes and allows 512 MB of data transfer with files up to 5 MB. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes per execution. Usage is counted in credits, which track operations. What Push Lap Growth itself charges is outside the scope of this page.
02What do you need to connect Push Lap Growth to Make?
A Push Lap Growth account and a Make account, since the documentation lists no other prerequisite. Add any Push Lap Growth module to a scenario, click Create a connection, name the connection if you like, then either authorize Make on the Push Lap Growth page or paste the key the app gives you, and click Save. The documentation does not say which of those two methods this app uses, so follow what the window shows. Once saved, the connection serves all 22 modules of the app.
03Do Push Lap Growth triggers in Make fire instantly?
No. The 9 Push Lap Growth triggers are listed as scheduled: Make checks the app on the scenario's schedule instead of waiting for Push Lap Growth to call it. A new scenario checks every 15 minutes by default; the Free plan cannot go below 15 minutes, while paid plans go down to 1 minute. The documentation describes none of these triggers and their type follows from their Watch names, so look for the clock badge when you add one. None of them is instant, so no webhook from Push Lap Growth is on offer here.
04What if a Push Lap Growth module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Push Lap Growth API with the connection you already created, so an operation the listed modules skip stays within reach. You will need the endpoint and its parameters, and Make states that its documentation for this app is limited because little public information exists about Push Lap Growth. Look in the app's own material for them. If the limit comes from Make instead, such as the 5 minutes per execution on the Free plan, a paid plan raises it to 40 minutes.
05Should you use Make or n8n for Push Lap Growth?
It depends on what you plan to build. On Make, Push Lap Growth comes with 22 ready modules covering affiliates, referrals and sales: 9 scheduled triggers, 10 actions and 3 searches, and you can start on the Free plan. This page does not check whether n8n has a Push Lap Growth node, so verify that before comparing. If both tools cover the records you work with, compare them on the exact scenarios you need rather than in general, and read the n8n vs Make comparison mentioned earlier on this page.
Same platform

Other docs you might need on this stack.

Browse all integrations