FlowRunner
PricingContact
Theme
Start Free

Square

Payments

Connect AI agents to Square. Agents charge cards and record payments, issue refunds, create and pay orders, publish invoices, sync catalog and multi-location inventory, manage customers and subscriptions, and reconcile payouts.

58 actions API key available
Square website ↗ Platform Documentation ↗ Capability data verified 2026-07-22
A signed order arrives from the sales flow
Agent builds line items from the catalog and previews totals with Calculate Order
Create Order opens the order, then Create Invoice drafts against it
Agent checks the draft's amounts and terms against the original quote
The account owner gets the draft summary with the due date and delivery method
A person approves the draft; only then does Publish Invoice make it payable and send it to the customer

What This Integration Enables

Square is where in-person and online commerce meet one ledger: payments, orders, catalog, multi-location inventory, invoices, subscriptions, and the payouts that land it all in the bank. FlowRunner agents work that whole surface. They charge cards on file and record cash or external tenders, run the authorize-then-capture flow when a hold should precede a charge, build and pay orders, draft and publish invoices, sync catalog items and stock counts across locations, manage subscription pauses and resumes, and reconcile payouts entry by entry. The division of labor is deliberate. Recording, syncing, and reconciling run unattended, because they are reversible and auditable. Refunding a payment, publishing an invoice to a customer, overwriting a stock count, or deleting a catalog item and everything under it are moves that destroy or commit value, and those wait for a person by design.

Without FlowRunner

Invoices keyed twice The quote lives in one system and gets re-typed into Square, with the discrepancies found by the customer
Payout mystery The bank deposit and the register disagree, and nobody can say which fees explain the gap
Catalog cruft Dead items linger for years because deleting anything in bulk feels too dangerous to attempt

With FlowRunner

Order to invoice in one motion Line items, taxes, and totals flow from the order into a draft that a person approves before it sends
Payouts broken to entries Every deposit reconciled against its individual charges, refunds, and fees
Catalog cleanups with evidence Purges proposed with sales and inventory context, and executed only after sign-off

Use Case Scenarios

Signed order to published invoice

When a signed order lands, the agent assembles the line items, referencing catalog variations where they exist, and runs Calculate Order to preview totals, taxes, and discounts before anything is created. It then opens the order with Create Order and drafts against it with Create Invoice. The draft goes to the account owner with the amounts lined up against the quote. On approval, Publish Invoice sends it by email or returns the public payment URL, and the agent tracks Get Invoice until the balance clears.

Payout reconciliation into the books

Each morning the agent pulls new deposits with List Payouts and expands each one with List Payout Entries, which itemizes the charges, refunds, and fees behind the total. It posts each entry to the reconciliation workbook in [Google Sheets](/integrations/google-sheets) and mirrors the summary into [QuickBooks Online](/integrations/quickbooks-online). A payout whose entries do not tie to the day's payments gets flagged to the finance channel with the specific entries that disagree, so the person investigating starts at the discrepancy instead of the haystack.

Catalog cleanup with a cascade gate

Quarterly, the agent hunts dead weight: Search Catalog finds candidate items, Get Inventory Count confirms zero stock across locations, and Search Orders confirms no recent sales. It assembles the purge list, and for each item it spells out the cascade, because Delete Catalog Object permanently removes an item and every variation under it. The owner strikes anything worth keeping, approves the rest, and the agent executes the approved deletions and files the record of what was removed and why.

Human-in-Loop Highlight

Delete Catalog Object is the quiet destroyer in this connector: deletion is permanent, and deleting an item takes every one of its variations with it. A bulk cleanup that guesses wrong does not produce an error message; it produces a menu item that vanishes from every register at every location mid-shift. So the FlowRunner cleanup agent never deletes on its own conclusion. It posts its evidence to the channel: "14 catalog items with zero inventory at all locations and no sales found in order history. Deleting the item 'Seasonal Latte' also deletes its 3 size variations, permanently. Approve the full list, or strike items to keep?" The owner strikes two items that are seasonal, not dead, and approves the rest. The agent deletes exactly what was approved and logs the object IDs Square returns for the record. [Human-in-the-loop](/concepts/human-in-the-loop) is the difference between a tidy catalog and an outage at the register.

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

58 actions

Locations

2
  • List Locations Enumerate every business location with its currency, timezone, and capabilities. Location IDs anchor payments, orders, invoices, and inventory operations.
  • Get Location Load one location by ID before running location-scoped operations.

Payments

6
  • Create Payment Charge a card on file, or record cash and external tenders taken outside Square. With autocomplete off, the payment is only authorized until a later capture, which is how approval gates get built into charging.
  • List Payments Pull payments by time window and location.
  • Get Payment Load one payment's full detail, including fees and the version token updates require.
  • Update Payment Adjust an approved payment's amount or tip before capture.
  • Complete Payment Capture an authorized payment, the second half of the approval-gated charge.
  • Cancel Payment Void an approved payment and release the hold on the buyer's funds.

Refunds

3
  • Refund Payment Return all or part of a completed payment. Money out, processed asynchronously, and the classic step a named approver owns.
  • List Refunds Audit refunds across the account.
  • Get Refund Track an individual refund through pending, completed, rejected, or failed.

Orders

7
  • Create Order Open an order with catalog or ad hoc line items.
  • Get Order Load an order in full.
  • Update Order Apply sparse updates against the order's current version.
  • Search Orders Find orders across locations by state and date window, the backbone of reporting and reconciliation flows.
  • Pay Order Settle an open order with approved payments.
  • Calculate Order Preview a cart's totals and taxes without creating anything.
  • Clone Order Copy an order into an editable draft.

Catalog

6
  • List Catalog Browse items, categories, taxes, and discounts page by page.
  • Get Catalog Object Load one object with related objects expanded when needed.
  • Search Catalog Find catalog objects by name, type, or attribute.
  • Upsert Catalog Item Create or update catalog objects, from a simple name-and-price item to a full CatalogObject with multiple variations.
  • Delete Catalog Object Permanently delete an object and all of its children. The cascade that makes catalog cleanup a human decision.
  • Get Catalog Info Read the account's catalog limits and measurement metadata before batch operations.

Customers and Cards

10
  • Create Customer Create a customer profile new charges and invoices attach to.
  • Update Customer Maintain profile details as they change.
  • Delete Customer Delete a profile. Deletion is permanent, and therefore gated in cleanup flows.
  • List Customers Enumerate customer profiles page by page.
  • Get Customer Load one profile in full.
  • Search Customers Find customers by email, phone, or reference with fuzzy matching.
  • Create Card Save a card on file for later charging.
  • List Cards Enumerate the cards stored against customers.
  • Get Card Read a card's masked details.
  • Disable Card Permanently disable a card that should never be charged again.

Invoices

8
  • Create Invoice Draft an invoice against an order.
  • Update Invoice Refine a draft with sparse updates before it goes out.
  • Publish Invoice Make a draft payable and deliver it, by email or as a shareable payment URL. The customer-facing send a person approves.
  • List Invoices Track invoices by location through their full status lifecycle.
  • Get Invoice Load one invoice with its payment requests and current status.
  • Search Invoices Find invoices by location and customer.
  • Cancel Invoice Cancel a published invoice so it can no longer be paid.
  • Delete Invoice Permanently delete a draft that should never publish.

Inventory

4
  • Get Inventory Count Read current stock for one variation, per location and state.
  • Batch Retrieve Inventory Counts Read stock for many variations in a single call.
  • Adjust Inventory Move quantity between states, such as In Stock to Sold, or receive new stock. The delta-based write for everyday movements.
  • Record Physical Count Overwrite the calculated quantity with an absolute count after a stocktake. Because it replaces rather than adjusts, flows surface large variances to a person before writing.

Subscriptions

7
  • Create Subscription Enroll a customer in a plan variation, charging the card on file automatically.
  • Get Subscription Load one subscription's status and billing anchor.
  • Search Subscriptions Find subscriptions by location and customer.
  • Update Subscription Manage subscription details as terms change.
  • Cancel Subscription End billing at the paid-through date.
  • Pause Subscription Pause billing for a defined number of cycles.
  • Resume Subscription Resume a paused subscription on a schedule.

Payouts

3
  • List Payouts Track transfers to the bank as they land.
  • Get Payout Load one payout's total and status.
  • List Payout Entries Itemize a payout into its component charges, refunds, and fees, the raw material of daily reconciliation.

Team

2
  • Search Team Members Look up team member profiles by location and status.
  • Get Team Member Load one member's profile, used to attribute activity and route approvals to the right person.

Frequently Asked Questions

What can FlowRunner do with Square?

FlowRunner agents can run List Locations, Get Location, and List Payments in Square, plus 55 more actions.

Does connecting Square to FlowRunner require OAuth?

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

Can Square trigger a FlowRunner workflow automatically?

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

Start building with Square

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