CRM MVP
The CRM's activities and the user's external calendar stay in sync in both directions, so a meeting booked in either place appears in the other.
Salespeople live in their calendar. If the CRM cannot write to it, they will book meetings outside the CRM and the activity record will be permanently incomplete.
The distinction that matters is what is being synced. Pushing a date field to a calendar is not the same as syncing the activity object, because a date field carries no type, no owner and no link to the opportunity.
Judged on the activity object, not on a generic date field. The CRM's activities and the user's external calendar must stay in step against a mainstream provider.
Yes where the sync runs in both directions on the activity object.
Partial where it runs in one direction only, whichever direction that is. A feed the calendar subscribes to is one direction. Importing events the CRM cannot write back to is the other.
Fails if no external calendar sync exists at all.
Provider coverage is recorded but does not cap the verdict. A platform that syncs both ways against one mainstream provider passes, and the narrower coverage is stated in the evidence.
Act! documents two-way calendar synchronisation with both Google and Outlook, with configurable sync preferences, conflict handling and automatic scheduling of the sync. The Act! calendar is the view of the Activity object, and the API exposes Activities and Calendar as the same scheduling data, so it is the activity that syncs rather than a generic date field.
Calendar Feed publishes CRM tasks to Google Calendar, Apple Calendar, Outlook or any client that accepts a subscription calendar, filtered by task type, pipeline and owner. The vendor states plainly that the flow is one way: task changes made in the CRM reach the calendar, but changes or deletions made in the calendar are not reflected back in the CRM. Only incomplete tasks appear, and refresh frequency is set by the calendar client.
Event synchronisation runs in both directions with external calendars. For Office 365 the vendor states an automatic two way sync: an event created in the Office 365 calendar appears in Apptivo within minutes and an event created in Apptivo reaches Office 365 within seconds, once calendar sync is toggled on in preferences. For Google the vendor states that events can be created in Apptivo or in Google and sync automatically, with calendar sync and task sync toggled on under business settings after installing the Apptivo application from the Google marketplace. The object that syncs is the Apptivo event, the activity record created against a customer, contact or opportunity, not a date field on the opportunity.
https://answers.apptivo.com/questions/13525/how-do-i-sync-my-events-with-office365-calendar
https://www.apptivo.com/integrations/gsuite/google-calendar-crm-integration/
https://answers.apptivo.com/questions/12615/how-do-i-set-up-sync-services-in-my-account
https://answers.apptivo.com/questions/10313/how-do-i-create-new-event
Calendar sync connects Google Calendar or Outlook Calendar and imports events into Attio, where non-private events appear on the Activity tab of person and company records. The direction documented throughout is inbound only - Attio imports calendar events and continuously keeps them in sync - and no vendor page describes creating or editing an event in Attio that is written back to the external calendar. Meetings can be created through Attio's meetings API and logged manually on records, but neither route is documented as producing an event in the connected calendar. Attio's task object, the nearest equivalent to a schedulable activity, carries a deadline field with no documented calendar sync at all. One-way sync is partial under this dimension.
Events are one of the three activity types in Bigin's Activities module, and both calendar integrations sync that object rather than a generic date field. The vendor states that integrating Microsoft 365 or Outlook with Bigin synchronises contacts and events from Bigin to Microsoft 365 and the other way round, and that when a contact or event is added in one account it is updated in the other automatically. The Google integration is described in the same terms, with events and contacts activated separately. Synced Bigin events appear in Microsoft 365 under a dedicated Bigin Calendar category. The stated limitation is that recurring events are not synchronised, and contact sync with Google runs on a 24 hour cycle.
Connecting a Google or Outlook calendar syncs the user's upcoming meetings into the CRM, where the built-in recorder can join them automatically, and the help centre instructs users to ensure the email on the meeting invite matches the one held on the lead so that the meeting is filed against the right record, which is invite-level matching rather than transcript matching. The vendor states plainly that creating and updating invites from Breakcold does not exist, so nothing travels from the CRM outwards, and the sync is inbound only. The calendar connection is documented in vendor articles rather than appearing in the integration directory, which lists around thirty integrations and includes no calendar product.
Two separate one-way mechanisms exist and neither is a two-way sync. Outbound, Capsule publishes an iCalendar feed of the user's tasks that Outlook, Google Calendar or Mac Calendar can subscribe to, and the vendor states this is a one-way feed from Capsule to the calendar app with changes made only in Capsule. Inbound, a connected Google or Outlook calendar surfaces its events inside the Capsule calendar and contact sidebars, but the vendor states those events can be viewed and not edited in Capsule and that Capsule tasks do not appear in the connected calendar. Only one of the two calendar providers can be connected at a time.
The Meetings feature connects a Google Calendar or Office 365 Calendar and pulls scheduled meetings into Close, where they appear as meeting activities on the lead's feed and in the Inbox sidebar. Only events with an attendee matching a Contact on a Lead are pulled in, and internal or blocklisted domains are excluded. The documented flow is inbound only - vendor documentation describes meetings being pulled from the calendar into Close and does not describe creating a meeting in Close that is written out to the connected calendar - so the sync runs one way.
Calendar events are a two-way sync with Google Calendar: an event created on a Copper record is issued as a Google Calendar invitation, existing Google Calendar events are pulled into Copper against recognised record email addresses and logged in the activity log, and an update on either side is mirrored on the other. Two constraints apply. Tasks sync to Google Calendar in one direction only, into a Copper Reminders calendar carrying name, due date and due time, and vendor documentation describes no equivalent Outlook or Microsoft 365 calendar sync.
External calendar sync exists and it operates on the activity object rather than on a generic date field: connecting a Google or Microsoft account imports calendar events and files them as interactions on the matching contact profiles. It runs one way only. folk states that there is no back synchronisation with the source and that actions performed in folk are visible only in folk, and no vendor documentation describes creating or editing an external calendar event from within folk. Tasks carry a due date and generate in-app notifications, with no documented push to an external calendar. Declined events, events with twenty or more attendees, and daily or weekly recurring events are excluded from the import.
The vendor describes Google Calendar sync explicitly as a two-way sync in which meetings created in the CRM are added as events on the external calendar and events created on the external calendar are pulled back in as meetings. The sync operates on the meeting/appointment activity object, not on a generic date field, and synced events surface in the Activities dashboard and on contact records. An equivalent Office 365 calendar sync is documented.
Calendar sync works in both directions on the meeting activity object: a meeting scheduled in HubSpot is written to the connected Google or Outlook calendar and logged on the record, and an event created on the external calendar with an existing contact as guest appears on that contact's timeline. Constraints: only the user's primary calendar syncs, private events are excluded, and the separate task to calendar sync is one way only.
Calendar sync connects Google Calendar or Microsoft Exchange and Office 365, and events added, edited or deleted in either calendar update the other. Insightly Events are the object that syncs. Constraints: items originating in the external calendar cannot be edited inside Insightly, tasks and milestones sync out as separate read-only calendars, and invitations cannot be issued from Insightly.
Google and Outlook calendars can be connected. Vendor documentation states that external calendar events are displayed inside the Keap calendar and are used to block availability, but cannot be edited in Keap, and the Outlook article states that appointments booked through Keap are added to the Outlook calendar automatically. The Google article describes reading events into Keap and does not describe Keap appointments being written back, so the direction of sync is documented inconsistently between the two providers and is not a symmetrical two-way sync of the activity object.
Server-side synchronisation keeps appointments, contacts and tasks in sync in both directions with Exchange and Exchange Online, so the appointment activity object itself - not a date field - is mirrored to and from the user's Outlook calendar. The constraint is provider coverage: the supported configurations table records appointment, contact and task synchronisation as unsupported for Gmail and Yahoo mailboxes, which are limited to email, so an organisation on Google Workspace has no documented native calendar sync.
The monday CRM Google and Outlook calendar integrations pull external calendar events onto the contact's Emails & Activities timeline where the contact is an attendee, or is the creator with the connected account as an attendee - that direction is calendar into CRM. The reverse leg tied to the activity object is not documented: the Emails & Activities FAQ states that activities added to the Activities board after a calendar sync is set up are not automatically added to the calendar and that monday is working on making it possible, and manual timeline association does not yet support Calendar Meetings. A two-way board integration recipe does exist, but it maps a Date column on a board to a calendar event and creates board items from calendar events, which is column-to-calendar sync rather than the Meeting activity itself; the plain Calendar sync feature is explicitly one-way out of monday. Two-way Outlook calendar sync with Emails & Activities is an open request on the vendor community forum, with users reporting they resort to Make or Zapier.
Google Calendar and Microsoft 365 calendars connect to Nimble and the vendor describes the result as a two-way sync of events, which are the activity object rather than a date field on another record. Events created in Nimble reach Microsoft 365 on web and desktop immediately, while events created externally flow into Nimble hourly while a user is signed in and every three hours otherwise. Synced events appear on the Activities tab and on the Interactions tab of the related contact.
Two-way calendar sync is available for Google Calendar and Office 365. Activities scheduled in Nutshell are sent to the external calendar with date, time, location and attendees, and external calendar events can be synced back in as Nutshell activities, so an invitation received from a contact appears as a scheduled activity. The activity object is what syncs. Constraints: the sync can be configured one-way, historical events are not imported, and events whose only participants are Nutshell users are not created. A read-only ICS feed subscription is offered for other calendar applications.
Calendar sync connects Google, Exchange, Outlook or Office calendars. With two-way sync enabled, activities created in Pipedrive appear in the linked calendar and events created in the external calendar are created back as Pipedrive activities, with edits on either side updating the linked counterpart. A one-way option is also offered, and IMAP and POP configurations are not supported.
An Outlook calendar integration is authorised per user and the CRM calendar then shows a live reflection of the Outlook calendar alongside CRM tasks, with a refresh control to pull through changes made in Outlook. Events created in the CRM are written into the user's Outlook calendar and attendees receive the standard Outlook invitation, so traffic runs in both directions, but an event cannot be edited in the CRM once created and must be amended in Outlook. The integration is published as a Preview feature, only Microsoft Outlook is supported, and the vendor states Google Workspace support is planned rather than present.
Einstein Activity Capture syncs the Salesforce Event object with Microsoft Office 365, Exchange or Google calendars, and the sync direction is configurable as external-to-Salesforce, Salesforce-to-external, or Both Ways, with the external calendar winning on simultaneous edits. Documented constraints: custom fields are not synced between the two systems, the sync ceiling is 50,000 events per user, Salesforce-to-external propagation is slower than the reverse, and the connected mailbox must be the user's primary account in UPN format (aliases are unsupported) with one user syncing to one org only. Lightning Sync offered the same directional options but is closed to new customers and Salesforce states it retires in 2027, which leaves Einstein Activity Capture as the supported sync path; the Outlook and Gmail side panels are manual logging rather than sync.
A task carrying a due date is automatically created as an event in the user's Google Calendar, and changing the due date in Streak updates that event; clicking the event opens the associated box. Vendor documentation describes the flow only in that direction and does not describe an event created in the external calendar becoming a Streak task or activity, and no Google Calendar or Outlook calendar integration article appears in the integrations collection. The sync is therefore one-way from the activity object outward.
The activity object itself syncs, not a date field. The Exchange Connector synchronises contacts, events, tasks and emails between Vtiger and Microsoft Exchange, and the vendor states that events support two-way sync; the connector is documented for cloud accounts as well as self-hosted ones. A separate Google Contacts and Calendar integration syncs calendar events, with a Sync Direction setting chosen from three options per record type and a sync log. Constraints: the Exchange route needs a component installed on the Exchange server alongside the Vtiger component, and the three Google sync direction options are not named in the documentation reviewed.
Google Calendar synchronisation offers three modes - two-way, CRM to Google only, and Google to CRM only - and in two-way mode a change on either side updates the other. CRM entries sync out instantly while inbound Google entries arrive every few minutes, and the initial import is capped. A CalDAV option syncs meetings between the Zoho CRM calendar and an iOS calendar in both directions. Recurring events are excluded from both mechanisms.