When demo watched in CONSENSUS, sync it to Google Drive.
When a demo is watched in CONSENSUS, append or save viewing logs into a document in Google Drive.
See all CONSENSUS + Google Drive 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.
CONSENSUS Explore CONSENSUS →
TriggersFires when a new subscriber is added in CONSENSUS.
Fires when a campaign is sent from CONSENSUS.
Fires when a subscriber unsubscribes in CONSENSUS.
Adds or updates a subscriber in CONSENSUS.
Creates or sends a campaign from CONSENSUS.
Adds a subscriber to a segment in CONSENSUS.
Google Drive Explore Google Drive →
TriggersFires when a new file is uploaded to Google Drive.
Fires when a file in Google Drive is shared with someone new.
Fires when a folder's contents change in Google Drive.
Uploads a file to Google Drive.
Creates a new folder in Google Drive.
Shares a file from Google Drive with a link or user.
Common questions
Can Knit build “When demo watched in CONSENSUS, sync it to Google Drive.” between CONSENSUS and Google Drive?
Yes — describe it in the box above and Knit's Integrations Agent researches CONSENSUS and Google Drive'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.