With Google Docs, everyone can work together in the same document at the same time.
How to Connect
- On the My pipelines page, click Create a pipeline. Enter name, description, and tag fields and click the Create Pipelines button. The pipelines wizard displays:
- From the wizard you choose the connections for the first steps of your pipeline. When you choose a type, you'll add the channels and steps for your first steps. You can always add more steps later. A Triggered pipeline is started by a specific event in real-time. A Scheduled pipeline will start according to a schedule. A Manual pipeline only starts manually. Once you've completed the wizard, you'll be prompted for connection detail, if necessary. If you are an experienced builder, click the Start from scratch button and then from the right side of the page, choose the All to list all available channels.
- Expand Google Docs and click Connect to Google Docs.
- Review the permissions that Pipelines will receive once connected. Your permissions are based on your existing Google account. You can select specific permissions or allow all the options. Google Doc permissions are required. When finished click Connect to Google Docs.
Note: Depending on the permissions granted, integration and functionality will be affected.
- You may need to sign in with your Google credentials. This is required to set up the connection between Google Docs and Pipelines.
- Agree to allow Pipelines access to your Google account by clicking Allow.
How to reconnect the Google Docs channel
You may need to reconnect your account to a channel. Reasons may be (but not limited to):
If you need to connect a different account.
Authorization updates, such as a changed password.
Editing the access rights that Pipelines has to the channel.
- Select a pipeline that already has Google Docs in it.
- Open a step containing Google Docs.
- Under account, select Connect (or reconnect) and follow the process above, How to connect.
There is one available step you can use with Google Docs:
|Action||Replace Text in a Document||Replaces text in the selected document.|
There are no known limits for use with pipelines.
Examples of usage
The following is an example of a use of Google Doc in Pipelines.
Employee onboarding and user provisioning
A new employee record, created in our Quickbase app, triggers the creation of a new permissionsd for the new user in Google Drive.
A new employee's information is added in our Quickbase HR app.
Our pipeline, triggered by this addition, replaces text in New Employee document selected in Google Docs.