Resources · Make integration

ChargeKeep Make integrationAutomate ChargeKeep with Make.

Want new ChargeKeep payments and leads to update your other tools on their own? The ChargeKeep Make integration gives you 10 modules: 3 triggers and 7 actions. This guide shows how to link your account and build a first scenario, step by step.

Try the ChargeKeep integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the ChargeKeep Make integration do for you?

The ChargeKeep Make integration links your ChargeKeep account to Make, a visual tool where you build a scenario (the automation itself, a chain of blocks). Each block is a module: here, 3 of them watch ChargeKeep for new leads, payments and subscription events, and 7 act on contacts, subscriptions, products and invoices.

Every new lead lands in your CRM. Watch New Lead picks up leads recorded in ChargeKeep, and the next module sends them wherever your sales team works. Sales reps stop copying names by hand.

A payment gets its invoice. Pair Watch New Payment with Create an Invoice, and each payment ChargeKeep records can lead to a matching invoice without anyone opening the dashboard.

Subscription changes reach the right people. Watch New Subscription Events catches changes on subscriptions; a finance or support tool further down the scenario can react to them.

Know the limits before you start. Make's own documentation for ChargeKeep is limited because little public information exists about the app, so field details are best discovered inside the module itself. When a listed module falls short, Make an API Call reaches the rest of the ChargeKeep API with the same connection. If you are weighing tools, the n8n vs Make comparison lays out the differences, and Make training helps you go further. Stuck on an error? See Make troubleshooting.

Connect

How do you connect ChargeKeep to Make?

  1. 01

    Add a ChargeKeep module

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

  2. 02

    Name the connection

    Giving the connection a name is optional, yet useful when you manage several ChargeKeep accounts, such as a test account and a live one. A clear name saves you from picking the wrong account later in a busy scenario.

  3. 03

    Authorize Make and save

    Follow what the window asks: either approve Make on the ChargeKeep page that opens, or paste the key ChargeKeep gives you. Then click Save, and the module can now read your ChargeKeep data.

First scenario

Build your first scenario with ChargeKeep

GoalWhen ChargeKeep records a new payment, Make creates an invoice for it in ChargeKeep.

  1. 01

    Create the scenario

    Open the Scenarios page in Make and create a new scenario. An empty canvas appears with a single + in the middle: that is where your first module goes.

  2. 02

    Add the payment trigger

    Click the +, search for ChargeKeep and choose Watch New Payment. Click Create a connection to link your account, or pick the connection you already made.

  3. 03

    Add the invoice action

    Click the + on the right of the trigger and pick Create an Invoice. Fill its fields by mapping data from the payment, so each invoice carries the details of the payment that started it.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received (a bundle is one item passing between modules, here one payment). Check that the invoice looks right.

  5. 05

    Schedule and switch it on

    Click the clock on the first module to set the schedule; a new scenario runs every 15 minutes by default, and the Free plan allows no shorter interval. Then switch the scenario on.

Triggers

What starts a ChargeKeep scenario?

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

ChargeKeep1Watch New Lead

Watch New Lead

triggerIn the docs only

Watch New Lead hands your scenario each lead that ChargeKeep records, so a prospect never sits unseen in one tool while your team works in another. Every lead arrives as its own bundle for the next module.

How it fires
scheduled. Make checks the app on the scenario's schedule, going by the module's name and its listing in the doc, and picks up new leads since its last check.
When to use it
when a fresh lead should become a contact in your CRM or a message to a salesperson.
Watch out
each check and each lead processed count as operations, the unit Make charges against your plan.
ChargeKeep2Watch New Payment

Watch New Payment

triggerIn the docs only

With Watch New Payment, money that comes in through ChargeKeep can set off the rest of your process: an invoice, a thank-you email, a line in a finance sheet. Each payment becomes one bundle.

How it fires
scheduled. Make checks the app on the scenario's schedule (as the module's name and its doc listing suggest), so a payment shows up at the next check rather than the moment it happens.
When to use it
when a confirmed payment should lead to paperwork or a notification without anyone watching the dashboard.
Watch out
on the Free plan, Make checks no more often than every 15 minutes, so plan for that delay.
ChargeKeep3Watch New Subscription Events

Watch New Subscription Events

triggerIn the docs only

This trigger feeds your scenario the events ChargeKeep logs on subscriptions, so changes to recurring customers do not go unnoticed. Unlike Watch New Payment, it follows the life of a subscription rather than single charges.

How it fires
scheduled. Make checks the app on the scenario's schedule, based on the module's name and its doc listing, and collects events since the previous check.
When to use it
when support or finance must hear about a subscription change.
Watch out
the doc does not list which events count, so run the scenario once and read the bundles before you build filters on them.
Modules

What can Make do in ChargeKeep?

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

ChargeKeep1

Add a Contact

ActionIn the docs only

Add a Contact puts a new person into ChargeKeep from any other app in your scenario, so customer records start in the right place without retyping.

When to use it
a form or a CRM sends you a new buyer who should exist in ChargeKeep before any billing happens.
Watch out
the doc says nothing about duplicate handling, so test with Run once on a contact that already exists before you activate the scenario.
ChargeKeep2

Add a Subscription

ActionIn the docs only

This action opens a subscription in ChargeKeep straight from your scenario, which keeps recurring billing in step with a sale closed elsewhere.

When to use it
right after a deal is signed in another tool and the customer should start on a plan.
Watch out
the doc gives no detail on the fields this module expects, so open it in the editor and read what Make asks for before mapping anything.
ChargeKeep3

Create a Product

ActionIn the docs only

Create a Product adds an item to your ChargeKeep catalog without opening the app, which helps when your offer is managed in a spreadsheet or another system.

When to use it
a new offer is approved in your internal tool and should be ready to sell in ChargeKeep.
Watch out
test with Run once before switching the scenario on, since each new run can add the same product again.
ChargeKeep4

Create an Invoice

ActionIn the docs only

Here the scenario produces a ChargeKeep invoice for you, filled with data mapped from earlier modules, so billing no longer waits for someone to find time.

When to use it
paired with Watch New Payment, or after an order arrives from your shop or your quoting tool.
Watch out
an invoice goes to a customer, so check the mapped amounts in the bundles of a Run once test before you activate.
ChargeKeep5

Get a Contact Details

ActionIn the docs only

Get a Contact Details reads one contact from ChargeKeep and hands its data to the next module, so an email or a report can use up-to-date customer information.

When to use it
a trigger gives you a payment or an event, and the following step needs the person behind it.
Watch out
it is listed as an action that works on one contact, so it will not hand you a whole list to loop through.
ChargeKeep6

Make an API Call

ActionIn the docs only

Make an API Call is your way out when none of the listed modules does what you need: it calls any endpoint of the ChargeKeep API while reusing your existing connection.

When to use it
you need a ChargeKeep feature that has no module here, and the listed modules stop short.
Watch out
you write the request yourself, so keep the ChargeKeep API reference open, since Make's doc for this app stays thin.
ChargeKeep7

Update a Contact

ActionIn the docs only

Update a Contact changes an existing ChargeKeep contact, so a new address or company name entered elsewhere reaches your billing records too.

When to use it
a customer edits their profile in your CRM or support tool and ChargeKeep should follow.
Watch out
you need to point to the right contact, so pair it with Get a Contact Details or with an ID taken from a trigger before overwriting anything.
Need help

Need help automating ChargeKeep with Make?

A person reads every message.

FAQ

ChargeKeep and Make: common questions

01Is the ChargeKeep Make integration free?
Yes, ChargeKeep is a standard app in Make, so you can use it on the Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Make counts usage in credits, one per operation, each month.
02What do you need to connect ChargeKeep to Make?
You need a ChargeKeep account and a Make account. Make's documentation lists no special prerequisite for ChargeKeep and gives no app-specific steps, so the usual path applies. Add any ChargeKeep module, click Create a connection, name it if you want, then approve Make on the ChargeKeep page or paste the key ChargeKeep gives you, depending on what the window asks. Click Save and every ChargeKeep module in your scenarios can reuse that connection.
03Do ChargeKeep triggers in Make fire instantly?
No. All 3 ChargeKeep triggers work as scheduled triggers, going by their names and the doc listing. Make checks ChargeKeep on the scenario's schedule and collects new leads, payments or subscription events since the last check. A new scenario runs every 15 minutes by default; on the Free plan that is also the shortest interval, while paid plans go down to 1 minute. The clock badge on the module marks it as scheduled.
04What if the ChargeKeep module you need is missing in Make?
Use Make an API Call. It is one of the 10 ChargeKeep modules and lets your scenario call any endpoint of the ChargeKeep API with the connection you already set up. That covers whatever the 7 listed actions leave out, without a second connection. Keep in mind that Make's own documentation for ChargeKeep is limited, because little public information exists about the app, so the ChargeKeep API reference will guide the request.
05Should you use Make or n8n for ChargeKeep?
It depends on what you need, and this page can only speak for Make. On Make, ChargeKeep comes with 10 ready modules, 3 scheduled triggers and 7 actions, plus Make an API Call for anything missing, and it works from the Free plan. Many apps also have an n8n node, but this guide cannot confirm one for ChargeKeep. Check the n8n node list first, then compare how each tool fits the scenarios you plan to build.
Same platform

Other docs you might need on this stack.

Browse all integrations