Automation library · Scheduling

Synchronize events & attendees between KlickTipp

Started by an event in a connected app, and works across Google Calendar. 29 steps, 2 branches: large, and worth reading before you trust it with anything live.

Large

Download free
29 stepsLarge: read it before trusting it with anything live
2Branches: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 4Logic 8Service 17

The steps in the order they run, from what starts it.

  1. 1Watch updated Google Calendar eventsGoogle Calendar triggerStarts it
  2. 2Watch cancelled Google Calendar eventsGoogle Calendar triggerStarts it
  3. 3Watch new Google Calendar eventsGoogle Calendar triggerStarts it
  4. 4Watch Tagging in KlickTippKlicktipp triggerStarts it
  5. 5Iterate through attendees (event updated)Split OutLogic
  6. 6Iterate through attendees (event canceled)Split OutLogic
  7. 7Iterate through attendees (event created)Split OutLogic
  8. 8Create a Google Calendar EventGoogle CalendarService
  9. 9Filter attendees1FilterLogic
  10. 10Filter attendees2FilterLogic
  11. 11Filter attendeesFilterLogic
  12. 12Check if attendee exists as contact2KlicktippService
  13. 13Transfer attendees cancellationsKlicktippService
  14. 14Route by attendees' status1SwitchLogic
  15. 15Update contact in Klicktipp1KlicktippService
  16. 16Subscribe attendee to KlickTipp with SOI1KlicktippService
  17. 17Check if attendee exists as contact1KlicktippService
  18. 18Check if attendee exists as contactKlicktippService
  19. 19Route by attendees' statusSwitchLogic
  20. 20Update contact in Klicktipp2KlicktippService
  21. 21Subscribe attendee to KlickTipp with SOIKlicktippService
  22. 22Update contact in KlicktippKlicktippService
  23. 23Subscribe attendee to KlickTipp with DOIKlicktippService
  24. 24Transfer the event creation/update1KlicktippService
  25. 25Transfer the attendees' acceptancesKlicktippService
  26. 26Transfer the attendees' considerationsKlicktippService
  27. 27Transfer the attendees' declinesKlicktippService
  28. 28Transfer the attendees' acceptances1KlicktippService
  29. 29Transfer the event creation/updateKlicktippService

How it's built

Starts on
An event in a connected app
Steps
29, with 2 branches
Size
Large: read it before trusting it with anything live
Connects to
Google Calendar
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Google Calendar account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an event in a connected app.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Take your time. At 29 steps it is large: read it before trusting it with anything live.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 29 steps before you point it at anything that matters.