When something happens in slyText, sync it to Docparser.
When an event occurs in slyText, send message content to Docparser for extraction.
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.
slyText Explore slyText →
TriggersFires when a new text message is received in slyText.
Fires when a new call comes in or out through slyText.
Fires when a call is missed in slyText.
Fires when a call recording finishes processing in slyText.
Sends a text message through slyText.
Starts an outbound call via slyText.
Creates or updates a contact in slyText.
Sends a recorded voice message via slyText.
Docparser Explore Docparser →
TriggersFires when Docparser finishes extracting data from a document.
Posts a file to Docparser to be parsed.
Runs an extraction template in Docparser against a document.
Common questions
Can Knit build “When something happens in slyText, sync it to Docparser.” between slyText and Docparser?
Yes — describe it in the box above and Knit's Integrations Agent researches slyText and Docparser'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.