SimpleShop

SimpleShop is the Czech checkout and invoicing platform for selling online. Agents issue invoices, proformas and the other document types, email and settle them, maintain the address book, and export who bought what.

Verified 28 actions Basic auth available

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

A scheduled sweep runs, because SimpleShop publishes no event stream to subscribe to

Search Documents pulls everything issued since the last run, advancing the date each time

Agent decodes each document's flags to tell paid from emailed from canceled

Agent matches the incoming bank lines against the advance invoices still outstanding

Mark Document Paid settles the matches and Create Final Invoice closes each settled advance

Agent posts the unmatched remainder to the finance channel with amounts and customer names

The controller decides what happens to the payments that matched nothing

What This Integration Enables

SimpleShop is a document ledger with a checkout attached, and the clearest evidence is what its API declines to do. You cannot create, update or delete a product, and you cannot create a recurring invoice. Both of those are set up by a person in the administration, deliberately, and the API exists to issue documents against them, email them, settle them, and export who bought what. Reading the connector as a store API leads to the wrong flows; reading it as an invoicing ledger for a Czech seller leads to the right ones.

FlowRunner agents issue all nine document kinds through one operation, raise the two that need a parent link through their own, maintain the address book, and page the ledger with a moving date. Settling a document and emailing it to a customer are both real world acts with a tax document attached, which is why the connector's more consequential calls are the natural place for human-in-the-loop rather than an afterthought bolted on later.

Without FlowRunner

Documents issued on memory An invoice goes out when someone remembers the customer is waiting for one

State hidden in a number Whether a document is paid, emailed or canceled sits in a bit field nobody reads by hand

Advances closed by retyping Turning an advance invoice into a final one means keying every line again into a new document

With FlowRunner

A sweep with a moving date The ledger is worked on a cadence, from the last issue date forward, without a person starting it

State read as state Flags are decoded per document, so paid, emailed and canceled are separable in a condition

Final invoices carry their lines The agent repeats the line items SimpleShop does not copy forward, so the amount is right

Use Case Scenarios

Advance invoices closed without a person retyping the lines

The agent sweeps Search Documents for advance invoices whose payment has landed, then calls Create Final Invoice with the parent link and, critically, with every line item repeated. SimpleShop does not copy the lines forward, so an omission produces a final invoice for the wrong amount rather than an error, and the connector's shape makes that explicit rather than leaving it to be discovered. The flow also does not assert on the parent link in the same run, because the platform marks the relationship roughly an hour later. The document is issued now; the check that it linked runs on the next sweep.
Payment matching against the bank feed

A statement lands in Google Sheets or is read from the finance system. The agent pages Search Documents for unpaid rows, matches on amount, variable symbol and customer, and calls Mark Document Paid on each clean match. Send Document Email then delivers the settled document where the account is set up to do that. What does not match cleanly goes to a channel in Slack as a short list, not as an export. The controller works the exceptions instead of working the whole statement.
The address book and the buyer list, kept current

Search Contacts and Get Contact keep customer records in step with the CRM, with Create Contact and Update Contact writing back the corrections that come from sales. Export Product Buyers answers the question the marketing team actually asks, which is who bought a given product, and the result flows into Brevo or Klaviyo as a segment. The ledger stays the source of truth for who paid, and the marketing tool stops holding a stale copy of it.

Human-in-Loop Highlight

Delete Recurring Invoice is the sharpest gate on this connector, and the reason is an absence rather than a warning. SimpleShop offers Get, Update and Delete for a recurring invoice and no create at all: the template is built by a person in the administration, so once a flow deletes one, nothing in this connector can put it back. Deleting the template also ends the billing it drives. So a cleanup agent that finds a recurring invoice for a customer who churned assembles the case instead of acting on it: "Recurring invoice 2211 bills Nováková s.r.o. 4,800 monthly and has issued eleven documents, the last one 34 days ago. The contract record says the customer ended in June. Delete the template, or update it? There is no create operation, so a deletion has to be rebuilt by hand in the administration." The controller answers. The agent can gather every fact in that message in seconds. Choosing to remove something the software cannot recreate is a different kind of act, and it belongs to a person.

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

28 actions

Connection

Test Connection Verifies the credentials and reports which half is wrong when they fail, because SimpleShop distinguishes credentials that never arrived from credentials it rejected.

Documents

Create Document Issues any of the nine document kinds, with Type choosing between them. Only the line items are genuinely required; everything else falls back to the account defaults.
Create Final Invoice Issues an invoice whose parent is the advance invoice it settles. The lines have to be repeated here, because SimpleShop does not copy them forward from the advance.
Create Credit Note Issues a credit note whose parent is the document it corrects. The correction path for a document that has already gone to the customer.
Get Document Reads one document with its lines, totals and flags. The gather step before any decision about settling, correcting or emailing it.
Update Document Changes an issued document. Used for the corrections that do not warrant a credit note, and worth reading the document first so nothing is dropped.
Delete Document Removes a document from the ledger. Distinct from canceling it, which is a flag the document carries rather than a deletion.
Search Documents Pages the ledger by date, type, contact and flags. The workhorse of every scheduled sweep here, since there is no event stream to subscribe to.
Send Document Email Emails a document to its customer from SimpleShop. A real delivery to a real inbox, so it is a natural point to slow a flow down.
Mark Document Paid Records a document as settled. The write that closes the loop between the bank feed and the ledger.
Get Document Sale On Name Reads the sale-on-name detail recorded against a document. Used where the buyer of record differs from the paying party.

Recurring Invoices

Get Recurring Invoice Reads a recurring invoice template, including what it bills and how often. The only way to inspect a subscription this account is running.
Update Recurring Invoice Changes a recurring invoice template. The reversible alternative to deleting one, and usually the right answer.
Delete Recurring Invoice Removes a recurring invoice template and the billing it drives. There is no create counterpart in this API, so this is the operation this page puts a person in front of.

Contacts

Create Contact Adds a customer to the address book. Used when an order or a CRM record names someone the ledger does not hold yet.
Get Contact Reads one contact with its billing details. The lookup behind matching a payment or addressing a document.
Update Contact Changes a contact record. Used to push corrections from the CRM into the ledger so documents carry the right billing details.
Delete Contact Removes a contact from the address book. Used in cleanup flows and in erasure requests.
Search Contacts Pages the address book with filters. Used for reconciliation sweeps and for resolving a name into an identifier before issuing a document.

Products and Settings

Get Product Reads a product. Read only by design: SimpleShop keeps product management in the administration, so a catalog sync is not a flow this API supports.
List Payment Methods Lists the payment methods configured on the account, with the identifiers a document has to reference.
List Number Series Lists the numbering series the account issues documents into. Used to put a document in the right series rather than the default one.

Export

Export Product Buyers Exports who bought a given product. The operation that answers the marketing question directly instead of reconstructing it from the whole ledger.

Frequently Asked Questions

What can FlowRunner do with SimpleShop?

FlowRunner agents can run Test Connection, Create Document, and Create Final Invoice in SimpleShop, plus 25 more actions.

Does connecting SimpleShop to FlowRunner require OAuth?

No. SimpleShop connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can SimpleShop trigger a FlowRunner workflow automatically?

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

Start building with SimpleShop

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us