Turn new Jobber requests into HubSpot deals and Slack alerts

By General Input

Every new service request in Jobber becomes a HubSpot contact and deal, plus an instant Slack alert so your team can call the customer back the same day.

Integrations

  • Jobber
  • HubSpot
  • Slack Bot

Type

Deterministic Code

Categories

  • Sales
  • Operations

When a new service request comes into Jobber, create the matching lead in HubSpot and alert my sales channel in Slack. Trigger this workflow on the Jobber REQUEST_CREATE webhook, which fires whenever a new request is created.

Important implementation detail: the Jobber webhook payload carries only the topic, the account id, and the item id. It does not include the object body, so the workflow has nothing useful to work with until it fetches the record itself. Start by calling Jobber Get Request with the item id from the webhook payload to retrieve the request title, the associated property, the request notes, and the status.

Next, call Jobber Get Client for the client on that request to get the contact details: first name, last name, email address, and phone number. Also call Jobber Get Property for the property referenced on the request so you have the full service address.

Create the person in HubSpot with Create Contact, using the email address as the dedupe key so a repeat customer is matched to their existing record rather than duplicated. Map the client first name, last name, email, and phone onto the contact properties.

Then create the opportunity with HubSpot Create Deal. Set the deal name from the Jobber request title. Leave the deal amount blank, since a request arrives before the work has been quoted and the value is not known yet. Store the Jobber request id on the deal so the two systems stay traceable, and associate the deal with the contact from the previous step.

Handle the missing email case explicitly: when the Jobber client has no email address on file, skip the email keyed contact creation and attach the deal to the phone only record instead, matching on the client phone number and name. A request should never be dropped just because the contact details are incomplete.

Finish with slackbot Send a Message to the sales channel. The message should show the client name, the service address from the property, and the request notes, along with the request title and status, so whoever is on intake has everything they need to call the customer back the same day.

Related prompts

Explore more prompts
A brand asset library your marketing team actually searchesTurn Mailjet email clicks into ranked HubSpot follow-upsClean out the Looker dashboards and Looks nobody opensLiveKit live operations console for room moderationWake up dormant Keap leads with a researched reasoniMessage campaign console with pre-flight checks and delivery boardLiveChat coverage board for planning next week's shiftsPhone routing control panel for LiveKit voice agentsA searchable RFP answer library your bid team drafts fromLinkedIn Ads budget pacing dashboard for every client account