Skip to content
Nappai Documentation

Google Drive Webhook

This component acts as the starting point or trigger for automations related to Google Drive. It allows you to watch for changes—such as new files being added, existing files being modified, or files being deleted—and pass that information to other parts of your workflow. By using this component, you can automate tasks like organizing files, syncing data to databases, or sending notifications whenever a specific file changes.

How it Works

The Google Drive Webhook component works by connecting to your Google Drive account via an API. It acts as a listener that waits for notifications (webhooks) regarding file changes.

  1. Listening: The component checks for updates from Google Drive based on the folder you select and the types of events you choose to monitor.
  2. Processing: When a change occurs (e.g., a file is uploaded), Google sends a signal to Nappai. This component receives that signal and translates the raw technical data into a clear, structured format.
  3. Output: It outputs a data package containing details about the change, such as the file name, the type of change (added/modified/deleted), and when it happened. This data can then be used by subsequent components in your workflow.

If no changes are detected, or if the connection is empty, the component will output a message indicating “No data provided” or “No new events,” allowing you to handle empty states in your automation logic.

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 Drive and fill in the required fields (Select Project, Client Id, Client Secret, Google drive access). You can find your API key in the Google Cloud Console.
  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. Each field may be visible in different operations:

  • Watch Folder: Select the Google Drive folder to monitor for changes. If not selected, the entire Drive is monitored.

  • Events: Google Drive change events to listen for. Defaults to all if none selected.

    • File Added: A new file is created in Drive.
    • File Modified: An existing file is updated.
    • File Deleted: A file is removed or trashed.

Outputs

Output Data Example (JSON)

The component produces structured data about the detected changes. Below is an example of what the output looks like when a file is added or modified: json { “text”: “[added] document.pdf (application/pdf)”, “data”: { “event”: “added”, “fileId”: “123456789abcdef”, “fileName”: “document.pdf”, “mimeType”: “application/pdf”, “modifiedTime”: “2023-10-27T10:00:00.000Z” } }

If no changes are detected, the output might contain a simple status message: json { “text”: “No new events” }

Connectivity

This component is typically used as the start of a workflow. Because it outputs detailed information about file changes (such as file ID, name, and modification time), it should be connected to components that can process this data. Common connections include:

  • File Processors: Components that read or write to other files or databases.
  • Notification Systems: Components that send emails or Slack messages when a specific file changes.
  • Data Storage: Components that log changes into a spreadsheet or database for audit purposes.

The output from this component feeds directly into the next step, allowing you to react specifically to the file that triggered the event.

Usage Example

Scenario: Auto-Backup New Documents

  1. Add the Google Drive Webhook component.
  2. Set Watch Folder to select a specific folder like “Incoming Scans”.
  3. Keep Events selected for “File Added”.
  4. Connect the Output of this component to a “Copy File” or “Send Email” component.
  5. When a new PDF is dropped into that folder, the webhook triggers, and the next component automatically backs it up or notifies you.

Important Notes

Since the user_notes field is empty in the provided technical information, this section is omitted as per instructions.

Tips and Best Practices

  • Be Specific: If you only care about changes in a specific folder, use the Watch Folder input. Leaving it empty monitors the entire Drive, which can generate a large volume of notifications.
  • Choose Relevant Events: If you only need to react to new uploads, you can deselect “File Modified” and “File Deleted” in the Events input to reduce unnecessary processing.
  • Handle Empty States: Your workflow should be designed to handle cases where “No new events” are returned, ensuring the automation doesn’t break if no changes occur during a cycle.

Security Considerations

  • Credential Security: Ensure that the Google Drive credential configured in Nappai has the minimum necessary permissions (scopes) required for your workflow (e.g., read-only if you are only monitoring, or read/write if you need to modify files).
  • Data Privacy: The webhook processes metadata about files (names, IDs, modification times). Ensure that your workflow does not inadvertently expose sensitive file metadata to unauthorized users or components.