Alexander Bentlund
Workflows by Alexander Bentlund
Sync Google Calendar events to Outlook
## What this workflow does This workflow is used as a bridge between your private Google Calendar to your Work Outlook Calendar. The same mentality can be used with other calendar types. ## Description Send a copy of a Google Calendar event to your Outlook work account as a reminder to yourself or co-workers that you are booked for private matters like "Dentist appointment", "Taking kids to Disney Land" etc. ## How it works - Create event -- You create a Google Calendar event. -- A trigger in n8n reacts and collects the event info. -- An Outlook event is created with the same information in your Outlook Calendar. - Cancel -- You cancel an event in Google Calendar -- A trigger in n8n reacts and collects the canceled event info. -- Using the Outlook node to getAll events searches for the event in your Outlook Calendar. -- If the event is found it is then deleted. -- An email with the details of the cancelation is then sent to your Outook e-mail address. The n8n Merge node is used to combine results from two different nodes that are necessary to create the cancelled event e-mail notification. ## Important notice Make sure you use a dedicated Google Calendar for private events that will be displayed in your work Outlook calendar in order to avoid displaying unwanted calendar events that you do not wish to share with your co-workers. ## Requirements - Active workflow* - Google Calendar OAuth2 API - Microsoft Outlook OAuth2 API .*The Google Calendar trigger is activated only if this workflow is active. You can however TEST the workflow in the editor by clicking “Test step”. You will then receive a response from Google Calendar that you can use in order to view what data Google Sends.
Telegram to Spotify with OpenAI
**Search music and play to Spotify from Telegram** This workflow is a simple demonstration on accessing a message model from Telegram and it makes searching for songs an easy task even if you can't remember the artist or song name. An OpenAI message model tries to figure out the song and sends it to an active Spotify device**. **Use case** Imagine an office where you play music in the background and the employees can control the music without having to login to the playing account. **How it works** - You describe the song in Telegram. - Telegram bot sends the text to n8n. - An OpenAI message model tries to find the song. - Spotify gets the search query string. - First match is then added to queue. -- If there is no match a message is sent to Telegram and the process ends. - We change to the next track in the list. - We make sure the song starts playing by trying to resume. - We fetch the currently playing track. - We return "now playing" information to Telegram: Song Name - Artist Name - Album Name. **Error handling** - Every Spotify step has it's on error handler under settings where we output the error. - Message parser receives the error and sends it to Telegram. **Requirements** - Active workflow* - OpenAI API key - Telegram bot - Spotify account and Oauth2 API - Spotify active on a device** .* The Telegram trigger is activated only if this workflow is active. You can however TEST the workflow in the editor by clicking "Test step" and then it waits for the Telegram event. When event is received, just step through all steps or just clicking "Test step" on the "Fetch Now Playing" node. .** You must have a Spotify device active when trying to communicate with a device. Open Spotify and play something - not it is active.