When completed call in 800.com, sync it to Jobber.
Log details of completed calls from 800.com to Jobber for work order tracking.
4.9/5 on G2·
Google for Startups Accelerator
How Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
800.com Explore 800.com →
TriggersFires when a new inbound call is tracked in 800.com.
Fires when a tracked call in 800.com goes unanswered.
Fires when a caller leaves a voicemail in 800.com.
Creates or updates a caller's contact record in 800.com.
Adds a tag or disposition to a call record in 800.com.
Sends a text message via 800.com.
Jobber Explore Jobber →
TriggersFires when a new booking or appointment is made in Jobber.
Fires when a booking in Jobber is changed or canceled.
Fires when a new customer books for the first time in Jobber.
Creates a new booking or appointment in Jobber.
Cancels or moves a booking in Jobber.
Creates or updates a customer record in Jobber.
Adds a booking from Jobber to a connected calendar.
Common questions
Can Knit build “When completed call in 800.com, sync it to Jobber.” between 800.com and Jobber?
Yes — describe it in the box above and Knit's Integrations Agent researches 800.com and Jobber's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.