Integrations · E-commerce & payments

Square in the conversation.

Point-of-sale, payments and catalogue for businesses that also sell in person. Connect it once and your copilot works with payments, orders, customers, catalogue items and locations without leaving the thread — and your workflows can act on it while the customer is still typing.

Start free trial →All integrations

No credit card required · 7-day free trial

Square

E-commerce & payments

01 · COPILOT

Ask for it in plain language. It does the Square part.

Copilot rides inside the inbox. With Square connected it reads payments, orders, customers, catalogue items and locations and acts on them from the same panel as the conversation — no second tab, no copying an order number across.

Look up a payment or an order
Find a customer and their purchase history
Read catalogue items and stock by location
Issue a refund against a payment
List transactions for a location and date range

What a specific connection exposes is decided by Square, not by us: Settings → Apps lists the real tools your connection carries, each with its own switch.

02 · WORKFLOWS

Something happens in Square. A workflow starts.

Once Square is connected, its events show up in the workflow editor's trigger picker, and the fields the event carries become variables every later step can read — so the message you send is written from what actually happened.

A payment is completed
A refund is issued

The picker is the authority on which events your Square connection publishes — these are the kinds that apps of this sort emit.

03 · THE AI AGENT STEP

One step that decides which Square tools to call.

A workflow's AI Agent step runs a bounded tool-calling loop over the apps you have connected and returns an object whose fields you declared. So "find the record, check the status, and give me status and owner" is one step rather than four — and the fields it returns are available to every step after it.

You declare the output

The rows you name become the variables downstream steps read, so a branch can test what Square said.

You cap the effort

A step budget and a model tier per node — the loop stops where you told it to.

Only what you switched on

The loop can call the Square tools you left enabled and nothing else.

What teams do with it

Two ways Square earns its connection.

In-store purchase, online question

A customer who bought in the shop messages later — the agent finds the Square payment and answers the warranty question with the real receipt.

Per-location answers

A multi-branch business gets stock and hours from the Square location the customer actually walked into.

Setup

Connect Square in about a minute.

1
Open Settings → Apps
It is open to everyone in your organization, not just admins — which apps your copilot can reach is part of doing the job.
2
Find Square in Browse
The catalogue runs to hundreds of apps and is searchable. Connect Square from its card.
3
Authorize with your own Square account
You sign in on Square's own screen and approve the access. The connection carries that account's permissions — no API keys are pasted into Cloodot.
4
Choose the tools it may call
Open the connection and switch off anything you would rather it never touched. A tool you switch off is out of reach from the next question onward.

Open Settings → Apps →

Square questions.

How do I connect Square to Cloodot?

Open Settings → Apps in Cloodot, switch to Browse, and search for Square. Connecting it opens Square's own sign-in and consent screen; when you come back, the app is listed as Connected and your copilot can use it. Nothing is installed and no keys are pasted into Cloodot.

What can Cloodot do in Square?

Work of this kind: look up a payment or an order; find a customer and their purchase history; read catalogue items and stock by location; issue a refund against a payment; list transactions for a location and date range. The exact list depends on what your Square account is allowed to do — Settings → Apps shows every tool the connection actually exposes.

Can I limit which Square tools Cloodot may use?

Yes. Open the connection and every tool it exposes is a switch, searchable by name. A tool you switch off is out of reach from the next question onward, so a read-only Square connection is a matter of leaving the writes off.

Can an event in Square start a Cloodot workflow?

Yes. Events like a payment is completed, a refund is issued appear in the workflow editor's trigger picker once Square is connected, and the event's own fields become variables the rest of the workflow can read.

Who in my team can connect Square?

Anyone in the organization — Apps is not restricted to admins and owners, because which apps a copilot can reach is part of doing the job. The connection carries the permissions of the Square account that authorized it, so a e-commerce & payments connection is only ever as broad as the account behind it.

More e-commerce & payments