Personalized Calendar View Generator for Baserow - n8n Workflow

Baserow power users who need distinct calendar views for different entities (e.g., clients, employees, suppliers).
Automation specialists looking for robust n8n templates to interact with database APIs.
Teams needing to integrate filtered Baserow data directly into external calendars like Google Calendar or Outlook via ICS feeds.
Developers utilizing n8n to manage data views and configuration programmatically.

This n8n workflow solves the complexity of manually creating and configuring many individualized Baserow calendar views. By leveraging the Baserow API, this powerful n8n template iterates through a defined list (such as employees or customers) and automatically sets up a dedicated calendar view tailored specifically to records associated with that entity. This n8n solution ensures that each user or entity receives a clean, filtered calendar feed, which is then made public via an ICS link and saved back to the database, drastically improving integration and data segmentation. This use of an n8n workflow streamlines complex configuration tasks.

The n8n trigger for this automation is a Manual Trigger, ideal for initial setup and testing.

1. Authentication: The n8n workflow begins by retrieving Baserow user credentials defined in the 'Set Baserow credentials' n8n node. It then uses the 'Create a token' HTTP Request n8n node to generate a JSON Web Token (JWT) access token via the Baserow authentication API.


2. Configuration: The subsequent 'Set table and field ids' n8n node stores the generated JWT Token and crucial Baserow IDs, including the Database ID and various table and field IDs required for view creation and filtering.


3. Data Retrieval & Iteration: The 'Get all records from filter table' Baserow n8n node fetches all source records (e.g., employee list). The n8n workflow then processes each record sequentially:

1. Final Update: Finally, the 'Update the url's' Baserow n8n node updates the originating filter table record with the newly generated Baserow View Link and ICS URL.

1. Import the n8n workflow: Copy the provided JSON data and paste it into your n8n instance using the 'Import Workflow' feature.


2. Baserow Credentials Setup: Navigate to the 'Set Baserow credentials' n8n node. Replace the placeholders (username> and password>) with your actual Baserow login details. Verify the API host path.


3. API Key Credential: Ensure the dedicated Baserow n8n node ('Get all records...' and 'Update the url's') is connected to an active Baserow API Key credential configured within your n8n environment.


4. Configure IDs: Open the 'Set table and field ids' n8n node. You must accurately populate all required numerical and string IDs for your Baserow application, including the Database ID, Date table, Filter table, and all associated field IDs (Date field, Filter field, Ics field, etc.).


5. Execution: Save the complete n8n workflow. You can test the setup by clicking 'Execute Workflow' on the Manual Trigger n8n node.

When clicking ‘Execute workflow’ (Manual Trigger n8n trigger): The starting point for this specific n8n workflow execution. Typically replaced by a production-ready n8n trigger like a schedule or webhook.
Set Baserow credentials (Set n8n node): Stores configuration variables like user credentials and the API host URL for dynamic use in subsequent HTTP Request n8n nodes.
Create a token (HTTP Request n8n node): Responsible for calling the Baserow authentication endpoint to exchange user credentials for a necessary JWT token, authenticating the Baserow API calls throughout the n8n workflow.
Set table and field ids (Set n8n node): Stores the critical JWT token obtained earlier, along with all Baserow table and field IDs needed to target the correct database resources for view creation and linking.
Get all records from filter table (Baserow n8n node): Fetches the dataset (the list of entities, e.g., employees) that the n8n workflow will iterate over to create individual calendar views for each item.
Create new calendar view (HTTP Request n8n node): Creates the actual calendar view using the Baserow API, configuring its name (dynamically based on the iterating item) and its date source field.
Create filter (HTTP Request n8n node): Adds a linkrowhas filter to the new view, ensuring the calendar view is highly specific and personalized to the current entity being processed by the n8n node sequence.
Share the view (HTTP Request n8n node): Sends a PATCH request to enable ical_public: true, generating the shareable ICS URL necessary for external calendar integration.

• Update the url's (Baserow n8n node): The final n8n node uses the Baserow Update operation to save the generated ICS feed URL and the internal Baserow view link back into the originating 'Filter table' record.