For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
DeveloperAcademyCommunityStatus
  • Service Management
    • Overview
    • Concierge & Ticketing Capabilities Overview
    • Forms
    • Forms - Integration Specific Guides
    • Live Agent Chat / Handoff
    • Triage
    • Approval Mirroring
    • Ticket Interception
    • Generic Ticketing Integration: Ticket Gateway
  • Administration
    • MyMoveworks
    • Organization Information
    • Roles and Permissions
    • MyMoveworks SSO
  • Moveworks Setup
    • Accessing Moveworks Setup
    • First-Time Login via Magic Link
    • Moveworks Setup Modules
    • Moveworks Setup: Module How To Guides
    • Plugin Management
    • Monitor Alerts
    • Audit Logs
    • DSL Fields Defaults
    • Data Crawling View
    • API Playground
    • Setup Homepage
    • Troubleshooting Hub
    • Security and Privacy Settings
    • Configuration Delete
    • Advanced Config Editor
    • Identity configuration
    • Onboarding Stage
  • Security
    • Security
    • Hyperlink & Button Expiry
    • Attachment Handling
    • Moveworks Subprocessors
  • Provision Management
    • Overview
    • Access Software
    • Access Groups
    • Access Account
  • Access Requirements
    • Overview
    • Update Set Modules
    • Ticketing Systems & ITSMs Access
    • Identity and Access Management Systems Access
    • Multi-Factor Authentication (MFA) Systems Access
    • Knowledge Access Requirements
      • ServiceNow (KB Only) Access Requirements
      • Sharepoint Online Access Requirements (KBs & Files) [Classic]
      • SharePoint (On-Prem) Access Requirements
      • Confluence Cloud Access Requirements
      • Confluence Server / Data Center Access Requirements
      • Google Drive Access Requirements
      • Notion Access Requirements
      • Guru Access Requirements
      • Salesforce Knowledge Access Requirements
      • Simpplr Access Requirements [NEW]
      • LumApps Access Requirements
      • Unily Access Setup Guide
      • Jive Access Requirements
      • Interact Access Requirements
      • Igloo Access Requirements
      • Haystack Access Requirements
      • GitHub Knowledge Access Requirements
      • Dropbox Content Access Requirements
      • Contentful Access Requirements
      • Quip Access Requirements
      • Slite Access Requirements
      • ScreenSteps Access Requirements
      • RightAnswers Access Requirements
      • SAP Build Work Zone Access Requirements
      • StaffBase Access Requirements
      • Squiz KB Access Requirements
      • WordPress Access Requirements
      • Workday Access Requirements (Knowledge)
      • Axero Access Requirements
      • Comaround Access Requirements
    • Email Distribution List Systems Access
    • Facilities Management Access
    • Live Agent Chat Access
    • HR Information System Access
    • Expense Management Access
    • Calendar Management Access
  • Core Platform
    • User Identity
    • Moveworks On-Prem Agent
    • Approvals Engine
    • Entity Catalog
    • Configuration Languages
    • Moveworks Data Objects
    • SIEM
  • Employee Experience Insights
    • Overview
    • Breaking Down the Dashboard
    • Understanding Industry Benchmarks
    • Apps & Services
    • Impact Module
    • EXI Common Use Cases
    • Configure EXI
    • Ticket Backpolling
  • Knowledge Studio
    • Overview
    • Knowledge Studio Configuration
    • AI Powered Recommendations
    • Inspecting & Verifying Sources
    • Publishing Articles
    • Creating Knowledge Articles
    • Resolving IT Tickets Guidance
DeveloperAcademyCommunityStatus
On this page
  • Setup
  • How to generate the Client Credentials?
  • Creating the Connector
Access RequirementsKnowledge Access Requirements

Quip Access Requirements

||View as Markdown|
Was this page helpful?
Edit this page
Previous

Slite Access Requirements

Next
Built with

As Moveworks has integrated with Quip Knowledge, we would need the following details to connect our services with your Quip instance. Our systems fetch the knowledge articles stored in your system and serve the user with relevant answers.

Setup

To authenticate the API calls to Quip, we use the recommended OAuth mechanism summarized in the diagram below:

This will require the creation of a Service Account that has access to the documents present within your Quip instance as well as the creation of a New API Key for Client Credentials.

️

Quip’s Automation APIs have severely low Rate Limits and therefore you would need to contact your Quip Support to raise a ticket for upgrading the Rate Limit of the Service Account you created for us by at least 4X for us to successfully test and enable Quip Content Integration with your MW Bot.

After following through this setup, you will need to provide the following to Moveworks:

  • OAuth Client Credentials
    • Client ID
    • Client Secret
  • Service Account Credentials
    • Username
    • Password

How to generate the Client Credentials?

In order to get secure access to your instance using the available APIs, we will follow the authentication method that is used by Quip.

Note: Only a Quip admin can create an API key.

  1. Log in to the Quip Admin Console.
  2. Click Settings, then Integrations.
  3. Click New API Key.
  4. Name your API key and enable the User Read permission scope
  5. Copy the client ID and client secret and store it in a safe storage

Creating the Connector

With all the required details collected, we can now configure the connector to interact with your Quip Instance.

  • Go to the Connectors module in Moveworks Setup, by clicking on Manage Connectors under Core Platform, and then click on System Connectors.
  • Click on Create New in the top right corner.
  • Search for the Quip System here


  • Start by providing the the Quip URL, and the API Key we just generated along side the Username and Password for the Service Account.

You can now go ahead and save the config and start using this Connector across Setup.