Skip to main content

Synchronize events & attendees between KlickTipp and Google Calendar

Workflow preview

Workflow preview
100%
Synchronize events & attendees between KlickTipp and Google Calendar preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Community Node Disclaimer: This workflow uses KlickTipp community nodes. Introduction This workflow creates a ...

Best for

  • Social Media automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-klicktipp.klicktipp, n8n-nodes-base.googlecalendartrigger, n8n-nodes-base.splitout, n8n-nodes-base.switch, n8n-nodes-klicktipp.klicktipptrigger, n8n-nodes-base.googlecalendar, n8n-nodes-base.filter

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by KlickTipp.

Original n8n.io source

1.1 Workflow description

Title
Synchronize events & attendees between KlickTipp and Google Calendar
Workflow name
Synchronize events & attendees between KlickTipp and Google Calendar

Community Node Disclaimer: This workflow uses KlickTipp community nodes.

Introduction

This workflow creates a complete two-way synchronization between KlickTipp and Google Calendar.
When a contact in KlickTipp is tagged, an event is automatically created in Google Calendar.
If event status changes or if attendees respond, their RSVP status and event status are reflected in KlickTipp — keeping your contact database, campaigns, and event insights always up to date.

Perfect for marketers, coaches, or event organizers who want to automatically send event invites and instantly capture participation status without manual updates.

How it works

Google Calendar → KlickTipp:

This template keeps your KlickTipp list in sync with Google Calendar across the full event lifecycle.
For every incoming event, the workflow follows these steps:

  1. Watch Google Calendar events

    • Listens for:
      • Event Created
      • Event Updated
      • Event Cancelled
  2. Iterate through attendees

    • Each attendee is handled as a separate item.
    • This ensures accurate contact updates and tagging even for large events or webinars.
  3. Filter attendees (optional)

    • Attendees from internal or excluded email domains can be filtered out before any processing.
  4. Check if the attendee already exists in KlickTipp

    • If the contact exists → update the contact.
    • If the contact does not exist → subscribe the contact (with Single or Double Opt-In, depending on action).
  5. Transfer event data to KlickTipp

    • Event details (summary, description, location, start and end time) are written into KlickTipp custom fields.
    • Contacts always reflect the most recent event information.
  6. Route by attendee response status

    • Attendees are routed based on their responseStatus:
      • needsAction → contact was added to an event
      • acceptedevent confirmed
      • declinedevent declined
      • tentativeevent considered
  7. Apply tags in KlickTipp

    • Based on event type and attendee status, the workflow applies the corresponding tags:
      • Event created / updated
      • Event canceled
      • Event confirmed
      • Event declined
      • Event considered

KlickTipp → Google Calendar:

  • Watches for a tag like “Send an event invitation via Google Calendar”.
  • Creates an event in Google Calendar using mapped KlickTipp fields.

Setup Instructions

  1. KlickTipp Preparation

    • Prepare custom fields - Google Calendar | event summary, data type: "Single line" - Google Calendar | event description, data type: "Single line" - Google Calendar | event location, data type: "Single line" - Google Calendar | event start datetime, data type: "Datetime" - Google Calendar | event end datetime, data type: "Datetime"
    • Prepare tags: - Google Calendar | event created/updated - Google Calendar | event canceled - Google Calendar | event declined - Google Calendar | event confirmed
      - Google Calendar | event considered - Send an event invitation via Google Calendar
    • Prepare outbound: - Activation tag: Send an event invitation via Google Calendar - Activation URL: webhook URL from trigger
  2. Credential Configuration

    • Connect your Google Calendar account using Client ID and Client Secret from the Google Cloud.
    • Authenticate your KlickTipp connection with username/password credentials (API access required).

Customization

  • Recommended poll frequency: every 1–5 minutes for near real-time updates.
  • Adjust to your local timezone if necessary.
  • Each trigger works independently, allowing partial deployments if only certain event types are needed.
  • Ensure End > Start in your data. If you prefer a fixed duration, compute End from Start + minutes in a Date & Time node.
  • If you want a Meet link, enable “Add Google Meet video conferencing” in the Calendar node instead of pasting a Calendar URL into Location.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - 1. Get event data.

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 2 - 2. Segregate attendees.

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 3 - 5. Check for contact.

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 4 - Documentation

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 5 - Transfer attendees cancellations

Type / Role
n8n-nodes-klicktipp.klicktipp - klicktipp
Config choices
Version 3

Block 6 - Sticky Note9

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 7 - Watch updated Google Calendar events

Type / Role
n8n-nodes-base.googleCalendarTrigger - googleCalendarTrigger
Config choices
Version 1

Block 8 - Watch cancelled Google Calendar events

Type / Role
n8n-nodes-base.googleCalendarTrigger - googleCalendarTrigger
Config choices
Version 1

Block 9 - Transfer the attendees' declines

Type / Role
n8n-nodes-klicktipp.klicktipp - klicktipp
Config choices
Version 3

Block 10 - Transfer the attendees' acceptances

Type / Role
n8n-nodes-klicktipp.klicktipp - klicktipp
Config choices
Version 3

Block 11 - Transfer the attendees' considerations

Type / Role
n8n-nodes-klicktipp.klicktipp - klicktipp
Config choices
Version 3

Block 12 - Iterate through attendees (event canceled)

Type / Role
n8n-nodes-base.splitOut - splitOut
Config choices
Version 1

Block 13 - Route by attendees' status

Type / Role
n8n-nodes-base.switch - switch
Config choices
Version 3.3

Block 14 - Iterate through attendees (event created)

Type / Role
n8n-nodes-base.splitOut - splitOut
Config choices
Version 1

Block 15 - 4. Route by status.

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 16 - Watch new Google Calendar events

Type / Role
n8n-nodes-base.googleCalendarTrigger - googleCalendarTrigger
Config choices
Version 1

Block 17 - Watch Tagging in KlickTipp

Type / Role
n8n-nodes-klicktipp.klicktippTrigger - klicktippTrigger
Config choices
Version 1

Block 18 - Create a Google Calendar Event

Type / Role
n8n-nodes-base.googleCalendar - googleCalendar
Config choices
Version 1.3

Block 19 - Route by attendees' status1

Type / Role
n8n-nodes-base.switch - switch
Config choices
Version 3.3

Block 20 - 6. Transfer event data.

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 21 - Check if attendee exists as contact

Type / Role
n8n-nodes-klicktipp.klicktipp - klicktipp
Config choices
Version 3

Block 22 - Transfer the event creation/update

Type / Role
n8n-nodes-klicktipp.klicktipp - klicktipp
Config choices
Version 3

Block 23 - 8. Segmentation.

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 24 - Check if attendee exists as contact1

Type / Role
n8n-nodes-klicktipp.klicktipp - klicktipp
Config choices
Version 3

Showing the first 24 of 38 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow Synchronize events & attendees between KlickTipp and Google Calendar
Complexity advanced
Nodes 38
Categories Social Media
Author KlickTipp
Published 29 Oct 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/10295/10295.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Synchronize events & attendees between KlickTipp and Google Calendar do?

Community Node Disclaimer: This workflow uses KlickTipp community nodes. Introduction This workflow creates a ...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Social Media use case.