Google Workspace

Neudash has first-class Google Workspace support for the Google products that show up in real business workflows:

  • Gmail
  • Google Drive
  • Google Sheets
  • Google Calendar

For most teams, the default setup is straightforward: create a Google OAuth connection in Neudash and use the relevant trigger or process pattern from there.

What Neudash supports

OAuth

Neudash provides a managed Google OAuth client for standard setups. This is the fastest path when you want to connect Gmail, Drive, Sheets, or Calendar without maintaining your own Google app.

If you need your own Google app for branding, quota, or policy reasons, use the Google Custom OAuth Client guide instead.

Trigger and event coverage

Google Workspace support is not just “you can call the API.” Neudash has dedicated trigger logic for:

  • Gmail — mailbox-driven automation
  • Google Drive — file change detection
  • Google Sheets — row-level add, update, and delete events
  • Google Calendar — event create, update, and delete notifications

This means common Google workflows can run event-first instead of being rebuilt as brittle polling loops.

When to use Google Workspace in Neudash

Use Google Workspace support when:

  • email is the source of truth for part of the workflow
  • files in Drive should trigger downstream processing
  • Sheets acts like an operational database or handoff table
  • Calendar changes should drive tasks, notifications, or CRM updates

Notes on Sheets and Drive

Google Sheets and Google Drive are especially useful when a business already runs on shared operational spreadsheets and folders.

In Neudash:

  • Google Sheets is appropriate when row-level changes matter
  • Google Drive is appropriate when file-level changes matter

If the workflow depends on business records inside a spreadsheet, prefer Sheets. If it depends on document or file activity, prefer Drive.

Docs and setup paths

Recommended pattern

For most Google automations:

  1. Create or reuse a Google OAuth connection
  2. Choose the right trigger source:
    • Gmail
    • Google Drive
    • Google Sheets
    • Google Calendar
  3. Connect the trigger to a stream or process
  4. Keep the process logic focused on business rules, not auth plumbing

If you need something more custom

If a Google API is not covered by a dedicated trigger yet, Neudash can still use the OAuth connection in normal process code. The built-in support matters most for auth and event delivery; not every useful integration needs a bespoke provider surface.