- How to add a new guest to a Google Calendar meeting for each newly added contact in Brevo
- 1. Create your playbook and set the Brevo trigger as "New contact added"
- 2. Add the "Add guests to meeting" in Google Calendar automation
- 3. Activate your Relay.app playbook
- Learn more about integrating with Brevo and Google Calendar
- Related blog posts
- More how-to guides featuring Brevo and Google Calendar
How to add a new guest to a Google Calendar meeting for each newly added contact in Brevo
Create your playbook and set the Brevo trigger as "New contact 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 contact added" under Brevo. Then, select the contact's details. This will allow your playbook to automatically detect the newly added contact in Brevo and initiate necessary actions.
If this is your first time using a Brevo integration in Relay.app, a prompt will guide you through the connection process.
Add the "Add guests to meeting" in Google Calendar automation
Integrate the Google Calendar automation into your playbook to ensure the prompt addition of a new guest to the Google Calendar meeting when a new contact has been added on Brevo.
Click the "Add step" button, then locate the "Add guests to meeting" automation for Google Calendar and input the mandatory and relevant details.
If your Google Calendar 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 Calendar account.
Activate your Relay.app playbook
Activating your playbook is the final step to automate the addition of a new guest to the Google Calendar meeting. Once turned on, it will respond to each newly added contact on Brevo by adding a new guest to the Google Calendar meeting 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.