When new lead in Drive Chat, sync it to OTO.
When a new lead is logged in Drive Chat, sync lead delivery information to OTO.
Google for Startups AcceleratorHow 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.
OTO Explore OTO →
TriggersFires when a new order or shipment is created in OTO.
Fires when a shipment is picked up, in transit or delivered in OTO.
Fires when a shipping label is created in OTO.
Creates a shipping or delivery order in OTO.
Creates a shipment and books the carrier in OTO.
Looks up the tracking status of a shipment in OTO.
Drive Chat Explore Drive Chat →
TriggersFires when a new contact or lead is added to Drive Chat.
Fires when a field on a contact changes in Drive Chat.
Fires when a deal, case or record moves to a new stage in Drive Chat.
Fires when a deal is marked won in Drive Chat.
Creates or updates a contact in Drive Chat.
Creates a new deal in Drive Chat.
Moves a deal or record to a new stage in Drive Chat.
Logs a call, email, or note against a record in Drive Chat.
More OTO + Drive Chat workflows
See all OTO + Drive Chat integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “When new lead in Drive Chat, sync it to OTO.” between OTO and Drive Chat?
Yes — describe it in the box above and Knit's Integrations Agent researches OTO and Drive Chat'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.
Can a won deal create a shipment?
Yes. When a deal is won in Drive Chat, OTO can create an order or shipment.
Will reps see delivery updates?
When a shipment status changes in OTO, the related contact or deal in Drive Chat can be updated.