Quip is a document collaboration and creation tool for teams. It combines chat, docs, task lists, and spreadsheets in one app. Onna connects directly with Quip's Enterprise API to collect all information from an enterprise account in native format, as well as all relevant metadata.
To collect from Quip Enterprise you'll need access to a Quip admin account. The admin api must be enabled on your account by Quip prior to running a collection.
- All accessible documents from an Enterprise account - public folders and private documents
- To-do lists
- Metadata fields including created on, expanded users, and updated on
- Comments made on files
We currently support 2 syncing modes - one-time & auto-sync and archive.
- One-time is a one-way sync that collects information only once.
- Auto-sync and archive means that Onna will perform a full sync and archive the information collected. Onna will then automatically sync and archive any new information after the original sync.
You can export data and metadata in eDiscovery ready format. Load files are available in a dat, CSV, or custom text file.
Reasons to use Onna to collect from Quip
- We process and index all content so everything is searchable
- We can keep track of changes happening in Quip so you have a complete archive
- Our Quip Enterprise integration is the only ediscovery integration that collects Quip content in native format
How to Guide
For this integration, you'll need access to Onna's admin panel which is available to our Enterprise users.
Head to Enterprise Sources from the admin panel. Click 'Add new' and select Quip Enterprise
The next screen will ask you for the 'Client ID' and 'Client secret'. These are fields that you should have access to as a Quip admin. You also have to make sure that you're signed into Quip on your browser with the user that you're using for the collection.
Once you've entered these fields click 'Connect'.
The next page will ask you for:
- Data source name: This is the name of your choice that will be used in Onna. It can be changed at a later date.
- Company ID: This is a field you should have access to as a Quip admin
- Target users: This step requires you to provide email addresses for the users that you'd like to collect information from
Once you've filled these fields you can set the synchronization mode and select the start/end date of your sync (for one-time syncs) or the start date for your autosync, finally click 'Add & sync'.
You will see the Quip Enterprise source listed in your enterprise sources. To access the files within head to the user dashboard.
When you click on the Quip data source, you will start seeing results being populated.
From this screen, you are able to filter results by date range, categories, and/or extensions using the menu on the left.
Quip pages in Onna
All Quip pages are stored as html - this is the format that Onna receives them in. We try our best to replicate this formatting on the platform. Remember that you can always get to the original document in Quip from Onna by clicking the arrow within the document viewer:
Here are some examples of how Quip pages look like:
Example: Meeting Agenda & Notes
Format in Quip
Format in Onna
Chat notes are stored at the bottom along with all other metadata collected regarding the page. Changes to the Quip page will show up at the bottom of the page in Onna - edits will be demonstrated in green and deleted content in red.
- Content is offered for the entire user account(s) specified during collection - Onna can't collect specific folders.
- Quip's formatting exists mainly within their platform. We try our best to replicate it but in some cases may not get an exact match.
We do not receive content from the following App styles on Quip:
- Project Tracker
- Process Bar
A number of the other App pages that they offer, such as Product Launch Plan or Account Review, are combinations of the app styles above.
However, any content that is written directly to the page, such as text, titles or comments (for instance - comments made on a Kanban card) we do collect as it falls under their API. We also collect the documents metadata.