Skip to content

News

Update

Improvements

  • ChronoLink now supports a time condition for checking whether events are on certain days of week and/or within certain time ranges. Use this, for example, to synchronize private events to your work calendar only if they affect your usual working times. See the reference for details.

Update

Improvements

  • ChronoLink now displays the general status of each connection, current activity and the time it completed its last synchronization run. More importantly, the backend code that makes this possible enables us to diagnose problems much better than before.
  • Newly created connections with "Scheduled" trigger are now run immediately instead of after a random delay.

Update

Improvements

  • The names of condition and transformer components (e.g. daterange or append) and enumeration values (e.g. MEETING or ACCEPTED) can now be written in lowercase or uppercase letters (or any combination) as desired. Previously, they were required to be completely in lowercase or uppercase, respectively.

Fixes

  • When saving a connection, JSON properties of conditions and transformers were ordered alphabetically, leading to counter-inuitive orderings like "then - when". This is now fixed by saving properties in a predefined and meaningful order.
  • Fixed the reference documentation: the property to specify the keyword for the text condition is called search, not text.

Recipes

To get you started with ChronoLink, we published our first batch of recipes for common use cases:

  • Prevent collisions between company calendars
  • Publish a selection of events for stakeholders
  • Block days in your calendar based on an ICS feed

The recipes are available in a PDF on our documentation site.

Update

Improvements

  • Buttons to delete accesses and connections now require a second click for confirmation.
  • The UI now displays your short account ID for support purposes.
  • We added a footer that links to our documentation site site and the support portal.

Fixes

  • When you save a connection, ChronoLink always added all supported JSON properties to conditions and transformers, setting them to their default values (e.g. matchCase: false). This is no longer the case, but for existing connections, you need to remove the undesired properties manually.
  • After switching to a different account, you no longer see non-functional "add Google access" buttons for Google accounts linked to the other ChronoLink account.
  • The clickable area of the "add Google login" button no longer covers the entire width of the page.
  • Buttons in the access list now use proper margins.

Start of Closed Beta

Now that the first testers are using ChronoLink, we set up this page to keep them in the loop about any changes that we make.