SalesThumb has direct integrations for the major tools (Stripe, QuickBooks, Google Calendar, Twilio, SendGrid). For everything else, use Zapier or Make.com. Here are the 10 automations shops most often build.
Setup basics
Settings → Integrations → API → Generate API key. Copy the key. Paste into Zapier's "SalesThumb (Beta)" auth screen or Make.com's "SalesThumb" module.
The API exposes: - Customers (create, update, search) - Vehicles - Quotes (create, send) - Jobs (status events) - Invoices (created, paid) - Webhooks for: new lead, quote sent, deposit paid, job completed, review submitted
Pattern 1 — New Google review → Slack alert
Trigger: SalesThumb webhook "review.created" Action: Slack "Send message" → channel #wins → "🎉 New 5-star review: {customer_name} — {body}"
Why: surfaces wins to the team in real time. Free morale boost.
Pattern 2 — Quote sent → CRM update
Trigger: SalesThumb webhook "quote.sent" Action: HubSpot/Salesforce/Pipedrive → Update deal stage to "Quote Sent" + log activity
Why: keeps your CRM source-of-truth aligned with what's happening in the shop.
Pattern 3 — Invoice paid → Mailchimp tag
Trigger: SalesThumb webhook "invoice.paid" Action: Mailchimp → Add tag "Paid Customer" to subscriber Action 2 (optional): Mailchimp → Add to "Past Customers" automation
Why: enables post-job email sequences (reviews, referrals, recoating reminders) via Mailchimp if you prefer it over native SalesThumb sequences.
Pattern 4 — New lead from website form → SalesThumb customer
Trigger: Typeform/Webflow form submission Action: SalesThumb API → Create customer with name + phone + email
Why: any web lead lands in your shop's customer database instantly. Front desk can follow up.
Pattern 5 — Calendar event created externally → SalesThumb block
Trigger: Google Calendar "New event" (in a specific calendar like "Personal Out-of-Office") Action: SalesThumb API → Block tech availability for that window
Why: more granular than the built-in 2-way sync if you want to block specific calendars only.
Pattern 6 — Daily revenue → Notion / Google Sheets
Trigger: Schedule "Daily at 11:59 PM" Action: SalesThumb API → Get today's revenue, job count, close rate Action 2: Google Sheets → Append row OR Notion → Create page
Why: daily numbers persist for historical analysis without leaving your existing dashboard.
Pattern 7 — Stripe payout → Bookkeeper email
Trigger: Stripe webhook "payout.created" Action: Gmail → Send to bookkeeper with payout amount + breakdown
Why: bookkeeper has a real-time feed of money landing in bank. Reconciliation is one-click.
Pattern 8 — Customer SMS reply contains "URGENT" → Owner phone call
Trigger: SalesThumb webhook "sms.received" Filter: Body contains "urgent" or "emergency" or "ASAP" (case insensitive) Action: Twilio → Send SMS to owner OR PagerDuty → Trigger incident
Why: legitimate urgencies break through during off-hours. Won't flag every inbound.
Pattern 9 — Job completed → Auto-create Asana task
Trigger: SalesThumb webhook "job.completed" Action: Asana → Create task in "Post-job follow-ups" project, assign to manager, due in 3 days
Why: structured follow-up that doesn't rely on owner remembering.
Pattern 10 — Negative review → Owner phone call
Trigger: SalesThumb webhook "review.created" Filter: Rating is 1, 2, or 3 Action: Twilio → Send urgent SMS to owner with customer name + review text
Why: a 1-3 star review needs immediate attention. Don't wait until morning.
Common gotchas
- Rate limits: SalesThumb API allows 60 req/min per key. If your automation exceeds this, you'll get 429s. Use webhooks for high-volume scenarios.
- Webhook retries: SalesThumb retries failed webhooks 5 times with exponential backoff. If your endpoint is down for >30 minutes, you'll miss events.
- PII: be careful what you send to external systems. Don't pipe customer phone numbers to a Google Sheet that's broadly shared internally.
Where to find templates
We maintain a Zapier templates gallery: zapier.com/apps/salesthumb. Same for Make.com. About 25 templates ready to clone.