Automatic Notion User Database Update from Calendly Invites - n8n Workflow

• Sales professionals and BDRs who use Calendly for booking demos and need clean data entry into their CRM or project tracker.


• Consultants and service providers who track client onboarding progress in Notion.


• Users searching for robust n8n templates to sync scheduling and database tools.


• Anyone who wants to leverage the power of n8n to eliminate manual data transfer tasks.

Manual data entry following a successful booking can be time-consuming and prone to errors. This specific n8n workflow solves that pain point entirely. By deploying this automation, every time a new meeting is booked via Calendly, the invitee's details are instantly captured by the n8n trigger and forwarded directly to a specified Notion database. This ensures your customer relationship management (CRM) data or project management lists are always up-to-date, reflecting immediate engagement without any human intervention. This efficient n8n template is essential for scaling operations and maintaining high data quality.

This automation begins with a specialized n8n trigger listening for specific booking events. The logic flow is straightforward and highly effective:

1. Calendly Monitoring (The n8n Trigger): The n8n workflow starts immediately upon receiving a webhook notification from Calendly. The Calendly Trigger n8n node is configured to listen specifically for the invitee.created event, which fires immediately after a meeting is booked.


2. Data Extraction: Once triggered, the n8n node extracts critical information from the incoming JSON payload, specifically the invitee's name and email.


3. Notion Database Update: The execution then passes to the Notion n8n node. This node uses the extracted data to create a brand new page (row) in a pre-defined Notion database.


4. Property Mapping: The invitee's name is mapped to the 'Name' title property, the email is mapped to the 'Email' property, and a default 'Status' select value is assigned, ensuring structured and consistent data across your n8n workflow implementation. This completes the fully automated process.

To deploy this powerful n8n workflow, follow these steps:

1. Import: Copy the provided JSON data and paste it directly into your n8n canvas using the 'New' button and 'Import from JSON' option.


2. Calendly Credentials: Locate the Calendly Trigger n8n node. You must set up and select your Calendly API Credentials. You may also need to configure a webhook in your Calendly settings pointing to the exposed webhook URL provided by the n8n trigger node once the workflow is activated.


3. Notion Credentials: Locate the Notion n8n node and set up your Notion API Credentials. Ensure the associated integration has access to the specific database targeted in this n8n template.


4. Configuration: In the Notion n8n node, you must update the Database ID (b40628ca-9000-4576-ab2c-4ed3c37e6ee4 in the input data) to match your target Notion database.


5. Property Matching: Verify that the 'Name', 'Email', and 'Status' properties exist in your Notion database, and adjust the internal IDs if necessary (especially for the 'Status|select' property).


6. Activation: Save the n8n workflow and click 'Activate' to start listening for new Calendly events. This makes the n8n template live.

Calendly Trigger (n8n node):
Function: This critical n8n trigger initializes the workflow. It acts as a webhook listener, waiting for events from your configured Calendly account.
Key Configuration: Configured to monitor only the invitee.created event, ensuring the n8n workflow runs only when a new meeting is successfully booked.

Notion (n8n node):
Function: Handles the final data action by writing the captured invitee details into a structured database within Notion.
Key Configuration:
Resource: Database Page (creating a new entry).
Database ID: Requires updating to match the user's intended Notion database.
Properties: Uses n8n expressions to dynamically map data:
Name: ={{$json["payload"]["invitee"]["name"]}}
Email: ={{$json["payload"]["invitee"]["email"]}}
Status (Select): Assigned a static internal ID, meaning the record is instantly tagged with a specific status (e.g., 'Booked', 'New Lead') upon creation by this n8n node.