- How to copy and rewrite Google Slides presentations for new Google Calendar events
- 1. Add the Google Calendar "Event scheduled" trigger
- 2. Add the Google Slides "Copy slides & fill in {{placeholders}}" automation
- 3. Turn on the playbook
- Learn more about integrating with Google Slides and Google Calendar
- Related blog posts
- More how-to guides featuring Google Slides and Google Calendar
How to copy and rewrite Google Slides presentations for new Google Calendar events
Add the Google Calendar "Event scheduled" trigger
Every playbook starts with a trigger. The trigger detects changes in your connected apps and runs your playbook in response.
Click "Add trigger" and select "Event scheduled" under Google Calendar. Then, select the calendar and relevant details. This trigger will automatically detect all the new scheduled events in Google Calendar to copy and rewrite Google Slides presentation.
If this is your first time using a Google Calendar integration in Relay, you'll be prompted to connect your Google Calendar account.
Add the Google Slides "Copy slides & fill in {{placeholders}}" automation
Integrate the Google Slides automation into your playbook to ensure copying and customizing the specific Google Slides presentation for every every new events scheduled in Google Calendar. Add a new step and select "Copy slides & fill in {{placeholders}}" from the list of Google Slides automations.
Connect Google Slides to Relay if you haven't already, then fill out the mandatory details and placeholders to replace. You can reference fields from Google Calendar to automatically pass along the right data.
Turn on the playbook
Activating your playbook is the final step to automate copying and customizing the specific Google Slides presentation for every new events scheduled in Google Calendar. Once turned on, it will respond to a new scheduled event in Google Calendar by copying and customizing the specific Google Slides presentation 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 sent correctly.