Connector · Payments
Shopify, in every client’s workflows.
Create a customer, update a customer, or start when a new order comes in, with the client’s own Shopify account.
- Triggers
- 2start a workflow
- Actions
- 2steps in a workflow
Start a workflow when something happens in ShopifyBeta
By webhook where Shopify sends one, by checking where it does not. A webhook is checked once a day to see it is still on, and if Shopify turns it off the alert carries a Reconnect button.
- A new order comes inPolledA new order in the store, checked every 5 minutes. The app needs the read_orders scope.
- An order is paidPolledAn order whose payment went through, checked every 5 minutes; once per order. The app needs the read_orders scope.
Do it in Shopify
A step with its own fields: values from the run go in by name, and what Shopify answers is there for the next step.
- Create a customerA new customer. Shopify refuses a duplicate email; the run fails and names it.
- Update a customerChange a customer’s name, email, phone or note, found by id. Fields left empty keep their value. Tags are not changed here: Shopify would replace them all.
Connect the client’s Shopify
On the client’s page in Thrum: Add credential, type Shopify custom app token.
Only for a store that already has an admin-created custom app. In the client’s Shopify admin: Apps → Develop apps → the app: its Admin API scopes must include write_customers and read_orders; the token is under API credentials (shown once when it is made; if it is no longer shown, generate a new one).
The key is stored encrypted and bound to that client: another client’s workflow cannot use it, and no template or pack copies it.
Watched like everything else
When Shopify 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
Shopify 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.