The Google Calendar connection brings the appointments from your calendar into your iSend contacts, so the reminder automation finds them on its own. You give iSend read-only access to the calendar, choose which calendar, which contact group and which date and time field the appointment is written to, and click sync. The platform reads the events of the next 30 days, finds the contact for each event by email, phone number or name, and writes the time to the field. iSend does not write, change or delete anything in Google.
What you need before you start
- A contact group with the customers who book appointments, with phone number, first name and last name filled in, and email where possible.
- A custom field of the "date with time" type in the group, e.g. "Appointment". You can also create it from the automation form.
- A Google account with the appointments calendar. One Google account per iSend account is supported.
The connection in four steps
- In the Integrations menu select Google and click Connect with Google. Google's page opens, where you select an account and approve the access. Google returns you to iSend with the connection card filled in with the account's name and email.
- Turn on the Calendar Sync switch and in its settings choose the calendar from the list of your calendars, the contact group and the appointment field. Save.
- Click Preview events. You see the calendar's upcoming events and, for each one, whether a contact was found and which. This lets you correct names or phone numbers before anything is written.
- Click Sync Calendar. At the end you see three numbers: how many events were added to contacts, how many updated an existing time, and how many were skipped because no contact was found.
The sync runs when you click it. Make it part of your routine, e.g. every morning or every time you book new appointments, before the time the reminders go out.
How it matches events to contacts
For each event of the next 30 days, the platform tries three methods in order:
| Order | What it looks at in the event | What it matches it with in the group |
|---|---|---|
| 1 | The guests' emails, except your own | The contact's email field |
| 2 | Phone numbers inside the event title or description | The contact's mobile number, ignoring spaces, dashes and the leading 30 |
| 3 | The event title | The contact's first and last name, case-insensitive |
The most reliable method is the phone number: write the customer's mobile number in the title or description of the appointment, e.g. "Maria Papadopoulou 6912345678". The name works when it is written the same way as in the contact. An event with no matching contact is skipped and counts among the "skipped" in the preview, so you can see it.
The time is written to the field as day/month/year and time, e.g. 21/10/2026 11:30. An all-day event without a time is written with the time 09:00. If the contact already has the same time, nothing changes. If it has a different one, it is updated with the new one. The field holds one appointment per contact, the last one the sync read.
From the field to the reminder
The sync fills the field, it does not send anything. Sending is done by the "Appointment" type automation on the same field, with an offset from 15 minutes to 2 days before and an optional confirmation link. The article about the appointment reminder has the setup. The flow for a medical practice: you book appointments in Google Calendar as always, every morning you click sync, and in the afternoon the reminders for tomorrow go out on their own.
Google Contacts sync
The same connection also syncs your Google Contacts to iSend, with a separate switch and its own settings: a destination group, or automatic creation of a "Google Contacts" group with the fields phone number, first name, last name, email and date of birth, and what happens with numbers that already exist, whether they stay as they are or get updated. Contacts without a phone number are skipped. The preview shows what will be added before you click it.
A note on consent: having someone in your Google Contacts does not mean you have permission to send them advertising SMS. Sync only groups of customers who have consented, or use the imported contacts for appointments and updates, not for offers. The article about sending hours and the law explains the difference.
What iSend sees and what it does not
| Data | Access | For what |
|---|---|---|
| Profile email and name | Read | Identifying and displaying the connected account |
| Calendar events | Read-only | Appointment time, guests, title, description |
| Google Contacts | Read-only | Names, phone numbers, emails, birthdays |
iSend does not read your emails, does not create, change or delete events or contacts in Google, and does not share the data with third parties. With Disconnect, access is revoked at Google and the credentials are deleted from iSend. The contacts and appointment times that have already been written stay in your groups.
Frequently asked questions
Does the sync run automatically?
No, you click it from the integration page. Each time it reads the events of the next 30 days, up to 250 events, and updates whatever changed. One click a day, before the reminder time, is enough.
What happens if a customer has two appointments within the month?
The field holds one appointment per contact. The sync writes the last event it read for the contact. For customers with many appointments, sync daily, so the field always has the next one.
Why are some events skipped?
Because the platform did not find a contact in the group with the guest's email, with a phone number in the title or description, or with a first and last name identical to the title. The preview shows which ones. Add the mobile number to the appointment title or the contact to the group and run the sync again.