Tana Setup

This page will help you integrate EventLink into your Tana workflow.

To start using EventLink with Tana commands, add the Tana Template to your workspace. The template contains the commands and instructions to continue.

1. Start EventLink and accept the request to access calendar information.

Click Allow Full Access to allow EventLink to work properly.

1. Copy the Authorization header onto your clipboard.

Copy your authorization header

1. Press ⌘K to show the command menu, and type "Summarize my day"

A popup will appear.

Find the EventLink authorization header field, and paste it in.

1. A message will popup in the top right corner, and your settings page will automatically open. Paste the header you copied earlier in and you are done.

2. Re-run the command through ⌘K again, and it should summarize your day!

Adding EventLink to your #day tag

The best way to use EventLink is to import your events daily. You can easily make this a habit, by adding a button to your day tag.

Right-click your day tag to configure it.

Then, under AI and Commands, add the "Get events" command to your "Command palette"

Go to AI and commands.

You can @-search for the "↓ Events" command. Then close the configuration and you cna use the button every day to import your events.

Ensuring attendees are correctly tagged

Though we cannot ensure this always happens correctly, EventLink tries to import the name of attendees (and not their email). Unfortunately this does not work for every calendar supplier.

If names appear, but are not properly tagged, I suggest going to your meeting tag, and ensuring the "Attendees" field is of type "Options from supertag" with your #person tag selected.

Ensure your attendees field is correctly setup.

Customizing EventLink further

EventLink is very flexible and can be customized in many ways. From simple tweaks to returning a totally different format. Most customisations happen by editing the URL EventLink uses in its command. The command is in the imported template (by default it is called "↓ Events").

This is the default URL we use:

http://localhost:8080/events.tana?filterStatus=Cancelled&truncate=true&filterField=Identifier,Availability,Status,Start,End&timingField=Date&date=${sys:dateFromDayNode}

This URL:

• Filters "Cancelled" events

• Truncates video call additions from the notes field

• Removes the Identifier, Availability, Status, Start, and End fields.

• Sets the field name for the meeting's date and time range to Date

• Sets the imported date to the calendar node the command is run from.

Changing the meeting tag

Edit the command and change the default URL by adding &tag=custom_meeting at the end. Replace custom_meeting with the name of your meeting tag.

Not importing all calendars

You can either select with calendars to import, or filter the ones you do not want to import by adding &selectCalendar=Work or &filterCalendar=Personal to the end of the URL.

Removing yourself as an attendee

You can filter our specific attendees (like yourself) if you do not want to always see yourself pop up. Simply add &filterAttendee=YOUR_NAME at the end of the URL. Make sure your name matches the one in the calendar 100%.

Creating Tana searches for previous meetings of a recurring meeting

Edit the URL and remove "Identifier" from the filterField part of the URL. This will ensure an identifier field is imported along with your calendar events. This identifier will be the same for each instance of a recurring meeting and can be used in a Tana Search.

You can create a search like this and put it in your relevant content area.

Magic Tags

You can add specific rules to tag meetings depending on their title. Unfortunately, this is a bit of a power-user feature and thus is not as easy to use as the other things in EventLink. The feature is supported for both the default and custom Tana outputs.

The easiest way to get this running it to ask for ChatGPT's help. Customize the following prompt with the events you want to recognise and take the result of the url-encoded regex.

I want a regular expression that matches events with a titles like "Andre - Mihai", "Peter - Andre", etc. Return just the expression and url-encoded version of it.

Now update your url and add the following query parameter *-tag where * is the name of the tag you want to add to the matched events, and its value is the url-encoded version of the expression ChatGPT gives you. In the example above, I will update my url like so to add the 1-1 tag ot those meetings:

events.tana?1-1-tag=%5E%5Ba-zA-Z%5D%2B%5Cs-%5Cs%5Ba-zA-Z%5D%2B%24

This will add the 1-1 tag to any event where the title matches.

Note that although ChatGPT is smart, it will try to be too smart. Keep your examples simple and do not have a wide variety of titles, else it will not work. If you need multiple groups to match a single tag, you can add multiple expressions by splitting them with two underscores (i.e. ?1-1-tag=expression1__expression2)

Advanced

AI prompts

An example AI prompt

You can embed your calendar information into an AI prompt to ask the AI about your day, or summarize it, or extract specific information. Simply change the Prompt field to your liking.

Structured data (simple)

Return structured events

The default get events command returns meetings in Tana Paste format and will place each event tagged as 'meeting' into Tana. As you can see the URL can be customized to your liking.

Check out Endpoints for the parameters you can use in the URL.

Structured data (with your own template)

Return structured events based on your template

If you want full control, you can use the custom format command as a starting point. Simply change the payload to fit your needs and EventLink will return events in the format you want.

Check out Endpoints for the parameters you can use in the URL and fields you can use in the payload.

Creating Events

You can create events in any of your calendars using the 'Create event' command. You can fill the title, startDate, endDate, and notes from Tana.

Edit the payload in the command to ensure your Tana fields match the ones in the payload.

Note that you can use a range in Tana for startDate and endDate. Simply refer to them like this: ${Timing.start} and ${Timing.end}.