When new incoming call in Magnetis, sync it to Magnetic.
Sync call records from Magnetis into Magnetic.
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.
Magnetic Explore Magnetic →
TriggersFires when a new task, job or item is created in Magnetic.
Fires when a task in Magnetic is marked complete.
Fires when a task's due date in Magnetic is coming up.
Fires when a task, job or project changes status in Magnetic.
Creates a new task, job or item in Magnetic.
Updates a task's status or assignee in Magnetic.
Posts a comment on a task in Magnetic.
Assigns a task in Magnetic to a team member.
Magnetis Explore Magnetis →
TriggersFires when a new inbound call is tracked in Magnetis.
Fires when a tracked call in Magnetis goes unanswered.
Fires when a caller leaves a voicemail in Magnetis.
Creates or updates a caller's contact record in Magnetis.
Adds a tag or disposition to a call record in Magnetis.
Sends a text message via Magnetis.
Common questions
Can Knit build “When new incoming call in Magnetis, sync it to Magnetic.” between Magnetic and Magnetis?
Yes — describe it in the box above and Knit's Integrations Agent researches Magnetic and Magnetis'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.