Square
POS + payment ops on Square in your workflows
Square is the payment-and-POS platform that powers a lot of brick-and-mortar businesses (and increasingly online ones too, Square Online Store competes with Shopify in the SMB segment). Eight actions cover both payment and customer surfaces: Create Payment, Refund Payment, List Payments, Create Customer, Search Customers, Create Invoice, List Locations (Square's multi-location stores), Search Orders. No native triggers today (Square emits webhooks but per-event configuration is needed; native triggers ship in the next release). The integration uses Square OAuth with the right merchant scopes. Common patterns: a Stripe Online order syncs into Square as a corresponding offline-receipt-only customer record for unified reporting across both rails; or a Square POS sale at a specific location triggers a Slack notification to the store manager (configure via Square's native webhooks pointing at a Tiny Command HTTP webhook trigger).
Do anything Square can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Create Square Customer | Creates a customer with email, name, address. For "POS customer → push to Square Customers for repeat-business loyalty tracking" workflows. |
| Create Square Invoice | Creates an invoice with line items, customer, due date. For service-business workflows where Square is the payment processor but the invoice is generated externally. |
| Square Create Payment | Charges a saved customer card or processes a payment with provided source. For "external order completed → charge via Square" workflows. |
| List Square Locations | Returns the merchant's locations. Useful for resolving location IDs and for multi-location reporting workflows. |
| List Square Payments | Paginated payments with filters by date, location, status. For revenue-reporting workflows and for accounting reconciliation. |
| Refund Square Payment | Refunds full or partial. For "customer requested refund via support" or "fraud detection → auto-refund" workflows. |
| Search Square Customers | Lookup by email, phone, name. For "find existing customer record by phone" POS workflows. |
| Search Square Orders | Returns paginated orders with filters by date, location, state. For "today's orders" rollups and for sync to accounting systems. |
Pre-built Square workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Square once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Square field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Square integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Square to Tiny Command?
What Square triggers does Tiny Command support?
What Square actions can I run from a workflow?
Is the Square integration real-time?
Do I need to write code to use Square with Tiny Command?
How much does the Square integration cost?
More e-commerce apps people connect.
Same category as Square, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Square.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
