Essential Steps and Best Practices for Quip–Salesforce Integration

1. Use a Dedicated Service Account for the Quip Connection

The Quip–Salesforce integration authenticates using a Salesforce user account. Using a personal user account creates a single point of failure — if that person leaves or their password changes, the integration breaks for everyone. Instead, create a dedicated Salesforce service account with the Quip Admin permission set and use that account to establish and maintain the OAuth connection.

Best practice: Name the service account something clear like quip-integration@yourcompany.com and ensure at least two administrators know the credentials.

2. Assign the Correct Permission Sets Before Deploying

Users need the Quip User permission set to interact with embedded Quip documents on Salesforce records. Administrators who manage Quip Document Components need the Quip Admin permission set. Assign these before users encounter the Quip component to avoid the confusion of a blank or error-state component on first load.

3. Configure Synced Sharing Deliberately

Synced Sharing determines what access level all Salesforce record viewers automatically receive to the embedded Quip document. The default is Comment Access. Review this setting with your security team before enabling it for the entire org — setting it too permissively can expose sensitive documents to users who should have read-only access.

4. Store the Document URL in a Custom Field

When the Quip Document Component generates a document from a template, it stores the document URL in a custom URL field on the Salesforce record. This field is essential for any Flow automations that need to reference, move, or lock the document. Create and configure this field before deploying the component to production.

5. Test in Sandbox Before Production

Always configure and test the Quip integration in a Salesforce sandbox before deploying to production. Key things to verify in sandbox:

• Users can generate documents from the component
• The document URL field is populated correctly
• Flow automations that reference the document URL run without errors
• Synced Sharing gives users the expected access level

6. Reconnect After Sandbox Refresh

A Salesforce sandbox refresh resets the OAuth tokens and API keys associated with the Quip integration. After every sandbox refresh, you must regenerate the Quip API key in the Quip Admin Console and update the Salesforce Auth Provider with the new credentials. See Reconnecting the Quip/Salesforce Integration after a Sandbox Refresh for step-by-step instructions.

7. Monitor for API Key Conflicts

Using the same Quip API key across multiple Salesforce orgs causes 500 errors and sync failures. Each Salesforce org connected to Quip should have its own unique API key. If you are seeing intermittent 500 errors in your Quip–Salesforce integration, check whether the same API key is used in multiple orgs.