---
schema_version: "1"
id: e265316cdddcfe6ffaa51089629b37484d189eee950f8fb681ce49bfd82393eb
title: Managing Documents Process Example
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/process_example_quip.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.process_example_quip.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 4f142d35caea53842670cb5a8030799d57ff77f738781b9ad80d3a1484c95940
description: This example uses Process Builder to manage documents in Salesforce. The example moves a document to a shared folder in Quip whenever the record that the document is associated with is created or updated. This process ensures that the documents associated with a Salesforce record object are always available to users who have access to the shared folder.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Managing Documents Process Example

This example uses Process Builder to manage documents in Salesforce. The example moves a document to a shared folder in Quip whenever the record that the document is associated with is created or updated. This process ensures that the documents associated with a Salesforce record object are always available to users who have access to the shared folder.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic (<a href="https://help.salesforce.com/s/articleView?id=xcloud.overview_edition_lex_only.htm&amp;language=en_US" target="_blank">not available in all orgs</a>) and Lightning Experience</td></tr><tr class="" id="process_example_quip__d2613e343"><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <span id="process_example_quip__d2613e347"><a name="process_example_quip__d2613e347"></a><strong>Essentials</strong>, <strong>Professional</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</span></td></tr></tbody></table>

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_important.png)

Important Support and updates for Process Builder have ended as of December 31, 2025. This means that support won't be provided for any process and bugs in the Process Builder product won't be fixed. See [Workflow Rules & Process Builder End of Support](https://help.salesforce.com/s/articleView?id=001096524&type=1&language=en_US).

After December 31, 2025, existing processes continue to run, and you can activate, deactivate, and edit them; however, we recommend using Flow Builder. To migrate existing processes, plan your [switch to Flow Builder](https://help.salesforce.com/s/articleView?id=platform.flow_migrate_to_flow_learning_map.htm&release=264.0.0&type=5 "Flow Builder combines the capabilities of workflow rules and Process Builder in a single point-and-click tool, making it easier to create a triggered process. If you created triggered processes with workflow rules or Process Builder, use the Migrate to Flow tool to move them to Flow Builder. Start by migrating and testing in a sandbox environment before moving your new flows to production.") and use the [Migrate to Flow](https://help.salesforce.com/s/articleView?id=platform.flow_migrate_to_flow.htm&release=264.0.0&type=5 "Use the Migrate to Flow tool to convert your Process Builder processes and workflow rules into Flow Builder, including scheduled actions. The tool also supports partial migration of processes for most actions.") tool. For new automations, create flows in [Flow Builder](https://help.salesforce.com/s/articleView?id=platform.flow.htm&release=264.0.0&type=5 "Automation reduces repetitive work and helps your team complete tasks faster and more accurately. With Flow Builder, you can build simple or complex automations, forms, and guided experiences with no code. You can add forms to Salesforce pages and Experience sites, and launch flows using buttons, record triggers, or schedules.").

In the example, it’s assumed that:

- The Account object has a custom field labeled Quip Account Plan Doc (API name Quip\_Account\_Plan\_Doc\_\_c). For each account, the custom field stores the URL of an associated document that contains a plan for the account.
- All the Account Plan documents are in a shared folder. The folder’s URL is https://acme.quip.com/123FakeURL456.

The process starts when an Account record (1) is created or updated.

![Process Builder example to move a Quip document to a shared folder](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/platform_automation/images/process_builder/pb_quip_example.png)

The criteria (2) checks whether the value of the Quip Account Plan Doc custom field has changed and whether the field isn't null. If both conditions are true, an immediate action (3) moves the Quip Account Plan doc to the specified shared folder. Let’s dig a little deeper into the criteria and action in this sample process.

The criteria’s Set Conditions section defines which conditions must be met in the Quip Account Plan Doc field to move a document. There are two conditions: the Quip Account Plan Doc field isn’t null and that it’s changed. The Field column requires the full API name of the field, in this case, `[Account].Quip_Account_Plan_Doc__c`. The Conditions section specifies that all the conditions must be met to execute the action.

![Criteria node showing the two conditions.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/platform_automation/images/process_builder/pb_quip_example_criteria_node.png)

For the action definition, you select **Quip** for Action Type to view the Quip-related actions. Enter an Action Name (Move Doc to Folder in our example) then select the action (**Add Document to Folder**). The Document URL is a field reference to the custom field (\[Account\].Quip\_Account\_Plan\_Doc\_\_c) that contains the URL of the document to move. The Folder URL is a String type that specifies the URL of the shared folder.

![Quip action to add the document to a shared folder.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/platform_automation/images/process_builder/pb_quip_example_action.png)

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_note.png)

Note To replace the existing Process Builder processes and Workflow Rules with flows before Process Builder and Workflow Rules reach [end of support](https://help.salesforce.com/s/articleView?id=001096524&type=1&language=en_US), see [Quip Actions in Flow Builder](https://help.salesforce.com/s/articleView?id=xcloud.quip_automation_flow.htm&type=5&language=en_US).