Square, in every client’s workflows.

Create a customer, update a customer, or start when a payment lands, with the client’s own Square account.

Triggers: 3start a workflow
Actions: 2steps in a workflow

Start a workflow when something happens in SquareBeta

By webhook where Square sends one, by checking where it does not. A webhook is checked once a day to see it is still on, and if Square turns it off the alert carries a Reconnect button.

A payment landsPolledA payment completed at the account’s default location (in person, online or on an invoice), checked every 5 minutes; once per payment. The token needs PAYMENTS_READ.
A new bookingWebhookA new appointment, within seconds. The token needs APPOINTMENTS_READ. The customer’s name and email are not in the event: find the customer by its ID in a step.
A new customerWebhookA customer added to the Square directory, within seconds (at the till, online or by a booking). The token needs CUSTOMERS_READ.

Do it in Square

A step with its own fields: values from the run go in by name, and what Square answers is there for the next step.

Create a customerA new customer in the client’s Square directory.
Update a customerChange a customer’s details, found by id. Fields left empty keep their value.

Connect the client’s Square

On the client’s page in Thrum: Add credential, type Square access token.

developer.squareup.com → the client’s application (their own account) → Credentials → Production access token. A personal access token for the client’s own account needs no Square review.

The key is stored encrypted and bound to that client: another client’s workflow cannot use it, and no template or pack copies it.

Square’s API documentation

Watched like everything else

When Square stops answering or refuses the client’s key, you hear about it, and your client does not.

A failing request: Tried 3 times, 5 seconds apart and doubling, only for errors a retry can fix
A service that asks for a pause: Given it, up to an hour
Requests at once, per account: 2, per worker; the rest wait their turn
Timeout: 15 seconds, unless the step sets its own
Private and internal addresses: Refused, on every redirect too
The client’s key: Encrypted, bound to the client, and kept out of every run record
A step that keeps failing: Marks the workflow Degraded and alerts you, not the client

Square and its logo are trademarks of their owner, used here only to say what Thrum works with; no endorsement is implied.

Thrum is cooking.

Get early access and you’ll be among the first in. Early members get a launch perk.

Get early access See pricing