FlowRunner
PricingContact
Theme
Start Free

DropFunnels

E-commerce

Pull leads, orders, and course activity from DropFunnels, covering sites, funnels, every order type, and course membership. Agents route new buyers and students into fulfilment and onboarding the moment they convert.

23 actions API key available
Nightly sweep of subscription billing across a DropFunnels site
Agent pulls Get Subscription Orders and Get Membership Orders for each funnel
Agent compares the lapsed payers against Get Deactivated Members and skips anyone already suspended
Agent confirms each lapse is a genuine billing failure rather than a plan change already recorded upstream
Agent calls Deactivate Course Member on the clear expired-card cases, which keeps the learner's progress intact
Agent posts the accounts it will not rule on by itself to the course owner in Slack
Owner decides each one, choosing continued suspension or Delete Course Member, which discards the enrolment permanently

What This Integration Enables

DropFunnels keeps the site, the funnel, the checkout and the course under one roof, which means the record of who paid and the record of who has access are the same record. That is the reason this integration is worth wiring up. It is not a lead-sync connector with a course endpoint bolted on the side. Thirteen of its actions read money and progress, three of them write entitlement, and the interesting work sits in between: somebody bought something, and now they need access to something, and one day that access has to come back.

The order surface is already sliced the way a business reads it. Get Main Product Orders returns clean acquisition, Get Upsell And Downsell Orders returns what the offer steps added, and Get Subscription Orders returns the recurring base, so nobody has to do that arithmetic in a spreadsheet first. The progress surface goes four levels deep, from course down to lesson, which turns "should this person keep their access" from a guess into a question with evidence attached. FlowRunner's connectors are built and verified against each vendor's official API, so an agent working this surface is reading DropFunnels itself, not a scraped approximation of it.

Without FlowRunner

Access follows nobody Payment lives in the billing system, access lives in the course, and a person copies between them
Suspension and deletion blur together Under time pressure the fastest revocation wins, so an expired card gets handled like a chargeback
Revenue arrives as one number Front-end, bump, upsell and subscription income are separated by hand before anyone can read them

With FlowRunner

Access follows the payment Enrolment is granted, suspended and restored by the same workflow that watches the billing
Reversible by default Suspension is the automatic path and permanent deletion is a decision somebody makes on purpose
Revenue arrives pre-split Each order slice is pulled on its own, so acquisition and expansion revenue land separately

Use Case Scenarios

Provisioning access from a checkout that lives somewhere else

Plenty of creators sell through DropFunnels but charge through a separate processor, or sell a bundle where one purchase should unlock three courses. When a payment settles in Stripe, the agent resolves the buyer's entitlement against Get All Membership Products, calls Create Course Member for each course in the bundle with the right access levels, and confirms the enrolment landed by checking Get Membership Orders. If the purchase does not map cleanly to a known membership product, the agent does not guess a course. It routes the order to the owner rather than enrolling somebody in the wrong thing.

Splitting acquisition revenue from expansion revenue

A funnel that runs paid traffic needs to know what the front-end offer earned on its own, because that is the number the ad spend is judged against. On a schedule, the agent pulls Get Main Product Orders, Get Upsell And Downsell Orders and Get Subscription Orders separately, tags each slice, and writes them into Google Sheets for the media buyer and into QuickBooks Online for the books. Get Orders With API Fields picks up the checkout metadata that has to travel with the order, so attribution does not get lost between systems. The reporting shifts from an assembly job to a review job.

Refunds, chargebacks and erasure requests

Three different events end with a member losing access, and they are not the same event. A goodwill refund on a course somebody barely opened is not a chargeback, and neither is a data erasure request. The agent gathers the same evidence for all three, the order from Get Membership Orders and the progress from Get Lesson Completed Members, then applies the outcome the owner chose: suspension through Deactivate Course Member, or removal through Delete Course Member. Get Deleted Members afterwards is the audit trail that shows an erasure request was actually carried out, which is the part that matters when somebody asks six months later.

Human-in-Loop Highlight

The gate is the difference between Deactivate Course Member and Delete Course Member, and DropFunnels draws that line sharply: deactivation suspends access and keeps the member's progress, deletion discards the enrolment record entirely. A dunning agent hits that fork every night. It can suspend an expired card on its own, because suspension is reversible and Create Course Member restores the person the moment billing recovers. It cannot decide that somebody's progress should stop existing. So when a lapse looks like a dispute rather than a dead card, the agent stops and posts the case to the course owner in Slack: "Subscription for [email protected] lapsed 11 days ago on Advanced Positioning. She has completed 14 of 19 lessons. Suspend and keep her progress, or delete the enrolment? Deletion cannot be undone." That is a human-in-the-loop pause with the evidence already assembled, not an alert that makes somebody go and look things up. The agent handles the reversible half on its own and brings the permanent half to a person.

Agent processes routinely
Detects that fork every night
Clear match Continues automatically
Ambiguous Routes to human via Slack
Human decides
Agent resumes with decision

Agent Capabilities

23 actions

Sites and Catalog Lookups

5
  • Get All Sites Lists every DropFunnels site the authenticated token can reach, returning each site's ID and name. Nearly every other action is scoped to a site, so this is the first call when an agent works across more than one property.
  • Get All Funnels Lists the sales funnels published on a site with their IDs and names. Used to translate a funnel name a person typed into the ID the lead and order actions expect.
  • Get All Courses Lists the courses hosted on a site with their IDs and names. Used as the lookup step before any enrolment or progress action, since course IDs are required by all of them.
  • Get All Membership Products Lists the membership products configured on a site. Used to reconcile what a customer is entitled to against the access actually granted elsewhere in the stack.
  • Get All Quizzes Lists the quizzes published on a site with their IDs and names. Used ahead of Get Completed Quiz Results when an agent needs scores or answers.

Leads

2
  • Get Leads Returns leads captured by a funnel, including name, email, phone and the specific funnel page that converted them. Used to sync opt-ins into a CRM or email platform on a schedule.
  • Get Two Step Leads Returns leads captured through two-step opt-in forms, where the visitor clicks a button before the form appears. DropFunnels stores these separately from standard leads, so an agent building a complete opt-in picture pulls both.

Orders and Revenue

6
  • Get All Orders Returns every purchase recorded against a funnel, covering all products bought in each transaction. Used as the starting point for revenue reporting or an accounting sync.
  • Get Main Product Orders Returns only the front-end product purchases for a funnel, excluding upsells, downsells and order bumps. Used when the question is acquisition performance rather than total basket value.
  • Get Upsell And Downsell Orders Returns the upsell and downsell purchases made inside a funnel after the initial checkout. Used to measure what each offer step adds on top of the front-end sale.
  • Get Subscription Orders Returns the recurring subscription purchases made through a funnel. Used to reconcile active plans, detect lapsed billing, or feed recurring revenue reporting outside DropFunnels.
  • Get Membership Orders Returns the purchases that granted access to a specific course, tying revenue directly to enrolment. Used to verify that paying customers actually received the access they bought.
  • Get Orders With API Fields Returns orders that carry custom API fields, looked up by customer email and optionally narrowed to a product or a specific field key. Used when checkout metadata has to travel with the order into another system.

Course Membership

5
  • Create Course Member Enrols a person into a course and grants the access levels specified, creating the member record when it does not already exist. Used when a purchase or an approval in another system needs to provision access without anyone typing it in.
  • Deactivate Course Member Suspends a member's access to a course while keeping their record and progress intact. Used on a failed payment or a paused subscription, with Create Course Member restoring them when billing recovers.
  • Delete Course Member Removes a member from a course entirely, discarding the enrolment record. Used for refunds, chargebacks and erasure requests, and gated behind a person because it cannot be undone.
  • Get Deactivated Members Lists the members whose access to a course is currently suspended. Used to drive win-back messaging and to confirm a dunning sequence actually revoked what it said it revoked.
  • Get Deleted Members Lists the members that have been removed from a course. Used as the audit trail when reconciling refunds or proving an erasure request was carried out.

Progress and Quiz Signals

5
  • Get Course Completed Members Lists the members who have finished an entire course. Used as the moment to issue a certificate, unlock the next course, or ask for a testimonial.
  • Get Module Completed Members Lists the members who have finished a module within a course. Used as a mid-course progress signal to time a nudge before somebody stalls.
  • Get Lesson Completed Members Lists the members who have finished a lesson inside a course, the finest-grained progress signal DropFunnels exposes. Used for drip pacing and for spotting learners who stopped partway through.
  • Get Unit Completed Members Lists the members who have finished a unit within a course. Units sit between modules and lessons in the DropFunnels hierarchy, filling in the middle tier of progress reporting.
  • Get Completed Quiz Results Returns everyone who has completed a quiz, with their score, every question and answer pair, and the total question count. Used to route leads by their answers or to feed a qualification score into a CRM.

Frequently Asked Questions

What can FlowRunner do with DropFunnels?

FlowRunner agents can run Get All Sites, Get All Funnels, and Get All Courses in DropFunnels, plus 20 more actions.

Does connecting DropFunnels to FlowRunner require OAuth?

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

Can DropFunnels trigger a FlowRunner workflow automatically?

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

Start building with DropFunnels

$100 in credits. No card required. Connect in minutes.