Skip to content
Nappai Documentation

Google Calendar Component

The Google Calendar Component acts as a friendly bridge between your Nappai automation workflows and your Google Calendar account. It allows you to automatically retrieve, create, update, or delete calendar events without needing to understand complex APIs or coding. Simply define what you want to do, connect your account, and the component handles the secure communication with Google’s servers to return the results you need for the next steps in your workflow.

How it Works

This component works by sending your instructions to Google’s Calendar service through a secure connection. When you configure it with your preferred action (like fetching upcoming events or creating a new meeting), the component packages that request and sends it to Google. Google processes the request, applies your calendar’s specific settings, and sends back a structured response. The component then unpacks this response into easy-to-use data blocks that you can pass along to other nodes, such as notification systems, data filters, or scheduling tools.

Connection & Credentials

This component requires configuring a credential in the Nappai panel before interacting with the external service:

  1. Go to the Credentials section in your Nappai panel.
  2. Create a new credential of the type specified for this component and fill in the required fields (API Keys, tokens, etc.).
  3. In your workflow, select the saved credential in the Credential input field of this node.

Operations

This component offers several operations that you can select based on what you need to do. You can only use one operation at a time:

  • Create: Adds a new event or calendar entry to your Google Calendar.
  • Get: Retrieves existing events, calendar details, or schedules based on your filters.
  • Update: Modifies the details of an existing calendar event or entry.
  • Delete: Removes a specified event or calendar entry from your Google Calendar.

To use the component, first select the operation you need in the “Operation” field.

Inputs

Mapping Mode

This component has a special mode called “Mapping Mode”. When you enable this mode using the toggle switch, an additional input called “Mapping Data” is activated, and each input field offers you three different ways to provide data:

  • Fixed: You type the value directly into the field.
  • Mapped: You connect the output of another component to use its result as the value.
  • Javascript: You write Javascript code to dynamically calculate the value.

This flexibility allows you to create more dynamic and connected workflows.

Input Fields

The following fields are available to configure this component. Each field may be visible in different operations:

  • Operation: Selects the action you want to perform.
    • Visible in: Create, Get, Update, Delete
  • Calendar Id: Enter the unique identifier of the calendar you want to interact with. If left blank during a Get operation, all your calendars will be returned.
    • Visible in: Get, Update, Delete
  • Calendar Selection: Choose a specific calendar from your linked Google Calendar account.
    • Visible in: Get, Update, Delete
  • Description: Provide a brief explanation or summary of the calendar or event.
    • Visible in: Create, Update
  • Input Type: Choose how you want to specify the calendar input.
    • Visible in: Get, Update, Delete
  • Mapping Mode: Toggle this on to enable batch processing and dynamic data mapping across your workflow.
    • Visible in: Create, Get, Update, Delete
  • Summary: Specify the name or title that will appear for the calendar or event.
    • Visible in: Create, Update
  • Tool Name: The identifier name that will be used when this component is connected as a tool.
    • Visible in: Create, Get, Update, Delete
  • Tool Description: A detailed explanation of what this tool does for agent configuration.
    • Visible in: Create, Get, Update, Delete
  • Tools arguments metadata: Defines the structural metadata for tool arguments.
    • Visible in: Create, Get, Update, Delete

Outputs

Once the component finishes processing your request, it provides the results through two main output ports:

  • Data: Contains the structured information returned by Google Calendar, such as event details, calendar metadata, or confirmation statuses. This is your primary output for passing information to downstream nodes.
  • Tool: Exposes the component as a reusable tool for other agents or automated processes within Nappai.

Output Data Example (JSON)json

{ “calendar_data”: { “id”: “primary”, “summary”: “Work Schedule”, “timeZone”: “America/New_York”, “accessRole”: “owner”, “events”: [ { “id”: “evt_123abc”, “summary”: “Team Sync Meeting”, “start”: { “dateTime”: “2024-11-15T09:00:00” }, “end”: { “dateTime”: “2024-11-15T10:00:00” } } ] }, “status_code”: 200, “errors”: [], “result”: “Operation completed successfully” }

Connectivity

This component is designed to fit naturally into time-based or scheduling workflows. Typically, you will connect the Data output to:

  • Notification Nodes: To send reminders via email, Slack, or SMS when events are created or updated.
  • Data Filter/Transform Nodes: To clean, sort, or map event details before storing them in a database or spreadsheet.
  • Scheduling or Routing Nodes: To trigger downstream actions only when specific calendar conditions are met (e.g., events within the next 24 hours).

The component’s output structure aligns well with standard dashboard data tables and conditional logic blocks, making it easy to branch workflows based on successful retrievals or creation confirmations.

Usage Example

Scenario: Automating Weekly Team Meeting Reminders

  1. Set the Operation to Get and leave Calendar Id blank to fetch all upcoming events.
  2. Connect the Data output to a date filter node that only keeps events happening within the next 3 days.
  3. Route the filtered data to an email or messaging node to automatically send reminder links to team members.
  4. If you need to create recurring slots, switch Operation to Create, fill in the Summary and Description, and map the output to a confirmation log node.

Important Notes

🔒 Protect Your Credentials 🔴 Keep your OAuth tokens and API keys secure. Never expose them in public scripts or version control. Store them in a protected environment variable or secret manager.

⚠️ Only Google Calendar Supported 🟡 This component works exclusively with Google Calendar. It cannot read or write to other calendar services such as Outlook or Apple Calendar.

📋 Google Account and OAuth Setup 🟡 To use this component you must have a Google account and grant the necessary OAuth permissions. Set up your Google API credentials before connecting the component.

💡 Filter by Date Range 🟢 When querying events, specify a start and end date to limit the amount of data retrieved. This improves performance and reduces network traffic.

⚙️ API Scopes and Permissions 🟡 Ensure the OAuth scope includes at least calendar.readonly for reading events. If you need to modify calendars, add calendar.modify scope. Using the minimal scope improves security.

ℹ️ Time Zone Handling 🟢 Event times are returned in the time zone configured in the Google Calendar settings. If your application expects UTC, convert the times accordingly to avoid confusion.

Tips and Best Practices

  • Always test your workflow in a sandbox or secondary calendar before applying automations to your primary account.
  • Use the Get operation with specific date filters to avoid overwhelming the API with large calendar datasets.
  • When creating events, keep summaries concise and descriptions clear to prevent formatting issues in downstream nodes.
  • Monitor the output status code to quickly identify if authentication or permission issues arise during automation runs.
  • Disable Mapping Mode if you only need to process a single calendar event to keep your workflow lightweight.

Security Considerations

This component relies on OAuth 2.0 authentication, meaning it requires your explicit permission to access Google Calendar data. Nappai handles token storage and refresh securely, but you should review the granted permissions in your Google Account settings. Avoid sharing workflow configurations that contain mapped credential tokens, and regularly rotate or revoke API access if a workflow is no longer in use.