Two-Way Event & Attendee Synchronization Between KlickTipp and Google Calendar - n8n Workflow

Marketers using KlickTipp for lead nurturing and event management.
Coaches or Consultants who schedule meetings and need instant status updates reflected in their CRM.
Event organizers needing automated contact tagging based on Google Calendar RSVP status.
Users looking for powerful n8n templates to handle complex, multi-application data flows.

• Technical users wanting to leverage the KlickTipp n8n node for robust synchronization.

This robust n8n workflow solves the critical challenge of keeping event data and attendee status harmonized across two distinct platforms: Google Calendar (for scheduling) and KlickTipp (for contact management and marketing automation). Without this n8n template, users face manual data entry, leading to outdated contact records and missed follow-up opportunities.

The power of this n8n workflow lies in its dual-direction capability. First, changes in Google Calendar (creation, updates, cancellations) automatically update the corresponding contact in KlickTipp, tagging them based on their response status (accepted, declined, tentative, or canceled). Second, the n8n workflow acts as an n8n trigger, monitoring KlickTipp for specific tags (e.g., "Send invitation"), and instantly generating a complete Google Calendar event using the contact's custom field data. Utilizing key n8n node types like filters, splitters, and switches ensures accurate processing of attendee lists and status updates.

This n8n workflow operates across two main data paths, each managed by specialized n8n trigger nodes:

Path 1: Google Calendar to KlickTipp (Status Sync)

1. Google Calendar Triggers: Three separate Google Calendar n8n trigger nodes initiate the flow based on event changes: eventCreated, eventUpdated, and eventCancelled. The trigger frequency is recommended to be high for near real-time updates.


2. Attendee Segregation: The data proceeds to an Iterate through attendees n8n node (Split Out), which processes each attendee's details individually.


3. Filtering: An n8n node Filter checks if the attendee's email domain should be excluded (e.g., filtering out internal staff).


4. Event Creation/Update Flow: If an event is created or updated, the attendee contact is synchronized in KlickTipp using the KlickTipp n8n node, mapping event details (summary, dates, location) to designated KlickTipp custom fields. They are then tagged as "event created/updated."


5. Status Routing (Event Updated Flow only): If an event is updated, the Route by attendees' status n8n node (Switch) inspects the attendee's responseStatus (accepted, declined, tentative, or needsAction).


6. KlickTipp Tagging: A series of KlickTipp n8n node actions apply the corresponding tag (e.g., event confirmed, event declined, event considered, or event canceled) to the contact's record.

Path 2: KlickTipp to Google Calendar (Event Invitation)

1. KlickTipp Trigger: The Watch Tagging in KlickTipp n8n trigger (using a webhook) initiates the flow when a contact receives a designated invitation tag (e.g., "Send an event invitation").


2. Event Creation: The n8n workflow uses the contact's custom field data (containing event details) to execute the Google Calendar n8n node, creating a new event and automatically adding the contact as an attendee. This process demonstrates the value of using n8n templates for complex scheduling tasks.

To leverage this powerful n8n workflow, follow these setup steps:

1. Import the n8n template: Copy the provided JSON code and import it directly into your n8n instance.


2. KlickTipp Preparation:

1. Calendar Configuration: Ensure all Google Calendar n8n node instances reference the correct calendar ID where events should be created or monitored.


2. Customization: Adjust the timezone mapping in the Google Calendar n8n node for event creation (Path 2) if your KlickTipp date formats differ from the provided example.


3. Activate: Set the n8n workflow to "Active" and run a test execution to confirm data mapping and synchronization success.

This n8n workflow utilizes several crucial n8n node types to manage the complex synchronization logic:

Google Calendar Trigger (Watch new/updated/cancelled Google Calendar events):
Function: Acts as the initial n8n trigger, polling Google Calendar for specified event changes (Created, Updated, or Cancelled) at frequent intervals.
Key Configuration: triggerOn is set uniquely for each node. Requires OAuth2 credentials.
KlickTipp Trigger (Watch Tagging in KlickTipp):
Function: This webhook-based n8n trigger listens for contacts being tagged in KlickTipp, initiating the calendar invitation process.
Split Out (Iterate through attendees):
Function: A crucial n8n node that splits the nested attendees array from the calendar event into separate items, allowing subsequent nodes to process each attendee individually.
Filter (Filter email domain):
Function: Used to prevent internal staff or test accounts from receiving tags or being processed by the n8n workflow. Checks if the attendee email notContains a specific internal domain.
Switch (Route by attendees' status):
Function: A core flow control n8n node that routes attendees based on the value of their responseStatus (declined, accepted, tentative, or needsAction).
KlickTipp Node (Create or update contact & Transfer tags):
Function: Executes contact creation/updating and applies specific tags based on event status or cancellation. Maps event details using expressions to KlickTipp custom fields.
Google Calendar Node (Create a Google Calendar Event):
* Function: Creates a new calendar event based on data retrieved from KlickTipp custom fields, ensuring the correct formatting for start and end times using date expressions in the n8n node.