Disclosure: Some links in this article are affiliate links. If you purchase through them, we may earn a small commission at no extra cost to you.
The math: Time to implement: ~15 min | Tasks automated: chat-to-dispatch entry | Weekly time reclaimed: ~1-2 hours
- No direct Tidio-to-Jobber link exists. Make.com bridges them — check Make’s pricing page for current rates, but most operators start free.
- Make.com maps finished chat transcripts into Jobber job requests automatically.
- Typical operators reclaim 1-2 hours per week they spent re-typing chat leads.
You’re back at the truck at 7 PM and three people have already typed their name, address, and problem into your Tidio chat widget. None of that landed in Jobber. This tutorial fixes that in about 15 minutes.
Why There’s No Direct Connection (And What to Use Instead)
Tidio and Jobber do not talk to each other natively.
Most software directories list both tools and imply a simple click-to-connect experience. That is not reality. As of May 2026, neither Tidio’s integration marketplace nor Jobber’s lists the other as a partner.
Tidio is a website chat widget that captures visitor messages in real time. Jobber is field service management software built for trades like plumbing, HVAC, and landscaping. Both have APIs (application programming interfaces — the behind-the-scenes hooks that let software share data). Neither has built a direct connector to the other.
Make.com bridges them. Make is a visual automation builder: drag boxes onto a canvas, connect them with lines, no code. The free tier gives you 1,000 credits per month and two active scenarios — plenty for a single Tidio-to-Jobber connection. If you’ve used the drag-and-drop editor in Canva, the learning curve is similar.
The real bottleneck is deciding which Tidio chats qualify as real job requests. A homeowner describing a leaking water heater at 9:47 PM? That goes into Jobber. A bot exchange that never gets a reply? It should not. The setup below handles both cases.
| Task | The Old Way | The AI Way | Time Saved |
|---|---|---|---|
| New chat lead entry | Read chat transcript, open Jobber, type name/phone/address, create request | Make.com reads finished Tidio chat, creates Jobber Client Request automatically | 3-5 min per lead |
| After-hours lead capture | Check Tidio next morning, hope you remember | Request appears in Jobber before you wake up | Eliminates forgotten leads |
The 3-Step Setup Guide: Tidio to Jobber Flow
Before starting, confirm: (1) You have a Tidio account with access to the Flows or automation settings. (2) You have a Jobber account on any paid plan (Jobber does not offer a free tier; a 14-day trial works). (3) You have a Make.com account (free tier is fine to start).
Step 1: Create a Make Webhook and Connect It to Tidio (5 minutes)
A webhook is a small alert that fires when something happens — think of it as Tidio tapping Make on the shoulder and saying “a chat just ended.”
Log into Make.com and create a new scenario. For the first module, search for “Webhooks” in Make’s app directory and select “Custom webhook.” Make generates a unique webhook URL for you. Copy it.
Inside your Tidio dashboard, go to Settings → Integrations (or look for a “Webhooks” or “Developer” tab — the exact label varies by plan). Paste the Make webhook URL as the endpoint and save. Make’s webhook documentation covers the technical details if you get stuck: Make webhooks guide.
If you do not see a Webhooks option in Tidio, your plan may not include it. In that case, use Make’s HTTP → Make a request module to poll the Tidio API at a scheduled interval instead of waiting for a push. Either approach lands the same data in Jobber.
You will know it worked when: you close a test chat in Tidio and Make shows “Successfully determined” on the Custom Webhook module within 60 seconds.
Step 2: Filter and Map the Data (5 minutes)
Not every Tidio chat is a real lead. Add a filter between the Tidio module and the Jobber module in Make. A filter is a rule that says “only continue if the data meets these conditions.”
Set the filter to check that the visitor’s name or email field is not empty. This blocks bot-only conversations and abandoned chats from cluttering your Jobber board. If your Tidio Flows collect a phone number, add that as an additional condition.
This is the step most guides skip. Without this filter, you end up with half-empty Client Requests in Jobber that waste more time than they save. Spend two minutes here and your dispatch board stays clean.
You will know it worked when: you run a test with a fake chat that has no name and Make stops the scenario at the filter, showing “The operation was filtered out.”
Step 3: Create the Jobber Client and Request (5 minutes)
Add a Jobber module after the filter. The recommended sequence is two actions: first “Search Client” (to check whether this contact already exists), then either “Update Client” or “Create Client” depending on the result, and finally “Create Request” linked to that client record.
Connect your Jobber account using OAuth (a secure login handshake where you grant Make permission to act on your behalf). Follow the prompts, it takes about 90 seconds.
Map the incoming Tidio fields: visitor name to Client Name, email to Email, phone to Phone, and the chat transcript or summary to Request Details/Notes. The notes field is where you or your office manager reads what the customer actually described.
Save the scenario. Turn it on.
You will know it worked when: you send a test chat through your website’s Tidio widget with a name and phone number, close the chat, and within two minutes a new request appears in Jobber under the correct client record.
For a deeper walkthrough on connecting Make to Jobber specifically, our guide on does Make.com integrate with Jobber covers authentication, error handling, and quota management in detail.
What This Connection Actually Costs You
The short version: roughly $9-10 per month on top of what you already pay for Tidio and Jobber.
Make.com’s free tier includes 1,000 credits per month and two active scenarios. Each run of this three-module scenario (trigger, filter, create request) uses a small number of credits—typically 1-3 credits per execution. For most home service businesses handling 50-200 chat leads per month, you will stay well within the free tier.
Get Your Free AI Tools Starter Kit
Take the 2-minute quiz to find your AI match — plus get the tools, checklist, and 50 prompts matched to your business type.
Take the Quiz →If your volume pushes past 1,000 credits, Make.com’s Core plan runs $9/month for 10,000 credits. That gives you headroom for roughly 3,000-5,000 Tidio-to-Jobber transfers per month—far more than most single-location operations will ever need.
Here’s the real cost breakdown:
| Tool | Free Tier Covers You? | Paid Cost If Needed |
|---|---|---|
| Make.com | Yes, up to ~300-500 transfers/month | $9/month (Core plan) |
| Tidio | Free tier = 50 conversations/month | $29/month (Starter) |
| Jobber | No free tier—you’re already paying | $0 additional |
The hidden cost most people miss is not a subscription fee. It is the 15-20 minutes you spend maintaining the scenario each quarter. Jobber occasionally updates its API, and Make.com modules reflect those changes. When that happens, you may need to re-authenticate or remap a field. Set a calendar reminder every 90 days to run a test lead through the scenario and confirm everything still lands in Jobber correctly.
You might also find value in understanding whether GoHighLevel integrates with ServiceTitan if you’re managing multiple platforms across your service business.
Cost comparison worth noting: Zapier can handle this same workflow, but its free tier only includes 100 tasks per month with single-step Zaps. Since this workflow requires multiple steps, you would need Zapier’s Starter plan at $19.99/month minimum. Make.com saves you roughly $10/month for the same result with more flexibility in data mapping.
Common Failure Points (And How to Fix Them)
Three issues account for most problems with this setup:
1. Tidio webhook stops firing.
This almost always means your Tidio plan’s conversation limit has been reached, or a chatbot flow edit accidentally removed the webhook action. Fix: Check your conversation count in Tidio’s dashboard, then confirm the webhook endpoint is still saved in your integration settings.
2. Jobber rejects the request.
Jobber requires at minimum a first name and either a phone number or email address to create a client record. If a visitor skips those fields, the Make scenario will error. Fix: Add a filter module that checks for required fields before the Jobber module runs. If data is missing, route the lead to a Google Sheet or email so you can follow up manually.
3. Duplicate client records in Jobber.
If the same person chats twice, you may get two separate client records. Jobber’s API does not deduplicate automatically. Fix: Add a Jobber “Search Client” module before “Create Client.” If a match is found on phone or email, update the existing record rather than creating a new one. This adds one module but keeps your client list clean.
Your Move: Set This Up Today
You now have everything you need to connect Tidio to Jobber through Make.com. The entire setup takes 15 minutes, costs nothing to start, and ensures every after-hours chat lead lands in your job management system automatically.
Here is your action list:
- Right now (2 minutes): Create a free Make.com account if you do not have one.
- Next (5 minutes): Build your Tidio chatbot flow with the webhook action, collecting name, phone, email, and service needed.
- Then (5 minutes): Set up the Make.com scenario with the webhook trigger, data filter, and Jobber create-request module.
- Finally (3 minutes): Run a test conversation through your Tidio chatbot and confirm the request appears in Jobber.
Once it is running, you are done. Every lead from Tidio flows into Jobber without you copying, pasting, or remembering to check another dashboard. That is one less place for jobs to fall through the cracks. (Source: voicemail abandonment research.) (Source: voicemail usage statistics.)
Before You Go — Grab Your Free AI Tools Starter Kit
Join 250+ small business owners getting smarter about AI. Take the 2-minute quiz and get your personalized toolkit.
Get Your Free Kit →Frequently Asked Questions
Does Tidio connect with Jobber natively?
No. Tidio and Jobber have no native integration as of May 2026. You connect them through Make.com, which automatically creates Jobber job requests from finished Tidio conversations.
How much does it cost to connect Tidio and Jobber through Make.com?
Make.com’s free plan handles up to 1,000 operations per month, which covers most small operators. If you need more volume, the Core plan is $9/mo (as of May 2026) (billed annually). Check Make’s current pricing before upgrading. Tidio’s Starter plan is $29/mo if you exceed the 50 free conversations.
Do I need coding skills to automate Tidio chats into Jobber?
No coding required. Make.com uses a visual drag-and-drop interface. You connect pre-built modules for webhooks and Jobber without writing a single line of code.
How long does setup take?
About 15 minutes for initial setup and testing. After it goes live, job requests from Tidio chats appear in Jobber automatically, no manual entry needed.
How we create this content
AIscending articles are researched using public documentation, verified user reviews, and published benchmarks, then written with AI assistance and editorially reviewed for accuracy. Some links on this site are affiliate links — we may earn a commission if you sign up, at no extra cost to you. Affiliate relationships never influence our recommendations. Read our editorial policy for details.
You Might Also Like
