We’ve implemented a macro language in our titles that allows you to put a little bit of logic into the definition of a title. This syntax looks something like this:

  • Meeting with {{ Attendees }} -> expands to Meeting with <First name of each attendee>
  • Meeting with {{ Attendees or “TBD” }} -> expands to "Meeting with <first name of each attendee>” if there is an attendee, and “Meeting with TBD” if there are no attendees
  • There can even be some logic in here. For example: "Lunch {% if Attendees %}{{ Organizer }} | {{ Attendees }} {% else %}with {{ Organizer}}{% endif %}” will expand to:Lunch with Tim - if no attendeesLunch Tim | Burc, Bob, +1 - if there are 3 attendees

This is particularly valuable for published scheduling links (for example for client consultations), where the participant can't be known until the event is scheduled.

This syntax is already in Woven. You can use it by setting the title of any event with that logic, though it is much easier to just use this with templates. That way each time you select the template, when it is scheduled, the title of the event will get formatted. It can also be used with scheduling links.

Here are the specific fields we support:

  • Attendees - > The first two participants first names, “+N” where N is any additional number beyond 2, except the organizer
  • AttendeeFirstNames -> Synonymous with Attendees
  • AttendeeFullNames -> Same as Attendees but includes the Full name of the user
  • AttendeeDomains -> Same as Attendees but includes just the domain
  • Organizer -> The organizer’s first name
  • OrganizerFirstName -> Same as Organizer
  • OrganizerFullName -> The organizer’s Full name
  • AttendeesAndOrganizer -> The full list of Attendees First names including the Organizer
Did this answer your question?