Pack · E-commerce
Dropshipping store pack
A dropshipping store holds no stock: a supplier ships each order, on thinner margins.
Start the 14-day trial, then find it under Templates → Library. It installs into the client you choose, switched off, with its checklist.
- Workflows
- 3
- Steps
- 12
- Client fills in
- 8
- Starts
- From Shopify, Zendesk or Intercom, within 5 minutes
UsesBeta
The workflows in this pack
Built for online stores.
01
Order hand-off for online stores
When an order is paid, send it to the supplier, add it to the order log, and tell the team.
- Starts whenAn order is paid
- EmailSend to the supplier
- App stepAdd to the order log
Google Sheets
- App stepTell the team
- Starts whenAn order is paid
02
Ticket triage for online stores
Acknowledge every support ticket at once, sort it by topic and urgency, page someone for the urgent ones, and tell the team.
- Starts whenA ticket is opened
- AgentSort the ticket
- Zendesk: Update a ticketAcknowledge it
- BranchUrgent?
- IfIf yes
- TextText whoever is on call
- IfIf no
- App stepPost to the team
- Starts whenA ticket is opened
03
Conversation triage for online stores
Sort every new conversation in the support chat inbox by topic, page someone for the urgent ones, and put each in front of the team that handles it.
- Starts whenA new conversation comes in
- AgentSort the message
- BranchUrgent?
- IfIf yes
- TextText whoever is on call
- IfIf no
- App stepPost to the team
- Starts whenA new conversation comes in
What each client fills in
- Supplier email
- Where orders are sent to be fulfilled.
- Order log sheet ID
- The Google Sheet orders are logged to.
- Team channel
- The Slack channel that hears about it.
- Business name
- How messages sign off.
- AI model
- The model the client’s key can use.
- Topics
- Comma-separated: billing, bug, how-to, account.
- When a person replies
- One sentence the customer reads: “We answer within one working day.”
- Owner’s mobile
- Texted when something needs a person now.
The accounts it needs
Each is the client’s own, stored encrypted and never copied between clients. Until one is added the client’s checklist shows it, and nothing runs.
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).
In your own Google Cloud project: enable the Google Sheets API, then IAM & Admin → Service accounts → Create → Keys → Add key → JSON, and paste the file here. Then share each client sheet with the service account’s email (…@….iam.gserviceaccount.com) as an Editor. The account is yours; no Google review is needed.
In the client’s Slack: api.slack.com/apps → Create New App → OAuth & Permissions → add the chat:write scope (and channels:history, plus groups:history for a private channel, for the message trigger) → Install to Workspace → copy the Bot User OAuth Token. Invite the app to the channel.
In the client’s Zendesk: Admin Center → Apps and integrations → APIs → Zendesk API → enable Token access → Add API token. The triggers make webhooks, which needs an admin’s email and token.
platform.claude.com → Settings → API keys → Create key, in the workspace that bills this client.
In the client’s Intercom: Settings → Integrations → Developer Hub → New app (for their own workspace, no review) → Authentication → copy the access token. The conversation trigger needs the app to be allowed to read conversations.
After you install it
It lands switched off. The client’s checklist holds exactly this:
- Connect the client’s Shopify, for “An order is paid”
- Connect the client’s Resend (email), for “Send to the supplier”
- Connect the client’s Google Sheets, for “Add to the order log”
- Connect the client’s Slack, for “Tell the team”
- Fill in Supplier email (Where orders are sent to be fulfilled)
- Fill in Order log sheet ID (The Google Sheet orders are logged to)
- Fill in Team channel (The Slack channel that hears about it)
- Connect the client’s Zendesk, for “A ticket is opened” and “Acknowledge it”
- Connect the client’s Anthropic, for “Sort the ticket”
- Connect the client’s Twilio (SMS), for “Text whoever is on call”
- Connect the client’s Slack, for “Post to the team”
- Fill in AI model (The model the client’s key can use)
- Fill in Business name (How messages sign off)
- Fill in Topics (Comma-separated: billing, bug, how-to, account)
- Fill in When a person replies (One sentence the customer reads: “We answer within one working day.”)
- Fill in Owner’s mobile (Texted when something needs a person now)
- Connect the client’s Intercom, for “A new conversation comes in”
- Connect the client’s Anthropic, for “Sort the message”
- Fill in Topics (Comma-separated, the team’s own: billing, booking, complaint, technical, sales)
Related templates
- PackE-commerceOwn-brand store packAn own-brand store makes or buys its own stock and ships it itself or through a fulfilment warehouse.
Google Sheets
3 workflows · 11 steps · 7 apps
- PackE-commerceSubscription store packA subscription store lives on recurring billing, so pauses, skips and cancellations matter more than one-off checkout.
Google Sheets
3 workflows · 14 steps · 7 apps
- PlaybookE-commerceApplicant intake for online storesAcknowledge every job application at once, check it against the must-haves, log it, and send it to whoever hires.
Google Sheets4 steps · 3 apps
Thrum is cooking.
Get early access and you’ll be among the first in. Early members get a launch perk.