- How to create Google Docs from a specific templates for every new Airtable record
- 1. Create your playbook and set the Airtable trigger as "New record added"
- 2. Add the "Copy doc & fill in {{placeholders}}" in Google Docs automation
- 3. Activate your Relay.app playbook
- Learn more about integrating with Google Docs and Airtable
- Related blog posts
How to create Google Docs from a specific templates for every new Airtable record
Create your playbook and set the Airtable trigger as "New record added"
After creating your playbook, you can proceed to add your trigger. The trigger detects changes in your connected apps and responds to your playbook.
To setup this playbook, click "Add trigger" and then select "New record added" under Airtable. Then, select the table you're working with. This will allow your playbook to automatically detect the new record added in Airtable and initiate necessary actions.
If this is your first time using a Airtable integration in Relay.app, a prompt will guide you through the connection process.
Add the "Copy doc & fill in {{placeholders}}" in Google Docs automation
Integrate the Google Docs automation into your playbook to ensure the specific document is promptly copied and replaced the details from each new data added in Airtable records.
Click the "Add step" button, then locate the "Copy doc & fill in {{placeholders}}" automation for Google Docs and input the mandatory and relevant details.
If your Google Docs account isn't already connected to Relay.app, you will be prompted to complete that connection. Make sure to allow the necessary permissions for Relay.app to sync with your Google Docs account.
Activate your Relay.app playbook
Activating your playbook is the final step to automate copying the specific Google Doc and replace the details. Once turned on, it will respond to a each new row added in Google Sheets by copying the specific Google Docs and replacing the details from the new Airtable records without manual intervention.
To enable your playbook, click the toggle button located in the header. It is advisable to perform a test run of your playbook beforehand to ensure all steps work seamlessly together and reminders are being sent correctly.