Simplero

Manage contacts, lists, courses, subscriptions, and revenue with the Simplero v2 API. Agents enrol buyers, grant course access, and keep billing and access in step.

30 actions API key available

Simplero website ↗ Platform Documentation ↗ Capability data verified 2026-08-02

A refund request is approved in the support queue

Agent reads Get Purchase for the amount, the product and the purchase date

Agent checks which courses that purchase granted, using List Courses and the contact's record

Agent calls Refund Purchase to return the money

Agent posts the refunded purchase and the access it granted to the course owner

Owner decides whether access follows the money, and the agent calls Revoke Course Access only if they say so

What This Integration Enables

Simplero is the most recurring-revenue shaped platform of its class, and the action list shows it. Refund Purchase and Cancel Purchase sit next to Grant Course Access and Revoke Course Access, which means the money ledger and the entitlement ledger are both reachable from the same workflow. That combination is rare. Most course platforms make you read billing in one system and grant access in another, and the gap between them is where customers end up paying for something they cannot open, or opening something they stopped paying for.

Simplero also draws a line that this integration takes seriously: refunding a purchase does not revoke access. That is a deliberate product decision, not an oversight, and it is correct, because whether access follows the money is a business call that differs case by case. An agent can process the refund, gather the evidence about what that purchase unlocked, and hold the access question for a person. Around that core the connector covers the full contact lifecycle, from Create Contact through list subscriptions, tagging, segments, lead scoring and automations, so provisioning a new buyer and winding one down are both single workflows rather than a checklist. FlowRunner's connectors are built and verified against each vendor's official API, and this one targets Simplero's v2 API, where contacts are addressed as customers.

Without FlowRunner

Money and access move by hand A refund is issued in one screen and access is revoked in another, whenever somebody remembers

Every refund treated the same A goodwill refund and a chargeback trigger the same reflex, because the reflex is faster than the judgment

Recurring revenue read after the fact Purchases are exported and reconciled at month end, so a failed renewal surfaces weeks late

With FlowRunner

Money and access move together on purpose The refund and the access decision happen in one workflow, with the second one recorded as a decision

The two cases are separated The agent brings the progress and the reason to a person, who rules once and the workflow finishes

Recurring revenue read continuously Purchases flow into the books as they happen, and a lapse becomes an exception the same day

Use Case Scenarios

Provisioning a buyer whose payment happened elsewhere

A payment settles in Stripe for a product sold off a landing page that Simplero does not host. The agent calls Create Contact or Update Contact so the buyer exists with the right details, Subscribe Contact To List to put them on the list matching the product, Grant Course Access for what they actually bought, and Start Automation For Contact to begin the onboarding sequence. Add Tag To Contact records the acquisition source so the segments stay meaningful later. One purchase, one workflow, and the buyer opens their course while the confirmation email is still arriving.

Recurring revenue that reconciles itself

List Purchases and Get Purchase carry the transaction detail that finance needs, and Simplero's date filters take relative presets like This Month and Last Quarter rather than arbitrary ranges, which suits a scheduled close. The agent pulls the period, maps products through List Products and Get Product, and writes the result into QuickBooks Online or Xero. Anything that does not map to a known product is not silently posted to a suspense account. It is raised as one of the workflow's automation exceptions and sent to the controller with the purchase attached.

A renewal fails and somebody has to decide what that means

A subscription payment does not go through. The reflex is to cancel and cut off access, but an expired card and a customer who has decided to leave look identical in the data and are completely different situations. The agent pauses the nurture sequence with Stop Automation For Contact so the person is not receiving upsells while their billing is broken, posts the case to the owner in Slack with the purchase history from List Purchases, and waits. If the owner says stop billing, the agent calls Cancel Purchase. If they say chase it first, the agent starts the dunning automation instead and leaves access alone.

Human-in-Loop Highlight

Simplero's own documentation is explicit that Refund Purchase does not revoke access, and pairing it with Revoke Course Access is a choice the operator makes. That is exactly where the agent stops. Returning the money is mechanical: it was approved, the amount is known, and the call is safe to make. Deciding whether the person also loses the course is not mechanical, because the right answer depends on facts the agent has but cannot weigh. A customer who refunded on day three after opening one lesson is not the same as one who refunded in month two having finished the whole thing, and a chargeback is not the same as either. So after the refund lands, the agent posts to the course owner: "Refunded 297 USD to [email protected] for Positioning Intensive, purchased 61 days ago. He has completed the course. Revoke his access, or leave it in place? Revoking cannot be reversed without re-granting." The owner answers once and the workflow finishes the job. This is the human-in-the-loop pattern doing what it is for: the agent takes the reversible action on its own and puts the judgment call, with the evidence already gathered, in front of the person who owns the outcome.

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

30 actions

Contacts

List Contacts Lists contacts with pagination, where the page size defaults to 20 and caps at 100. Used to reconcile a Simplero audience against another database or to build a working set for a bulk workflow.
Get Contact Retrieves a single contact record. Used as the lookup step before any decision that depends on who the person is or what they already have.
Create Contact Creates a new contact. Used when a purchase, a form submission or a CRM record outside Simplero needs to become a person inside it.
Update Contact Updates the fields on an existing contact. Used to keep details in step with the system of record rather than letting the two drift apart.
Adjust Lead Score Changes a contact's lead score. Used to reflect behaviour that happened outside Simplero, such as a demo attended or a proposal opened, so the scoring reflects the whole relationship.
Mark Contact As Do Not Contact Flags a contact as do not contact. Used to honour an opt-out request that arrived through a support ticket or a reply rather than an unsubscribe link.
Archive Contact Archives a contact. Used to retire a record at the end of a relationship while keeping the history intact.

List and Tag Membership

Add Tag To Contact Applies a tag to a contact. Used to record a state or a source that segments and automations later key off.
Remove Tag From Contact Removes a tag from a contact. Used to take somebody out of a tag-driven audience without touching their list subscriptions.
Subscribe Contact To List Subscribes a contact to a mailing list. Used when a purchase or an event should put somebody on a specific list, with the welcome email and auto-responses skipped when migrating existing subscribers.
Unsubscribe Contact From List Unsubscribes a contact from a mailing list. Used to narrow what somebody receives without marking them do not contact entirely.

Automations

Start Automation For Contact Enrols a contact into an automation. Used to hand a sequence back to Simplero once an outside workflow has decided which one applies.
Stop Automation For Contact Removes a contact from a running automation. Used when circumstances change mid-sequence, such as pausing onboarding while a billing problem is being resolved.
List Automations Lists the automations configured in the account. Used to resolve an automation by name before starting or stopping it.

Course Access

Grant Course Access Grants a contact access to a course. Used to provision a buyer whose payment settled in another system, or to unlock the next course when a prerequisite is finished.
Revoke Course Access Removes a contact's access to a course. Used after a refund or a cancellation, and gated behind a person because Simplero deliberately does not tie it to the refund itself.
List Courses Lists the courses in the account. Used to resolve a course by name and to see what a given purchase was supposed to unlock.

Lists, Tags and Segments

List Lists Lists the mailing lists in the account. Used to resolve a list by name before subscribing anybody to it.
Get List Retrieves a single mailing list. Used to confirm the target of a subscription before writing to it.
Create List Creates a new mailing list. Used when a launch or a cohort needs its own audience rather than a tag on a shared one.
List List Subscriptions Lists the subscriptions attached to a list. Used to audit who is actually receiving a sequence, which is often different from who was supposed to.
List Tags Lists the tags defined in the account. Used to resolve a tag by name and to avoid creating a near-duplicate of one that already exists.
Create Tag Creates a new tag. Used when a workflow needs a state that the account does not yet track.
List Segments Lists the segments defined in the account. Used to read how the audience is already divided before an agent builds anything on top of it.

Products and Purchases

List Products Lists the products in the account. Used to map a transaction to what was actually sold.
Get Product Retrieves a single product. Used to confirm what a purchase entitles somebody to before access is granted.
List Purchases Lists purchases, with relative date presets such as This Month or Last Quarter rather than arbitrary ranges. Used to pull a period into finance reporting on a schedule.
Get Purchase Retrieves a single purchase with its amount, product and date. Used as the evidence step before a refund, a cancellation or an access decision.
Refund Purchase Refunds a purchase. Note that Simplero does not revoke course access as part of a refund, so an agent pairs this with Revoke Course Access only when a person has decided access should follow the money.
Cancel Purchase Cancels a purchase, stopping future billing on a subscription. Used when a customer leaves or a failed renewal has been ruled a genuine cancellation rather than a card problem.

Frequently Asked Questions

What can FlowRunner do with Simplero?

FlowRunner agents can run List Contacts, Get Contact, and Create Contact in Simplero, plus 27 more actions.

Does connecting Simplero to FlowRunner require OAuth?

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

Can Simplero trigger a FlowRunner workflow automatically?

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

Start building with Simplero

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

Start Building Free Talk to us