Getting Started

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 the API to collect all information in native format, as well as all relevant metadata.

Integration Features

Files Collected

  • All accessible documents from a user account - public folders and private documents
  • To-do lists
  • Spreadsheets
  • Metadata fields,  including created on, expanded users, and updated on
  • Comments made on files
  • Chatrooms

Sync Modes

We currently support two syncing modes - one-time and archive.

  • One-time is a one-way sync that collects information only once.
  • Archive means that Onna will perform a full sync first and will keep tracking all changes at the source. If something is deleted in Quip it will not be deleted in Onna. 

Data Exports

Yes, you can export data and metadata in eDiscovery ready format. Load files are available in a dat, CSV, or custom text file.

Reasons for using 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

Ready to start collecting Quip?

How to Guide

Click on "Add a Source" and select Quip.

Once you click on Quip, it will open the following modal 

The first section covers the Source name. This is the name of your source in Onna. We've pre-filled it with the name of the source you're adding however this is entirely customizable. 

Quip's authentication method is through a token that is generated by Quip for each account. The token is valid until a user generates a new one. To collect multiple times from the same account either reuse the last generated token or request a new one using the link provided on the modal. 

Note: if you request a new token, the previous one is invalidated. This means that previous Quips set on Archive will be disabled. 

Once you have generated the token, you can either choose to sync the account or click on 'Configure' to change the sync type. 

Clicking on 'Configure' will take you to the following screen. Here you can choose what type of sync mode to choose for the sync and whether you'd like to add a date range for the files collected.  

Once you have clicked 'Add & Sync', you will see this integration under your Sources page.  Once the data source is fully synced, you will see a check mark at the top of the card with the last sync date.

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 the link to it provided in the file details. 

Quip chats will appear below the document. 

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. 

API Limitations

  • Content is offered for an entire user account - Onna can't collect specific folders. 
  • Due to limitations from their API, deleting documents from Quip will not delete them from Onna. However, any modifications to Quip documents will be applied to Onna.
  • 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: 

  • Kanban
  • Calendar
  • Project Tracker
  • Process Bar
  • Poll
  • Countdown

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 document's metadata. 

Did this answer your question?