Resources · Zapier integration

Digistore24 Zapier integrationAutomate Digistore24 with Zapier.

The Digistore24 Zapier integration gives you 3 triggers, 0 actions and 0 searches. All three are instant: a sale, an approved affiliate or an eticket change starts your automation straight away, even on the free plan. Here is what each one does and where it trips people up.

See the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Digistore24 Zapier integration is for

The Digistore24 Zapier integration lets your sales platform report what happens to your products to the rest of your tools. Digistore24 sells digital products and seminars. Zapier listens for three kinds of events there, then hands the details to another app, with no copying by hand and no code.

Three results come up again and again. First, a live sales log: New Order Event pushes each payment or refund into a spreadsheet, so finance stops exporting reports. Second, a warm welcome for partners: New Affiliate Approved fires when you accept an affiliate, and the next step can send them your promo kit by email. Third, a guest list that keeps itself current: New Eticket Event follows tickets as they are created, updated or used at the door.

Now the honest part. Zapier can only listen to Digistore24 here. There is no action and no search on this app, so a Zap (more on that word below) cannot create a product, refund an order or look up a buyer inside Digistore24. Data flows out, never back in. If your plan needs writing into Digistore24, this integration will not cover it.

Zapier is not the only route, either. The Digistore24 Make integration page covers the same app on another platform, and the Make vs Zapier comparison helps you weigh the two before you commit.

Vocabulary

Zapier words, in plain English

Seven words do most of the work on this page. Read them once and the rest goes faster.

Zap
The automation you build in Zapier: one starting event, then one or more steps that run each time that event happens.
Trigger
The event in an app that starts the Zap. Here, a Digistore24 sale, affiliate approval or eticket change.
Action
What the Zap does once it starts: the step that writes a row, sends an email or posts a message in another app.
Task
What Zapier bills you for: one action that completes successfully. Your plan's allowance is a count of those.
Polling vs instant
A polling trigger is checked on a timer. An instant trigger is pushed by the app the second it happens. Digistore24 only has instant ones.
Filter
A step that lets the Zap carry on only when the incoming data meets your condition, and quietly stops it otherwise.
Connection
Your Digistore24 account linked to Zapier once, then reused by every step and every Zap that needs it.
Cost

What a Digistore24 Zap actually costs

Good news first: Digistore24 is not a premium app, so it works on the free plan.

  • Premium appNo, free plan works
  • Free plan100 tasks a month, two-step Zaps
  • Trigger cost0 tasks
  • Digistore24 triggers3 instant, 0 polling

The trigger itself never costs a task. Only a successful action counts, and a failed one is not billed. A Zap with three actions uses three tasks per sale, not one. The free plan gives you 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger, one action. Add a filter or a second action and it becomes a multi-step Zap, which needs a paid plan. The interval grid below only matters for polling triggers. All three Digistore24 triggers are instant, so it does not apply here.

Connect

Connect Digistore24 to Zapier in 3 steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. Type Digistore24 in the search box of the dialog and pick it from the results.

  2. 02

    Sign in to Digistore24

    Click Add connection. A new tab opens on Digistore24: sign in with the Digistore24 account that owns the products you sell, or with one that has access to them.

  3. 03

    Grant access

    Allow Zapier to reach the account. The connection then appears in your list and every Digistore24 step in every Zap can reuse it, so you only do this once.

First Zap

Your first Zap: log real sales, ping the team

GoalEach first payment on a product lands as a row in Google Sheets, and the sales channel in Slack hears about it.

  1. 01

    Pick the trigger

    Create a Zap, choose Digistore24 as the app and New Order Event as the event. Then select the Digistore24 connection you just made.

  2. 02

    Set events and products

    Choose the payment events to follow and the products concerned. Leave follow-up payments off if you want one row per buyer, not one per instalment.

  3. 03

    Test the trigger

    Run the test. Zapier brings back the three most recent order events from your account, so you map fields on a real sale, not on dummy data.

  4. 04

    Add the filter

    Add a filter step and point it at the value that tells a payment from a refund in your test result. Refunds stop here. This makes the Zap multi-step, so a paid plan.

  5. 05

    Add both actions

    Add Google Sheets, map the buyer and product into the row, then add Slack and write the channel message. Test each step once. Read what came back before moving on, because a wrong mapping shows up here, not in production.

  6. 06

    Publish

    Click Publish to switch the Zap on. From now on, every new matching sale runs it. Orders placed before that click stay where they are.

Triggers

The 3 Digistore24 triggers

3 events start a Zap when something happens in Digistore24, and 3 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Affiliate Approved

Instant trigger

In Zapier“Triggers when a new affiliation has been approved.”

The moment you approve someone as an affiliate for one of your products, this trigger hands their details to the next step. It turns a manual onboarding chore into something that just happens.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
sending each new partner your swipe copy and banners, or adding them to a partner list in your email tool, without waiting for you to remember.
Watch out
you must choose at least one product, and only approvals on the products you picked start the Zap.
2

New Eticket Event

Instant trigger

In Zapier“Triggers when an eticket has been created, updated or used.”

Selling seats for a seminar? This one follows your etickets through their life: created, updated, or used. You pick which of those moments matter to you.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
keeping an attendee sheet current, or emailing practical details as soon as a ticket exists.
Watch out
a setting decides whether incomplete tickets count. Set to yes, the Zap can start before the participant's name and email are filled in, so later steps may receive blanks. Set to no, the creation event waits until the email address is entered.
3

New Order Event

Instant trigger

In Zapier“Triggers when a transaction for an order is received (like a payment or a refund).”

Every transaction on an order lands here, payments and refunds alike. If a Zap needs to know that money moved, in either direction, this is where it starts.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
sending buyers to your CRM, logging revenue in a sheet, or alerting the team on each sale.
Watch out
the follow-up payments setting changes everything. Off, the Zap only runs on the first payment, which suits collecting buyer contacts. On, it runs on every instalment, which suits tracking amounts but multiplies your tasks.
When it breaks

When a Digistore24 Zap breaks

Zapier publishes no help article and no rate limit specific to Digistore24. What breaks is general Zapier behaviour, and it bites here like anywhere else.

Four cases cover most of the surprises. Read them before you switch the Zap on, not after the first missing sale. For deeper digging, the Zapier troubleshooting guide walks through the usual fixes.

  • Past orders never show up

    A Zap only reacts to what happens after you publish it. Last month's sales will not be replayed, so moving that history is a separate job.

  • Rows full of blanks

    With incomplete etickets allowed, the Zap can start before the participant's name and email exist, and the next step receives empty fields.

  • A big batch gets held back

    When a trigger suddenly sends a huge batch, after a bulk import for instance, Zapier's flood protection can hold those runs back.

  • A Zap that sets itself off

    A Zap that writes into the very place its own trigger watches restarts itself over and over, and burns through your task allowance fast.
Need help

Need help automating Digistore24 with Zapier?

A person reads every message.

FAQ

Digistore24 Zapier integration: quick answers

01Is the Digistore24 Zapier integration free?
Yes, it runs on the free plan, because Digistore24 is not a premium app. The free plan gives you 100 tasks a month and as many Zaps as you like. The catch is size: each free Zap is limited to two steps, one trigger and one action. As soon as you add a filter, for example to skip refunds, or a second action like a Slack message after a spreadsheet row, the Zap becomes multi-step and needs a paid plan.
02How many tasks does a Digistore24 Zap use?
The trigger costs nothing, so the bill depends only on what follows it. Each action that completes successfully counts as one task, and a failed one is not counted. A Zap that adds a row and then posts a message uses two tasks per sale. On New Order Event, switching on follow-up payments makes the Zap run on every instalment, not just the first one, which can multiply the count quickly on payment plans.
03Do Digistore24 triggers fire in real time?
Yes. All three are instant triggers: Digistore24 tells Zapier as soon as the order, affiliate approval or eticket event happens, and the Zap starts right away. The plan intervals of 15, 2 or 1 minutes only apply to polling triggers, which this app does not have. That makes it one of the cases where a free plan reacts as fast as a paid one. In the editor, a Zap built on an instant trigger shows a lightning bolt.
04What do you need to connect a Digistore24 account?
A Digistore24 account and a Zapier account are enough to start. You add the connection from the Apps page, sign in to Digistore24 in the tab that opens, then grant access. Pick the login carefully: every trigger asks you to select at least one product, so the account must be able to see the products you want to follow. If you work on someone else's products, you need access to them first.
05Why does a Digistore24 Zap run several times for one order?
Most of the time, it is the follow-up payments setting on New Order Event. With it on, each payment of an order starts the Zap, so an instalment plan produces one run per instalment. Turn it off if you only want the first payment, typically to capture the buyer once. Remember that refunds also arrive through this trigger, so a filter on the event type keeps them out of a sales log.
06What if the Digistore24 operation you want is missing?
Then Zapier cannot do it on this app today. The integration only offers three triggers and no action or search, so nothing can be written into Digistore24 from a Zap: no refunds, no product edits, no buyer lookups. What you can do is take the data out and act on it elsewhere. If the missing piece is an action inside Digistore24, that need decides your tool choice more than anything on this page.
07Zapier, Make or n8n for Digistore24?
Judge them on what your workflow needs. On Zapier, Digistore24 gives three instant triggers, zero actions and zero searches, and it works on the free plan as long as each Zap stays at two steps. So the questions are simple: do you only need to react to sales, affiliates and tickets, or must you write back into Digistore24? And will your Zaps need filters or several actions, which means a paid plan? Check those two points on each platform before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations