Square, without opening Square.
Payments, orders and invoices from the counter and the online store.
- Free to start
- No card
- Every write waits for you
- Your own account, not a shared login
Ask in your own words.
Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own Square details, and Ray takes it from there.
@Ray what did we take at the shop yesterday?
@Ray refund that customer's last order.
@Ray which location did the most business last week?
@Ray are we running low on anything in the shop?
What Ray can and cannot do in Square
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
24 reads wired, 6 actions that wait for a human.
Runs on its own
What Ray reads in Square
- Payments, orders, invoices, refunds, and disputes
- Customers, locations, catalog, and inventory movement
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Refund a payment, under a daily ceiling
- Add or update a customer
- Create or update an order
- Save a catalog item
Ray posts a card showing exactly what it is about to do. Nothing happens until someone clicks approve, and no setting turns that off.
Not on the list
Things Ray is never handed
These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.
- Read a customer's stored card
- Run raw GraphQL queries against your account
- Charge a card or pay an order
Exactly what Ray will ask you to approve.
Not a category of permission. These are the Square actions Ray can take, each one stopping in the thread with the real content before it happens.
- Add Square customer
- Create Square order
- Refund Square payment
- Update Square customer
- Update Square order
- Save Square catalog item
Add Square customer
Showing Given name, Note, Email address and Phone number, each carrying the exact content that will land.
How Ray works with Square
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Square
One click, right where you asked. Ray posts a connect card, you authorise Square with your own account, and the work you asked for picks up where it left off.
- 02
Ask in plain words
In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.
- 03
Approve, and it lands
Reading runs on its own. Anything that creates, sends or spends stops first and shows you the exact content.
Priya
@Ray the checkout bug is back. Take a look in Square, and tell Dana it is being looked at.
Add Square customer
- Waiting on
- your approval
Ray uses Square together with the rest of your tools.
One ask can read Square, cross-reference what is in these, and land the finished result back in the thread. Not four connectors taking turns, one teammate with one memory.
What does connecting Square to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Square and it can do the Square part of a request without anyone leaving the conversation: read what it needs, draft the change, and post it for approval before anything is written.
It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.
Every person on the team connects their own Square account, so Ray can only reach what that person can already reach, and the history in Square shows who actually asked.
Security and permissions
- You authorise Square on its own login screen. Your password never passes through Ray.
- Writes are gated in the execution path, not by a prompt. There is no setting that grants blanket approval.
- Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
- Disconnect Square in a message, or uninstall Ray and every connection it held is revoked.
Square and Ray, answered
The questions teams ask before they connect Square. Every answer is how this integration is built rather than a promise about it.
More finance, billing & signatures integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in Square.
Free to start, no credit card, and it asks before it acts.