Properties¶
In addition to regular calendar event fields like title, description or location, your synchronization connections can also use additional pieces of information which we call "properties". This is especially useful for systems like Atlassian Jira or Clockodo which are not traditional calendars, but still deal with event-like data.
This page lists all available properties, grouped by the respective system. Use them with the following features:
- Conditions
- Transformers
Google Calendar¶
| Key | Description |
|---|---|
google:calendar.color.hex |
Default event color of the calendar, e.g. #ff9933. Used for displaying events that don't specify a color. Always present. |
google:color.hex |
Color specified for the event, e.g. #dbadff. |
google:color.name |
Color specified for the event, e.g. Grape. |
google:meet.code |
The Google Meet meeting code, e.g. aaa-bbbb-ccc. |
google:meet.url |
The URL to join a Google Meet meeting. |
Event colors
The color values given below are the ones recognized by the Google Calendar API. They are usually less saturated than their user interface counterparts.
| Color name | Value | Description |
|---|---|---|
| Tomato | #dc2127 |
Deep red |
| Flamingo | #ff887c |
Pale red |
| Tangerine | #ffb878 |
Orange |
| Banana | #fbd75b |
Yellow |
| Sage | #7ae7bf |
Pale green |
| Basil | #51b749 |
Deep green |
| Peacock | #46d6db |
Bright blue |
| Blueberry | #5484ed |
Deep blue |
| Lavender | #a4bdfc |
Pale blue |
| Grape | #dbadff |
Violet |
| Graphite | #e1e1e1 |
Gray |
Atlassian Jira¶
| Key | Example value | Description |
|---|---|---|
jira:issue.summary |
Reticulate splines to improve morale |
Summary field (title) of the associated issue |
jira:issue.key |
GOO-123 |
Key of the associated issue |
jira:issue.url |
https://jira.example.com/browse/GOO-123 |
Link to the associated issue |
jira:issue.id |
19392 |
Internal ID of the associated issue |
jira:worklog.comment |
Project kickoff meeting; write & publish meeting minutes |
Comment entered when work was logged (optional) |
jira:worklog.url |
https://jira.example.com/browse/GOO-123?focusedWorklogId=457727… |
Jumps to issue page & highlights the worklog to make editing easier. |
jira:worklog.id |
457727 |
ID of the worklog entry |
jira:project.name |
World of Goo |
Name of the project the issue resides in |
jira:project.key |
GOO |
Key of the project |
jira:project.id |
10001 |
Internal ID of the project |
Clockodo¶
| Key | Example value | Description |
|---|---|---|
clockodo:billable |
true |
true if the entry is marked as billable, false otherwise |
clockodo:customer.id |
1234567 |
ID of the customer, always present |
clockodo:customer.name |
ACME, Inc. |
Name of the customer (if known) |
clockodo:project.id |
7654321 |
ID of the project (if the entry has one) |
clockodo:project.name |
Spline Reticulator v2 |
Name of the project (if the entry has one and the name is known) |
clockodo:text |
Kickoff meeting |
Custom text of the entry (if entered) |
iCalendar¶
When connecting to a calendar via an iCalendar address, most event data is covered by regular ChronoLink conditions and transformers.
In addition, ChronoLink provides properties for each iCalendar text field, including vendor-specific ones. The respective property key is icalendar: followed by the field name turned into lower case and with dashes replaced by dots.
Examples
| iCalendar field name | ChronoLink property key |
|---|---|
SEQUENCE |
icalendar:sequence |
UID |
icalendar:uid |
X-MICROSOFT-CDO-IMPORTANCE |
icalendar:x.microsoft.cdo.importance |