When [crm event] new entity event in SOLAPI, sync it to Parsio.
When a CRM entity event triggers in SOLAPI, send document/entity data to Parsio for parsing.
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.
SOLAPI Explore SOLAPI →
TriggersFires when a new text message is received in SOLAPI.
Fires when a new call comes in or out through SOLAPI.
Fires when a call is missed in SOLAPI.
Fires when a call recording finishes processing in SOLAPI.
Sends a text message through SOLAPI.
Starts an outbound call via SOLAPI.
Creates or updates a contact in SOLAPI.
Sends a recorded voice message via SOLAPI.
Parsio Explore Parsio →
TriggersFires when Parsio finishes extracting data from a document such as an invoice, receipt, form or resume.
Posts a file to Parsio to be parsed.
Runs an extraction template in Parsio against a document.
Common questions
Can Knit build “When [crm event] new entity event in SOLAPI, sync it to Parsio.” between SOLAPI and Parsio?
Yes — describe it in the box above and Knit's Integrations Agent researches SOLAPI and Parsio'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.