Skip to content
Nappai Documentation

GoogleCalendarWebhook

The Google Calendar Webhook component allows you to automatically trigger actions in Nappai whenever something changes in your Google Calendar. It acts as a listener that watches for new events, modifications, or cancellations. When a change happens, this component captures the details and sends them to the rest of your workflow, enabling you to automate tasks based on your schedule updates.

How it Works

This component connects to the Google Calendar API. Once you set up the connection, it constantly checks for updates in a specific calendar. When Google detects a change (like a new meeting being added or an existing one being deleted), it sends a notification to Nappai. The component receives this notification, processes the information, and outputs the event details so other parts of your workflow can use them. For example, you could use this data to send a reminder, update a database, or notify a team member.

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 Google Calendar and fill in the required fields:
    • Select Project: Choose your Google Cloud Project.
    • Client Id: Enter your Google Cloud Project Client Id.
    • Client Secret: Enter your Google Cloud Project Client Secret.
    • Google Calendar access: Select the appropriate access permission.
  3. In your workflow, select the saved credential in the Credential input field of this node.

Inputs

Input Fields

The following fields are available to configure this component:

  • Calendar: Select the Google Calendar you want to monitor for event changes. Use the refresh button to update the list of available calendars based on your credentials.
  • Events: Choose which types of calendar changes should trigger the workflow. You can select multiple options:
    • Event Created: A new event is created in the calendar.
    • Event Updated: An existing event is modified.
    • Event Deleted: An event is cancelled or removed.

Outputs

The component produces structured data containing information about the calendar event that was processed. This data includes a readable summary and detailed metadata (such as start and end times, organizer, and status) that can be used by downstream components to perform actions like sending notifications or updating records.

Output Data Example (JSON)

json { “text”: “[created] Team Meeting”, “data”: { “event_id”: “abc123xyz”, “summary”: “Team Meeting”, “start”: { “dateTime”: “2023-10-25T09:00:00-05:00” }, “end”: { “dateTime”: “2023-10-25T10:00:00-05:00” }, “status”: “confirmed”, “organizer”: { “email”: “user@example.com”, “displayName”: “John Doe” } } }

Connectivity

This component is typically used at the beginning of a workflow to capture real-time triggers. You can connect its Data output to components that process information, such as:

  • Database nodes to log changes or update records based on calendar events.
  • Notification nodes (Email, Slack, SMS) to send alerts when events are created or deleted.
  • Logic nodes to trigger specific actions only for certain types of calendar updates.
  • AI Assistant nodes to analyze calendar changes and suggest next steps.

Usage Example

Automating Meeting Reminders and Follow-ups

Imagine you want to ensure your team is notified about new meetings and that follow-up tasks are created automatically.

  1. Connect a Google Calendar: Add the GoogleCalendarWebhook component to your dashboard and select the Calendar you want to monitor. Choose Event Created and Event Updated in the Events field.
  2. Trigger Actions: Connect the Data output to an Email component. Configure the email to send a reminder to the event organizer and attendees 15 minutes before the event starts.
  3. Update Records: Connect the Data output to a Database component. When a meeting is updated with a new location, the component automatically updates the project record with the new room number.

With this setup, you never miss a meeting detail, and administrative tasks are handled automatically.

Tips and Best Practices

  • Use Refresh Button: If you don’t see your calendar in the Calendar dropdown, click the refresh button to ensure the component fetches the latest list from Google.
  • Select Specific Events: Choose only the event types you need (e.g., only Event Created) to reduce unnecessary processing and make your workflow faster.
  • Secure Credentials: Ensure your Google Calendar credentials are kept safe and only shared with authorized users in your organization.
  • Monitor Output: When debugging, check the output data to ensure the event details match your expectations before connecting to other components.

Security Considerations

  • Credential Management: This component requires Google API credentials. Store these securely within Nappai and avoid sharing them publicly.
  • Data Privacy: The component processes calendar metadata such as event titles and times. Ensure that the data handled by your workflow complies with your organization’s privacy policies and data protection regulations.
  • Access Control: Restrict access to workflows containing this component to users who need to interact with calendar data to prevent unauthorized automation actions.