Skip to main content

​
Overview

Integrations covers everything that connects AmDital to the outside world: two deep, fully-built admin integrations (Slack and GreytHR), a browsable integration marketplace for connecting individual third-party tools, and the developer surface — API tokens, outbound webhooks, and the inbound MCP server that lets AI tools (Claude Code, Claude Desktop, Cursor, and similar) call into your workspace’s data. It isn’t in the main sidebar — reach it via Settings → Workspace.

​
Where to find it

​
Core workflows

​
Connect Slack

  • Slack is a full, production integration: channel notifications, slash commands, and presence sync feeding Attendance. Set it up once under Settings → Workspace → Integrations → Slack.

​
Connect GreytHR

  • GreytHR is a full, production integration for attendance, leave balances, and recruitment data sync between AmDital and GreytHR. Configure it under Settings → Workspace → Integrations → GreytHR.

​
Browse and connect a marketplace integration

  1. Open Integrations (/integrations) to browse the catalog by category — Communication, Productivity, Dev, HR, Finance, Storage, AI, Analytics, Marketing, Support.
  2. Each card shows its real state: Connect (OAuth-based, available now), Request Access (a non-admin asking an admin to enable it), Install/Configure (admin-only setup), or Coming Soon (cataloged but not yet built — several entries, including Microsoft Teams, Discord, GitLab, Bitbucket, Linear, BambooHR, Stripe, QuickBooks, Xero, Dropbox, OneDrive, PostHog, Mailchimp, and Zendesk, are in this state today).
  3. For an OAuth-based integration, Connect redirects into a real OAuth 2.0 + PKCE flow — but it only completes if your workspace admin has already configured that provider’s OAuth client credentials. Until then, Connect returns a “credentials not configured” error rather than silently failing.

​
Use the inbound MCP server

  • AmDital exposes a spec-compliant MCP server (/api/v1/mcp) so an external AI tool can call a set of read tools across nearly every module (CRM, Work, Marketing, HRMS, LMS, Recruitment, Finance, Docs, Reports, Goals, Support, AI, Activity, Clients, Calendar) plus a handful of Work write tools (create project/task/milestone/sprint, assign a project member).
  • Connect via an API key (Settings → Developer) or the in-browser OAuth consent flow — either way, the connected tool only ever acts with the permissions of the workspace member who authorized it. Manage or revoke a connected AI tool at Settings → Workspace → OAuth.

​
Permissions

Workspace-scoped. Admin/owner is required to configure Slack, GreytHR, or any marketplace integration’s credentials; a non-admin can request access to an integration an admin has enabled for the workspace.

​
Known limitations

  • The standalone Gmail and Google Calendar pages under /integrations/gmail and /integrations/google-calendar are leftover placeholders — their “Connect Account” button isn’t wired to anything. Use the main integration marketplace (/integrations) instead, where Google Calendar and Gmail appear as real catalog entries (still gated on your workspace’s own Google OAuth credentials being configured, as described above).
  • Several marketplace categories are mostly “Coming Soon” today (Finance and most of Storage, for example) — check each card’s own status rather than assuming a category is fully built out.