Resources · Make integration

Upgrade.Chat Make integrationAutomate Upgrade.Chat with Make.

Want new Upgrade.Chat payments to kick off the next step on their own? The Upgrade.Chat Make integration gives you 3 triggers and 7 actions. This guide walks you through linking your account, building a first scenario and picking the right module.

Try the Upgrade.Chat integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Upgrade.Chat Make integration do for you?

The Upgrade.Chat Make integration links your Upgrade.Chat account to Make, a no-code tool where you build a scenario (the automation itself, a chain of bricks called modules). Upgrade.Chat can start that chain when a lead, a payment or a subscription event shows up, and it can receive contacts, products, subscriptions and invoices sent by other apps.

An invoice for every payment. Watch New Payment picks up each new payment, and Create an Invoice produces the matching invoice. Nobody has to copy amounts by hand after a sale.

A clean contact list. When a signup form in another app collects someone, Add a Contact records them in Upgrade.Chat. If the person already exists, Get a Contact Details reads their record first and Update a Contact corrects it.

A follow-up on subscriptions. Watch New Subscription Events hands each event to the rest of the scenario, for example to alert a teammate or log it in a spreadsheet app. Watch New Lead plays the same role for fresh leads.

One honest limit: Make's own documentation for Upgrade.Chat is thin. It lists the module names but gives no description and no field details, so expect to discover the fields inside the editor. For anything the listed modules skip, Make an API Call reaches the rest of the Upgrade.Chat API with the same connection. If you are still deciding on a platform, the Make review and the n8n vs Make comparison lay out the options, and Make troubleshooting helps when a run fails.

Connect

How do you connect Upgrade.Chat to Make?

  1. 01

    Add an Upgrade.Chat module

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

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, such as the store or community it serves. Then either approve Make on the Upgrade.Chat page that opens, or paste the key Upgrade.Chat gives you, depending on what the window asks for.

  3. 03

    Save and check the fields

    Click Save. Back in the module, Make can now read your Upgrade.Chat data and offer the objects it finds. If the module still shows an error, reopen the connection and redo the authorization step.

First scenario

Your first scenario with Upgrade.Chat

GoalWhen a new payment lands in Upgrade.Chat, Make creates the matching invoice.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. This first module is the trigger, the brick that decides when everything else runs.

  2. 02

    Pick Watch New Payment

    Search for Upgrade.Chat, choose Watch New Payment and select your connection. Make then offers the settings it can read from your account, so fill them in from the lists it shows.

  3. 03

    Add Create an Invoice

    Click the + on the right of the trigger and add Create an Invoice. Map the payment data coming from the first module into the invoice fields, so each invoice matches the payment that triggered 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 passed along, here one payment). Check that the invoice came out as expected.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and paid plans can go down to 1 minute. Then flip the scenario switch on so it keeps running without you.

Triggers

What can start an Upgrade.Chat scenario?

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

Upgrade.Chat1Watch New Lead

Watch New Lead

triggerIn the docs only

Watch New Lead gives your scenario a starting point each time Upgrade.Chat has a new lead, so the rest of the chain can greet, tag or log that person. The documentation offers no description, so rely on the name and on what Run once shows you.

How it fires
it is a scheduled trigger, which means Make checks the app on the scenario's schedule rather than being alerted.
When to use it
you want every fresh lead copied into your CRM or announced to the sales team.
Watch out
run it once before switching the scenario on, to see which lead data really comes through.
Upgrade.Chat2Watch New Payment

Watch New Payment

triggerIn the docs only

With Watch New Payment, every new payment recorded in Upgrade.Chat becomes a bundle your scenario can act on: an invoice, a thank-you message, a line in your accounting sheet.

How it fires
scheduled, so Make checks the app on the scenario's schedule. On the Free plan the shortest gap between two checks is 15 minutes.
When to use it
the moment money comes in should trigger paperwork or a notification.
Watch out
each payment picked up costs operations in every module that follows, so keep the chain short while you test.
Upgrade.Chat3Watch New Subscription Events

Watch New Subscription Events

triggerIn the docs only

Watch New Subscription Events lets you react to what happens to subscriptions in Upgrade.Chat, one event per bundle. The documentation does not list which events are covered, so the first test run is your best source.

How it fires
scheduled; Make checks the app on the scenario's schedule and collects what appeared since the previous check.
When to use it
you track subscriber changes in a spreadsheet or want a teammate pinged about them.
Watch out
if only some kinds of events matter to you, look at how Run once labels them before you build the next modules around them.
Modules

What can Make do in Upgrade.Chat?

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

Upgrade.Chat1

Add a Contact

ActionIn the docs only

Add a Contact puts a new person into Upgrade.Chat from any other app in your scenario, so your contact list fills itself instead of waiting for manual entry.

When to use it
a form, a webinar tool or a chat app collects someone who should exist in Upgrade.Chat too.
Watch out
the documentation says nothing about duplicates, so if they would hurt, run Get a Contact Details first.
Upgrade.Chat2

Add a Subscription

ActionIn the docs only

This action attaches a subscription in Upgrade.Chat without anyone opening the dashboard, which helps when the decision to subscribe someone is made in another tool.

When to use it
a deal marked as won in your CRM should give the customer their subscription.
Watch out
the documentation lists no fields for this module, so open it in the editor and map only what Make proposes.
Upgrade.Chat3

Create a Product

ActionIn the docs only

Create a Product saves you from typing the same offer twice: the product defined elsewhere shows up in Upgrade.Chat through the scenario.

When to use it
your catalog lives in a spreadsheet or another store and Upgrade.Chat should mirror each new line.
Watch out
a test with Run once creates a real product, so tidy up any sample you make while building.
Upgrade.Chat4

Create an Invoice

ActionIn the docs only

Your paperwork catches up on its own: Create an Invoice issues an invoice in Upgrade.Chat from data the scenario already holds, such as a payment or an order.

When to use it
right after Watch New Payment, so every sale leaves a matching document.
Watch out
map values from the previous module rather than typing them, or every invoice will carry the same fixed text.
Upgrade.Chat5

Get a Contact Details

ActionIn the docs only

Need the full record of someone before acting on it? Get a Contact Details reads one contact from Upgrade.Chat and hands their details to the next modules.

When to use it
before Update a Contact, or to enrich a message with what Upgrade.Chat knows about that person.
Watch out
you must tell it which contact to fetch, usually by mapping an identifier from an earlier module.
Upgrade.Chat6

Make an API Call

ActionIn the docs only

When none of the other modules fits, Make an API Call lets you reach any endpoint of the Upgrade.Chat API from your scenario, using the connection you already set up.

When to use it
you need an object or an operation the 10 listed modules do not cover.
Watch out
you write the request yourself, so keep the Upgrade.Chat API reference at hand; the documentation describes no fields for this module.
Upgrade.Chat7

Update a Contact

ActionIn the docs only

Update a Contact keeps a person's record in Upgrade.Chat current when their details change somewhere else, without anyone retyping them.

When to use it
a customer edits their email or name in your CRM and Upgrade.Chat should follow.
Watch out
the documentation does not say how empty fields are handled, so test with Run once on a sample contact first.
Need help

Need help automating Upgrade.Chat with Make?

A person reads every message.

FAQ

Upgrade.Chat and Make: common questions

01Is the Upgrade.Chat Make integration free?
Yes, Upgrade.Chat is a standard app in Make, available from the Free plan. That plan lets you keep 2 active scenarios, with at least 15 minutes between two scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Every module run counts as an operation on your plan. 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 run. Upgrade.Chat's own pricing is a separate matter.
02What do you need to connect Upgrade.Chat to Make?
An Upgrade.Chat account you can manage and a Make account. Make's documentation lists no specific prerequisite for this app and no dedicated connection steps, so the standard flow applies: add an Upgrade.Chat module, click Create a connection, name it if you want, then authorize Make on the Upgrade.Chat page or paste the key the app provides, and save. The same connection then serves all 10 modules, including Make an API Call.
03Do Upgrade.Chat triggers in Make fire instantly?
No. Make's documentation only names the 3 Upgrade.Chat triggers (Watch New Lead, Watch New Payment and Watch New Subscription Events), and going by those names, they are scheduled. Make checks Upgrade.Chat on the scenario's schedule, every 15 minutes by default, and picks up whatever appeared since the last check. On a paid plan you can shorten the gap to 1 minute. No instant trigger is listed for this app, so a new payment waits for the next check before your scenario reacts to it.
04What if a module is missing in the Upgrade.Chat Make app?
Use Make an API Call. It calls any endpoint of the Upgrade.Chat API from your scenario with the connection you already have, which covers objects and operations the 3 triggers and 6 other actions leave out. Keep in mind that Make's documentation for Upgrade.Chat is limited: it names the modules without describing their fields, so you will rely on the Upgrade.Chat API reference and on test runs with Run once to see what each module returns.
05Should you use Make or n8n for Upgrade.Chat?
It depends on what each tool offers for this app when you compare them. On Make, Upgrade.Chat comes with 10 ready modules, all scheduled on the trigger side, plus Make an API Call for the gaps, and it works from the Free plan. On n8n, check whether an Upgrade.Chat node exists and which operations it covers before deciding. Pick the tool whose modules match your scenario with the fewest workarounds, and the one your team already knows how to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations