When check for new documents in Parashift, sync it to Discourse.
When document processing completes in Parashift, create a summary topic in Discourse.
See all Parashift + Discourse 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.
Parashift Explore Parashift →
TriggersFires when Parashift finishes extracting data from a document such as an invoice, receipt, form or resume.
Posts a file to Parashift to be parsed.
Runs an extraction template in Parashift against a document.
Discourse Explore Discourse →
TriggersFires when a new message is posted to a channel in Discourse.
Fires when a new channel is created in Discourse.
Fires when your team or a keyword is mentioned in Discourse.
Fires when a new file is shared in Discourse.
Posts a message to a channel in Discourse.
Sends a direct message to a specific person in Discourse.
Reacts to a message in Discourse.
Adds a user to a channel in Discourse.
Common questions
Can Knit build “When check for new documents in Parashift, sync it to Discourse.” between Parashift and Discourse?
Yes — describe it in the box above and Knit's Integrations Agent researches Parashift and Discourse'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.