Integrations directory

Neudash integrations

This page is the fast way to see which providers Neudash handles directly, what kind of trigger or auth model each one uses, and where to go for setup details.

What to expect

  • Managed OAuth where it matters
    Google and Microsoft use Neudash-managed OAuth apps for fast setup.
  • Real trigger coverage
    Email, calendar, file, and spreadsheet integrations are event-driven where supported.
  • Fallback for long-tail APIs
    When there is no dedicated provider, Neudash can still work with standard REST APIs and tokens.

Google Workspace

Gmail, Drive, Sheets, and Calendar with first-class OAuth and event-driven triggers.

  • Managed Google OAuth client available
  • Built-in Gmail, Drive, Sheets, and Calendar integrations
  • Good fit for inbox, document, spreadsheet, and calendar workflows
Read Google Workspace docs

Microsoft 365

Outlook Mail, Outlook Calendar, OneDrive, and Excel with verified OAuth and row-level spreadsheet triggers.

  • Managed Microsoft OAuth client available
  • Outlook, OneDrive, and Excel coverage
  • Excel supports row-level add, update, and delete events
Read Microsoft 365 docs

Slack

Connect Slack to Neudash for channel-based workflows, agent access, and install-driven setup.

  • Workspace install flow built in
  • Used for interactive agent and channel workflows
  • Good fit for approvals, notifications, and conversation-driven automation
Read Slack docs

Zoho CRM

OAuth-backed Zoho setup for CRM-driven automations and event intake.

  • Zoho OAuth supported
  • Zoho CRM notification-based triggers available
  • Best for CRM workflows where Zoho is the system of record
Read Zoho docs

ServiceM8

OAuth-backed ServiceM8 setup with a public activation page and polling-based automation patterns.

  • Public activation page for the ServiceM8 add-on flow
  • OAuth callback handled by Neudash
  • Best current fit is schedule + REST polling
Read ServiceM8 docs Open ServiceM8 activation page

Custom APIs and tokens

Use generic secrets, OAuth connections, and normal REST patterns when there is no dedicated provider page yet.

  • API keys, bearer tokens, and service secrets stored securely
  • Agent can usually research a normal REST API and wire the integration
  • Good fit for long-tail SaaS tools and internal APIs
Read API and token docs Need another integration?