When new job in Simpro, sync it to WhatConverts.
When a new job is created in Simpro, attribute and sync the lead source in WhatConverts.
See all WhatConverts + Simpro integrations or talk to a human
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.
Simpro Explore Simpro →
TriggersFires when a new task, job or item is created in Simpro.
Fires when a task in Simpro is marked complete.
Fires when a task's due date in Simpro is coming up.
Fires when a task, job or project changes status in Simpro.
Creates a new task, job or item in Simpro.
Updates a task's status or assignee in Simpro.
Posts a comment on a task in Simpro.
Assigns a task in Simpro to a team member.
Common questions
Can Knit build “When new job in Simpro, sync it to WhatConverts.” between WhatConverts and Simpro?
Yes — describe it in the box above and Knit's Integrations Agent researches WhatConverts and Simpro'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.