Append shared file references directly into project docs
When a file is shared in OneDrive, append its reference link into the relevant working document in Conversion Tools.
See all Conversion Tools + OneDrive 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.
Conversion Tools Explore Conversion Tools →
TriggersFires when a new page or doc is created in Conversion Tools.
Fires when a new record is added to a database or table in Conversion Tools.
Fires when a doc in Conversion Tools is published or shared.
Fires when a status field changes on a record in Conversion Tools.
Starts a new page in Conversion Tools from a saved template.
Creates or updates a record in Conversion Tools.
Adds text to the end of an existing doc in Conversion Tools.
Moves a page in Conversion Tools into a different space.
OneDrive Explore OneDrive →
TriggersFires when a new file is uploaded to OneDrive.
Fires when a file in OneDrive is shared with someone new.
Fires when a folder's contents change in OneDrive.
Uploads a file to OneDrive.
Creates a new folder in OneDrive.
Shares a file from OneDrive with a link or user.
More Conversion Tools + OneDrive workflows
Log uploaded cloud files into a central document table
When a file is uploaded to OneDrive, automatically create a new record in Conversion Tools containing the file name and access link.
See details
Create cloud storage folders for new project pages
Whenever a new project page is created in Conversion Tools, automatically set up a corresponding asset folder in OneDrive.
See details
See all Conversion Tools + OneDrive integrations → · Browse the full workflow library →
Common questions
Can Knit build “Append shared file references directly into project docs” between Conversion Tools and OneDrive?
Yes — describe it in the box above and Knit's Integrations Agent researches Conversion Tools and OneDrive'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.
What's the most common Files & Storage + Productivity & Docs automation?
Creating a linked page in Conversion Tools when a new file lands in a specific folder in OneDrive, with the file embedded or linked automatically.
Does this work in reverse — exporting a doc as a file?
Yes — the Agent can also export a finished doc from Conversion Tools into OneDrive as a file, keeping both systems in sync either direction.