When new event in Mav, sync it to WhatConverts.
When a new event occurs in Mav, update lead tracking data 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.
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.
Mav Explore Mav →
TriggersFires when a new text message is received in Mav.
Fires when a new call comes in or out through Mav.
Fires when a call is missed in Mav.
Fires when a call recording finishes processing in Mav.
Sends a text message through Mav.
Starts an outbound call via Mav.
Creates or updates a contact in Mav.
Sends a recorded voice message via Mav.
Common questions
Can Knit build “When new event in Mav, sync it to WhatConverts.” between WhatConverts and Mav?
Yes — describe it in the box above and Knit's Integrations Agent researches WhatConverts and Mav'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.