Digistore24
E-commerceRead your Digistore24 sales operation. Agents list purchases, orders, products, buyers, and financial transactions to sync new sales into a CRM, notify your team on purchases, and reconcile payments, refunds, and chargebacks.
What This Integration Enables
Digistore24 runs the storefront, the affiliates, and the payments for digital product vendors, which means it holds two ledgers that must agree: purchases, which are orders, and transactions, which are the individual money movements behind them. Most vendors only ever read the first one. FlowRunner agents read both, continuously, and push what they find into the CRM, the email platform, and the accounting sheet, so the sales operation runs on live data instead of dashboard visits. - Sync new sales into a CRM or spreadsheet as they happen, with full order context via Get Purchase - Announce purchases to the team channel the moment they post - Feed new buyers into email onboarding and nurture sequences - Reconcile payments, refunds, and chargebacks against orders for accounting - Verify credentials with Ping before any scheduled run commits to work
Without FlowRunner
With FlowRunner
Use Case Scenarios
The sale reaches every system before the buyer's confirmation email cools
A scheduled sweep calls List Purchases with a relative date range covering the last hour. Each new order becomes a profile and a purchase event in [Klaviyo](/integrations/klaviyo), which starts the onboarding sequence, and a row in the revenue sheet in [Google Sheets](/integrations/google-sheets). When an order crosses the high-value threshold, Get Purchase pulls the full detail and [Slack](/integrations/slack) alerts the sales team with buyer and product attached, so the personal follow-up happens while the purchase is still fresh.
Reconciliation that understands installments
Monthly close used to mean exporting orders, exporting payouts, and arguing with a spreadsheet. Now the agent calls List Purchases and List Transactions for the period and joins them: each installment payment, refund, and chargeback matched to its parent order. Subscription plans stop being a reconciliation headache because every money movement carries its order reference. The output is a closed ledger in the accounting sheet and a short exceptions list, which is the only part a person reads.
Buyers become an audience, not a list that goes stale
A weekly job calls List Buyers and diffs the result against the email platform. New buyers sync into [ActiveCampaign](/integrations/activecampaign) with their product associations, entering the nurture sequence that matches what they bought. List Products keeps the product mapping current, so a new offer added in Digistore24 shows up in the segmentation without anyone updating a lookup table.
Human-in-Loop Highlight
List Transactions is where the bad news arrives: the chargeback that reverses a sale you already celebrated and counted. What happens next is costly in both directions. Revoke the buyer's access and dispute aggressively, and you may burn a customer whose card simply expired. Do nothing, and chargebacks quietly become a habit that threatens your merchant standing. So the agent does the detection and the assembly, matching each reversal to its order, buyer history, and product, and then presents the case: "Chargeback on order DS-88412, second purchase from this buyer, first one kept. Revoke access and contest, or reach out first?" The [human-in-the-loop](/concepts/human-in-the-loop) gate makes sure a pattern-matching sweep never decides how you treat a customer's money.
Agent Capabilities
7 actionsConnection
1- Ping Tests the API connection and validates the configured key, returning the access level and version. The preflight step every scheduled workflow runs before committing to work.
Sales and Orders
2- List Purchases Lists sales and orders within a date range, with relative dates like "-24h" and "-7d" or absolute dates, covering everything you earn a commission on as vendor or affiliate. Paginated for large result sets. The backbone of every sync and reporting flow.
- Get Purchase Retrieves a single order's full detail by ID: buyer, product, payment plan, amounts, and payment status. The lookup behind support requests and high-value alerts.
Products
2- List Products Lists the account's products with IDs, names, prices, and status. Keeps external systems' product mappings in step with the storefront.
- Get Product Retrieves one product's full definition including pricing, payment plans, and configuration. Used when a workflow needs the offer's exact terms.
Buyers and Money Movements
2- List Buyers Lists customers with contact details and purchase associations. The source for CRM syncs and email audience building.
- List Transactions Lists individual money movements, payments, refunds, and chargebacks, within a date range. One order can carry many transactions across an installment plan, which is exactly why reconciliation needs this view. The operation this page's human gate exists for.
Frequently Asked Questions
What can FlowRunner do with Digistore24?
FlowRunner agents can run Ping, List Purchases, and Get Purchase in Digistore24, plus 4 more actions.
Does connecting Digistore24 to FlowRunner require OAuth?
No. Digistore24 connects to FlowRunner with an API key, no OAuth flow required.
Can Digistore24 trigger a FlowRunner workflow automatically?
Digistore24 doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Digistore24
$100 in credits. No card required. Connect in minutes.