elopage

elopage, now ablefy, is the German platform for selling digital products, courses, memberships and downloads. Agents grant access with free orders, cancel subscriptions, read payments and affiliate publishers, and manage funnels, upsells and webhook endpoints.

47 actions API key available

elopage website Platform Documentation Capability data verified 2026-08-26

An approved registration names a person who should have access to a course or download

Agent pulls the email address and the product the entitlement covers

List Products confirms the product and its pricing plan before anything is granted

Create Free Order grants access against that email address and returns the order token

The order token is written back to the CRM record, because nothing in the API can look it up later

The buyer gets the access confirmation and the revenue channel gets the entry

Any later cancellation is confirmed against the named person before access is revoked

What This Integration Enables

elopage, now trading as ablefy, sells things that are not shipped. Courses, memberships, downloads, and digital products change hands as entitlements, which means the operations work is not fulfillment but access: who is allowed in, who stops being allowed in, and which offer they came through. That reframes what the automation is worth. Create Free Order is the most useful operation in this API precisely because it is the one that grants access to a named email address without money moving, which is what a bonus, a workshop cohort, a partner bundle, or a service recovery actually needs.

Around that sits the selling machinery: products with up to five pricing plans, pre-checkout bundles and post-checkout one-click upsells, funnels whose nodes branch on whether the buyer accepted or declined, and an affiliate publisher roster. FlowRunner agents assemble and maintain all of it, and the platform's human-in-the-loop steps sit where the consequences fall on a paying customer rather than on a record.

Without FlowRunner

Access granted by hand Somebody opens the seller dashboard and adds each person to each product

Entitlements drift from the CRM The list of who has access lives only in elopage, and nobody outside can see it

Cancellations are unverified A churn signal leads to a subscription being ended without a check on whose it was

With FlowRunner

Access follows the approval The approval that already exists grants the entitlement, one call, no dashboard

The token travels with the record The order token is captured at creation, which is what makes a later cancellation possible at all

Ending access is a decision A person confirms the identity and the consequence before the subscription is canceled

Use Case Scenarios

Cohort access, granted in bulk, without a dashboard

A workshop closes registration with a list of attendees in Google Sheets. The agent reads the rows, confirms the product and pricing plan once, then calls Create Free Order for each email address. Each response carries an order token, and the agent writes that token back to the attendee's row immediately, because elopage publishes no route that resolves a token from an order id and a token never captured is a subscription that can never be canceled from a flow. The cohort is enrolled before anyone opens the seller dashboard.
A new offer built end to end

A launch plan calls for a product, a payment plan, a post-checkout upsell, and a funnel that branches on whether the buyer took it. The agent calls Create Product, then Create Pricing Plan, which returns the checkout URL the launch needs. It creates the upsell, attaches it through Create Product Upsell Relation with a deliberate position, and builds the funnel and its nodes so the accepted and declined branches both land somewhere. The checkout URL goes out to the members channel through Discord. What used to be an afternoon of clicking is a flow that produces the same structure every time.
The affiliate roster stays honest

On a schedule, the agent calls List Publishers and reconciles the affiliate list against the partnerships tracker. Approved applicants who are not yet enrolled get Enroll Publisher. Partners whose agreement has lapsed are collected into a single summary for the partnerships manager rather than being unenrolled automatically, because removing a publisher affects their commission on work already done. The roster in the tracker and the roster in elopage stop disagreeing.

Human-in-Loop Highlight

Cancel Subscription is keyed on the order token, not the order id, and that detail is the whole reason this gate exists. There is no route that looks a token up, which means the agent cannot ask elopage who a token belongs to before it uses it. It can only trust that the token it captured earlier still points at the person the workflow thinks it does. Refunds make it worse: elopage keeps them in the dashboard, so the API offers no compensating action if the cancellation was aimed at the wrong customer. The agent therefore assembles what it does know and stops. It posts: "Churn rule matched Anna Weber, Membership Pro, token captured 2026-03-04 from a Create Free Order response, last payment read through Get Payment on 2026-08-01. Canceling ends access immediately and cannot be refunded through this connector. Cancel, or hold for outreach?" A person confirms that the token, the name, and the intent line up. Ending someone's access to something they paid for is not a write the API can verify on the agent's behalf, so a human verifies it instead.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

47 actions

Products and Pricing

List Products Lists the seller's products with the ids the rest of this connector is keyed on. Also the connection check.
Get Product Retrieves one product with its embedded pricing plans.
Create Product Creates a digital product, course, membership, or download.
Update Product Updates a product. Include an existing plan's id when editing its pricing, because a plan sent without one is added rather than changed.
Get Pricing Plan Retrieves one pricing plan. elopage publishes no route that lists plans, so plan ids come from creation or from the plans embedded in a product.
Create Pricing Plan Creates a pricing plan attached to a sales page and returns the checkout URL a launch needs. A product may carry at most five.
Delete Pricing Plan Deletes a pricing plan and removes it from the sales page it was attached to.

Access and Payments

Create Free Order Creates a free order against an email address, which is how access to a course, membership, or download is granted from a flow. Its response carries the order token, so capture it.
Cancel Subscription Cancels a subscription using the order token, behaving exactly as canceling from the dashboard does. The operation this page's human gate exists for.
Get Payment Retrieves a payment record, including its state, for reconciliation and churn checks.

Affiliates

List Publishers Lists the affiliate publishers on the account with their email addresses.
Enroll Publisher Adds a publisher to the affiliate program, driven by a CRM or an application form.
Unenroll Publisher Removes a publisher from the program.

Funnels

List Funnels Lists the post-purchase funnels on the account.
Get Funnel Retrieves one funnel with its root node.
Create Funnel Creates a funnel, which is what a buyer is shown after a purchase completes.
Update Funnel Updates a funnel's configuration.
Delete Funnel Deletes a funnel.
List Funnel Nodes Lists funnel nodes. elopage publishes no way to filter these by funnel, so every funnel's nodes come back together.
Get Funnel Node Retrieves one node with its parent, its direction, and the upsell it points at.
Create Funnel Node Creates a node in a funnel, branching on whether the buyer accepted or declined the previous offer.
Update Funnel Node Updates a node's direction or target.
Delete Funnel Node Deletes a node from a funnel.

Upsells

List Upsells Lists the upsells configured on the account.
Get Upsell Retrieves one upsell with its form, which decides whether it is a pre-checkout bundle or a post-checkout offer.
Create Upsell Creates an upsell in either its presell or postsell form.
Update Upsell Updates an upsell's content or form.
Delete Upsell Deletes an upsell.
List Upsell Add-ons Lists the add-ons attached to upsells.
Get Upsell Add-on Retrieves one upsell add-on.
Create Upsell Add-on Creates an add-on on an upsell.
Update Upsell Add-on Updates an add-on.
Delete Upsell Add-on Deletes an add-on.

Product Relations

List Product Funnel Relations Lists the links between products and the funnels shown after their purchase.
Get Product Funnel Relation Retrieves one product to funnel link.
Create Product Funnel Relation Attaches a funnel to a product.
Update Product Funnel Relation Updates an existing product to funnel link.
Delete Product Funnel Relation Removes a funnel from a product.
List Product Upsell Relations Lists the links between products and the upsells shown on their payment page.
Get Product Upsell Relation Retrieves one product to upsell link, including its position.
Create Product Upsell Relation Attaches an upsell to a product's payment page. Position decides the order several upsells appear in, and a position of zero is a real value.
Update Product Upsell Relation Updates a link, which is how upsells are reordered.
Delete Product Upsell Relation Removes an upsell from a product.

Webhook Endpoints

List Webhook Endpoints Lists the endpoints the account posts events to.
Get Webhook Endpoint Retrieves one endpoint with its delivery URL.
Create Webhook Endpoint Registers a delivery URL, which is how an elopage account is pointed at a FlowRunner webhook so payment events reach a flow.
Update Webhook Endpoint Changes an endpoint's name or URL. elopage publishes no delete route for this resource, so repointing is how an endpoint is retired from a flow.

Frequently Asked Questions

What can FlowRunner do with elopage?

FlowRunner agents can run List Products, Get Product, and Create Product in elopage, plus 44 more actions.

Does connecting elopage to FlowRunner require OAuth?

No. elopage connects to FlowRunner with an API key, no OAuth flow required.

Can elopage trigger a FlowRunner workflow automatically?

elopage doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with elopage

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us