Google Calendar sync
Available on all current plans (Solo, Business and Team).
See your Velosiq appointments alongside everything else in Google Calendar — on your phone, in Gmail, everywhere Google Calendar lives.
Connect
- Open the Calendar page.
- Click Connect Google Calendar.
- Sign in with Google and approve calendar access.
- You're returned to Velosiq with a green Google Calendar connected chip.
Google asks for permission to manage your calendars. Velosiq uses it to write its own events and to remove them again — it does not read your existing events, and nothing already in your calendar is changed.
Sync is one-way: Velosiq → Google
This is the most important thing to understand about the feature. Your appointments flow out to Google:
- Create an appointment in Velosiq → it appears in your Google Calendar
- Edit or move it → the Google event updates
- Delete it → the Google event is removed
Nothing flows back. An event you create directly in Google Calendar will not appear in Velosiq, and it is invisible to availability checks — so a client can still book a public slot that your Google Calendar says is busy. If a commitment needs to block booking, it has to exist in Velosiq.
Editing a synced event inside Google works, but it doesn't last: Velosiq sends the whole event on every update, so the next time you touch that appointment in Velosiq your Google-side edits are overwritten. Treat the Google copy as a read-only mirror.
What actually syncs
Only the four fields Google needs to place the event:
| Velosiq field | Google event |
|---|---|
| Title | Event title |
| Description | Event description |
| Start / end time | Event time |
| All-day flag | All-day event |
Everything else stays in Velosiq. The client, linked assets, appointment status and location are not copied — so a Google event says what and when, never who for. If you want the client's name on your phone, put it in the appointment title.
Events land on your primary Google calendar. There is no per-calendar picker.
Per-person connections
Google connections are individual: each team member connects their own Google account, and appointments sync to the calendar of the person who creates or edits them. Your connection never exposes a teammate's Google account, and one person disconnecting has no effect on anyone else.
One consequence worth planning around: if a colleague edits an appointment you created, the update is written to their Google calendar, not yours — because syncing follows whoever made the change.
When Google is unreachable
Appointment saves never wait on Google. The appointment is committed to Velosiq first and the Google call happens afterwards, so a slow or failing Google API costs you nothing — the save still succeeds, and only the mirror is briefly out of date.
If you revoke Velosiq's access from your Google account permissions page, Velosiq notices the next time it tries to sync, clears the dead connection, and shows the Calendar page as disconnected again. Reconnect whenever you like. Temporary Google outages and rate limits are not treated as a disconnection, so a bad afternoon at Google won't quietly unlink your account.
Disconnect
Click Disconnect on the Calendar page any time. Velosiq revokes its access with Google and deletes the stored connection.
Your existing Velosiq appointments are unaffected. Events already written to Google are left in place — disconnecting stops future syncing, it does not clean up the past. Delete any you don't want directly in Google Calendar.