Resources · Make integration

Digistore24 Make integrationAutomate Digistore24 with Make.

What happens in your other tools the moment Digistore24 records a sale? The Digistore24 Make integration gives you 3 instant triggers and 1 API call module. This guide is for vendors who sell there: connect the account, then build a first scenario step by step.

Try the Digistore24 integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Digistore24 Make integration do for you?

The Digistore24 Make integration links your vendor account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick such as a trigger or an action. Digistore24 alerts Make when a payment, an eticket or an affiliate approval happens, and your scenario passes that data on to your other apps.

Welcome every buyer the same way. Watch New Payment starts a scenario for each new payment, so a CRM contact, a spreadsheet row or a welcome email can follow without anyone copying order details by hand.

Onboard new partners without a checklist. Watch Affiliate Approved fires when you approve an affiliate. Hand that record to your newsletter tool or your team chat, and the partner receives the right material while your team stays informed.

Keep an eye on etickets. Watch Eticket Created reacts when a new eticket is created, which lets you log each one somewhere your support team already looks.

The listed modules only watch events. Anything else goes through Make an API Call, which reuses your connection to reach other endpoints of the Digistore24 API. The Make documentation for this app is marked as AI-generated from the vendor docs, so check important details with Digistore24. The same app often exists in n8n too; the n8n vs Make comparison lays out both options, and Make training covers the editor from scratch.

Connect

How do you connect Digistore24 to Make?

  1. 01

    Create an API key in Digistore24

    In the vendor view, open Settings > Account access, then the API keys tab. Click New API key, name it, pick the permissions your scenario needs, click Save and copy the key shown.

  2. 02

    Add a Digistore24 module in Make

    In your scenario, add any Digistore24 module and click Create a connection. A connection is your Digistore24 account linked to Make once, then reused by every module of the app. The Connection name field is optional.

  3. 03

    Paste the key and save

    Enter the API key you copied, or follow the instructions Make shows on screen, and confirm. From now on the connection appears in the dropdown of each Digistore24 module you add to a scenario.

First scenario

Your first scenario with Digistore24

GoalWhen a new payment is created in Digistore24, Make calls the Digistore24 API endpoint you choose with the same connection.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to place the first module. Everything you build next hangs off this starting point.

  2. 02

    Pick Watch New Payment

    Search for Digistore24, choose Watch New Payment, click Create a webhook, then Create a connection and paste your API key. The lightning badge shows this trigger is instant.

  3. 03

    Add Make an API Call

    Click the + to the right of the trigger and add Make an API Call from Digistore24. Point it at the endpoint you need and map values from the payment, which arrives as one bundle: a single item handed from one module to the next.

  4. 04

    Test with Run once

    Click Run once, then wait for the next payment to reach Digistore24. Open the bubble above each module to read the bundle it received and check that the API call got the values you mapped.

  5. 05

    Switch the scenario on

    Turn the scenario on. From then on each payment runs it, and every module run counts as one operation, the unit Make deducts from your plan.

Triggers

Digistore24 triggers in Make

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

Digistore241Watch Affiliate Approved

Watch Affiliate Approved

Instant trigger

In Make“Triggers when an affiliate is approved.”

Your scenario starts as soon as you approve an affiliate in Digistore24, so a new partner gets onboarded by your other tools instead of by a reminder on your to-do list.

How it fires
instant. Digistore24 calls Make through a webhook the moment the approval happens.
When to use it
you recruit partners for a product launch and want each approved affiliate added to a partner list with the promo kit sent right away.
Watch out
click Create a webhook before the connection, or the trigger will never receive the event.
Digistore242Watch Eticket Created

Watch Eticket Created

Instant trigger

In Make“Triggers when a new eticket is created.”

Each time a new eticket is created in Digistore24, this module hands it to your scenario as one bundle, ready to be logged or forwarded to whoever handles it.

How it fires
instant. Digistore24 notifies Make by webhook as soon as the eticket exists.
When to use it
your support lead wants every new eticket to land in a shared table so nothing sits unanswered.
Watch out
the module description does not say what an eticket carries, so click Run once and read the first bundle before you map anything from it.
Digistore243Watch New Payment

Watch New Payment

Instant trigger

In Make“Triggers when a new payment is created.”

This is the trigger most vendors start with: every new payment created in Digistore24 launches your scenario, carrying the order data your CRM or accounting tool needs.

How it fires
instant. Digistore24 sends each payment to Make through a webhook as it is created.
When to use it
a course creator wants buyers tagged in the email tool and a row added to the sales sheet after each purchase.
Watch out
every payment runs the whole scenario, and each module run is an operation counted on your Make plan.
Modules

What Digistore24 can do in Make

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

Digistore241

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

With this module you reach any endpoint of the Digistore24 API from your scenario, using the connection you already set up, so you are not limited to the three listed triggers.

When to use it
a payment has arrived and you need Digistore24 to do something that none of its listed modules offers, following the endpoint described in the Digistore24 API documentation.
Watch out
the API key only allows what its permissions allow, so tick the right ones when you create it in Digistore24.
Need help

Need help automating Digistore24 with Make?

A person reads every message.

FAQ

Digistore24 and Make: common questions

01Is the Digistore24 Make integration free?
Yes, on the Make side. Digistore24 is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, 15 minutes minimum between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lift the scenario cap and bring the interval down to 1 minute, with usage counted in operations each month. You still need an active Digistore24 account, whose own pricing is set by Digistore24.
02What is needed to connect Digistore24 to Make?
An active Digistore24 account and an API key. In the vendor view, go to Settings, Account access, open the API keys tab and click New API key. Name the key, choose the permissions your scenario needs, save it and copy the value. In Make, add a Digistore24 module, click Create a connection and paste the key. For the instant triggers, click Create a webhook first so Digistore24 knows where to send events.
03Do Digistore24 triggers in Make react in real time?
Yes. All three triggers, Watch New Payment, Watch Affiliate Approved and Watch Eticket Created, are instant: Digistore24 calls Make through a webhook as soon as the event happens, so the scenario runs right after it instead of waiting for a polling interval. The 15 minute default schedule of new scenarios applies to scheduled triggers, not to these. Keep the scenario switched on, otherwise the webhook has nothing listening on the Make side.
04What if a Digistore24 module is missing in Make?
Use Make an API Call. It calls any endpoint of the Digistore24 API with the connection you already have, so actions the listed modules do not cover stay within reach. The Make documentation for this app is marked as AI-generated from the Digistore24 docs and may contain mistakes, so verify the endpoint and its parameters in the vendor documentation or with Digistore24 directly before you rely on it in a live scenario.
05Make or n8n for Digistore24?
It depends on the tool your team already uses. In Make, Digistore24 offers 3 instant triggers and an API call module, available from the Free plan, and the editor shows each step as a bubble you can test with Run once. The same app often has an n8n node as well. The fairest test is to build the scenario you need in both and keep the one your team finds easier to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations