Introduction
The Quip integration connects Rootly with your Quip workspace so teams can automatically create and update documents during and after incidents through Genius workflows. With the Quip integration, you can:- Automatically create Quip documents from incident workflows using retrospective templates or custom content
- Start documents from an existing Quip template
- Update existing Quip documents as an incident progresses
- Attach created documents directly to the incident record
Before You Begin
Before setting up the integration, make sure you have:- A Rootly account with admin permission to manage integrations
- A Quip account with permission to create API keys in the Quip admin portal
- Access to admin.quip.com
We recommend installing with a dedicated service account so the integration does not break if an individual user leaves your organization.
Installation
Create a Quip API key
Go to admin.quip.com and navigate to Settings > Integrations.
Create a new API key with the following settings:

- Permissions:
USER_READandUSER_WRITE - Redirect URI:
https://rootly.com/auth/quip/callback

Copy the Client ID and Client Secret after creating the key — you will need both to complete the setup in Rootly.
Workflow Actions
Create a Quip Page
This action creates a new Quip document in a specified folder. Parent Folder The Quip folder where the document will be created. Leave blank to create in your private folder. Title The title of the Quip document. Defaults to{{ incident.title }}. Supports Liquid syntax.
Use the Incident Variable Explorer to preview what Liquid variables return for your incidents.
If a Retrospective Template is selected, it overrides any content defined in the Custom Content field.
published after the document is created. Use this when follow-up notification workflows trigger on published retrospectives.
Update a Quip Page
This action updates an existing Quip document with new content. File ID The Quip thread ID of the document to update. Supports Liquid syntax.When a Create a Quip Page action runs, Rootly stores the resulting document ID and URL on the incident record. Reference the file ID in subsequent update actions using Liquid variables.

