When new contact in SALT, sync it to WhatConverts.
When a new contact is added in SALT, record the lead source details in WhatConverts.
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.
SALT Explore SALT →
TriggersFires when a form is submitted in SALT.
Fires when a respondent finishes a survey in SALT.
Fires when an existing response is edited in SALT.
Creates or updates a form or survey in SALT.
Looks up a specific form response in SALT.
Adds a respondent or contact to a form in SALT.
WhatConverts Explore WhatConverts →
TriggersFires when a new inbound call is tracked in WhatConverts.
Fires when a tracked call in WhatConverts goes unanswered.
Fires when a caller leaves a voicemail in WhatConverts.
Creates or updates a caller's contact record in WhatConverts.
Adds a tag or disposition to a call record in WhatConverts.
Sends a text message via WhatConverts.
Common questions
Can Knit build “When new contact in SALT, sync it to WhatConverts.” between SALT and WhatConverts?
Yes — describe it in the box above and Knit's Integrations Agent researches SALT and WhatConverts'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.