Clover

Connect AI agents to Clover, the Fiserv point-of-sale platform. Agents read and create orders, inventory items, and customers, list payments, and pull merchant settings to automate retail and restaurant back-office work.

10 actions API key available

Clover website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

The nightly close-out starts after the store locks up

List Payments pulls the day's takings with amounts in minor currency units

List Orders pulls the day's orders with lineItems and payments expanded for category-level detail

The agent reconciles payments to orders and flags the gaps: open orders with no payment, voids, and refunds

The reconciliation summary posts to the owner's channel with flagged gaps on top

The pricing sheet diff shows tomorrow's menu changes waiting to go live

The owner approves each new item and price before it exists on the register

Create Item writes the approved items with price in cents and the correct price type

What This Integration Enables

For a shop or restaurant, the point of sale is the only system that knows the truth: what sold, when, for how much, paid how. Clover holds that truth, and most small operations leave it there, reconciling from memory and receipts. FlowRunner agents pull it out on schedule and put it to work: orders and payments read with Clover's filter expressions and Expand parameter for inline detail, inventory items listed and created, customers captured with structured contact details, and the merchant profile read for the currency and timezone that downstream logic needs. - Nightly reconciliation: payments matched to orders, gaps flagged, summary delivered before opening - Accounting flow: the day's sales mirrored into the books without an export ritual - Catalog sync: the register's items and an external catalog agreeing on names, SKUs, and prices - Customer capture: checkout contacts flowing into marketing lists while the visit is still fresh One convention runs through everything here: amounts are in the smallest currency unit, 450 means $4.50. Agents carry that convention consistently, and the [human-in-the-loop](/concepts/human-in-the-loop) gate on register writes exists for the day a number means something different than someone assumed.

Without FlowRunner

The POS knows, the office guesses What actually sold today lives in the register, and the books catch up whenever someone exports

Menu changes at the counter New items and price updates get typed into the terminal between customers, sometimes wrong

Checkout data goes nowhere Customers pay and leave; names, emails, and repeat behavior evaporate at the register

With FlowRunner

Close-out runs itself Payments and orders reconcile nightly, and the morning summary already names the gaps

Menu changes are reviewed, then live Items and prices flow from the planning sheet to the register after an approval, not a hunch

The register feeds the business Sales flow to accounting, items sync to the invoice catalog, and customers land in marketing

Use Case Scenarios

The close-out that beats the owner to the store

Every night, List Payments and List Orders pull the day with a createdTime filter, orders expanded with lineItems and payments. The agent totals by category, matches payments to orders, and appends the day to the revenue workbook in [Google Sheets](/integrations/google-sheets). Sales mirror into [QuickBooks](/integrations/quickbooks-online) for the books, and the summary posts to [Slack](/integrations/slack): gross, by category, payment method mix, and anything that did not reconcile. The owner reads the day over coffee instead of assembling it after close.

Menu and catalog, one truth in two systems

The invoicing catalog and the register drift apart in every small business until someone makes them agree. The agent runs List Items weekly and diffs the register against the accounting catalog: items missing on either side, price disagreements in cents, SKU mismatches. Discrepancies queue for review, and approved fixes flow in the right direction, Create Item for products missing from the register, catalog updates on the accounting side for the rest. Wholesale clients get invoiced from the same catalog the counter charges, and the two never quietly disagree again.

The counter becomes the top of the marketing funnel

A customer at the register agrees to join the list. The staff captures name and email, and the workflow runs Create Customer with the contact details in Clover's nested structure, then adds the person to [Mailchimp](/integrations/mailchimp-marketing) for the post-purchase sequence. A weekly pass over List Customers with Expand on email addresses reconciles the two lists. The shop that saw the customer face to face stops losing them to anonymity the moment the receipt prints.

Human-in-Loop Highlight

Create Item writes to the live register, and the register does not double-check. The price field is in minor units: 450 is $4.50 and 45 is 45 cents, and both are valid input. An item created wrong at 7 am sells wrong all day, at the counter, to real customers, and every transaction rings up the mistake again; discovering it at close-out means a day of margin gone or a line of overcharged regulars to make right. So in FlowRunner, register writes are drafted by agents and released by the owner: the approval screen shows each item's name, SKU, price type, and price rendered in dollars and cents next to the raw minor-unit value, so the decimal error dies in review instead of at checkout. The same review covers Create Order and Create Customer where they feed live operations, because the counter is production, and production changes ship with a sign-off.

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

10 actions

Merchant

Get Merchant Retrieves the merchant profile: name, address, currency, timezone, and settings, with Expand for related objects. The context read that downstream logic keys on.

Orders

List Orders Lists orders with Clover filter expressions like state=open or createdTime ranges, paginated, with Expand to inline lineItems, payments, discounts, and customers.
Get Order Retrieves one order's totals, state, and timestamps, expandable to full line-item and payment detail.
Create Order Creates an order shell with an initial state, note, or title, ready for line items and payments to attach.

Inventory

List Items Lists inventory items with filters, pagination, and Expand for categories, modifier groups, and stock.
Get Item Retrieves one item's name, price in minor units, price type, SKU, and code, with a searchable item picker behind the parameter.
Create Item Creates an inventory item with price in the smallest currency unit and a price type controlling checkout behavior. The register write this page's human gate exists for.

Customers

List Customers Lists the merchant's customers with filters and Expand for email addresses, phone numbers, addresses, and cards.
Create Customer Creates a customer with first and last name plus contact details in Clover's nested elements structure. The capture step at the top of the local marketing funnel.

Payments

List Payments Lists payments with filter expressions and pagination, amounts in minor units. The ground truth feed for reconciliation and revenue reporting.

Frequently Asked Questions

What can FlowRunner do with Clover?

FlowRunner agents can run Get Merchant, List Orders, and Get Order in Clover, plus 7 more actions.

Does connecting Clover to FlowRunner require OAuth?

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

Can Clover trigger a FlowRunner workflow automatically?

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

Start building with Clover

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

Start Building Free Talk to us