When started call in 800.com, sync it to Square.
Track incoming call starts from 800.com in Square to align caller history with customer profiles.
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.
Square Explore Square →
TriggersFires when a customer places a new order in Square.
Fires when an order in Square is paid, fulfilled, refunded or disputed.
Fires when a new customer account is created in Square.
Fires when a customer abandons their cart before completing checkout in Square.
Creates or updates a product or listing in Square.
Updates an order's status or fulfillment details in Square.
Sends a custom API request to Square for actions not covered by a dedicated action.
Common questions
Can Knit build “When started call in 800.com, sync it to Square.” between 800.com and Square?
Yes — describe it in the box above and Knit's Integrations Agent researches 800.com and Square'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.