Skip to main content

Integrations — messaging, email, calendar

Integrations connect EnClaw to the systems your team already uses. They serve two roles:

  1. Tools for agents — agents can read messages, post to channels, send email, create calendar events, look up files.
  2. Platform infrastructure — the Teams integration also powers the platform's own outbound email (invites, password reset, verification). No Teams integration → no platform email → invite links must be shared manually.

For first-time setup the Microsoft Teams integration is the most important — it covers both roles in one shot.

Microsoft Teams (priority)​

Detailed guide: docs/integrations/channels/teams.md (in the repository).

What it does​

Allowed actionWhat it enables
Post messages to Teams channelsAgents can post in any channel the bot is a member of.
Send direct messages to usersAgents can DM specific users.
Send emails from EnClaw inboxPlatform invites + verification + reset emails. Most important for first-time setup.
Create calendar events from EnClaw inboxAgents can schedule meetings from a chat instruction.
SharePoint Lists (read / write / create)Agents can manage shared lists.
SharePoint SearchAgents can search files / list items across sites.

Quick setup checklist​

  1. In Entra ID: register a multi-tenant app for EnClaw's Teams bot. The EnClaw operator can share the canonical app registration template if you don't already have one.
  2. API permissions: Microsoft Graph Application permissions — Mail.Send, User.Read.All, ChatMessage.Send, Sites.ReadWrite.All (only the ones you want enabled).
  3. Grant admin consent for the app permissions.
  4. In EnClaw: /integrations → Microsoft Teams → Connect. Paste tenant ID, client ID, client secret. Pick the Outlook Send-From Email — the mailbox platform emails come from (e.g. no-reply@yourcompany.com, a shared mailbox is fine).
  5. Tick the Allowed Actions you want enabled — send_email is required for invite emails.
  6. Save. The page surfaces a Test button — click it to confirm the bot can authenticate.

Why platform email rides on Teams​

Rather than ship a separate Mailgun / SendGrid setup, EnClaw reuses your existing Teams integration:

  • One Azure AD app registration to manage instead of two.
  • No third-party email vendor account / API key / monthly bill.
  • Emails come from a real mailbox in your tenant (no-reply@yourcompany.com), so SPF / DKIM / DMARC are managed by Microsoft and inbox placement is excellent.
  • The same allowed-actions toggle your IT team already manages for the bot also gates platform email.

If you'd rather have a dedicated email pipeline (e.g. operator multi-tenant who doesn't want each customer's invites going from the customer's own mailbox), talk to your operator about provisioning a separate sender.

Slack​

If your team lives in Slack instead of Teams, the same flow exists in /integrations → Slack. Slack integrations don't currently power platform email — only Teams does that today. Invite emails will still fall back to the manual-share link if Slack is your only messaging integration.

Detailed guide: docs/integrations/channels/teams.md (in the repository) is Teams-specific; ask your operator for the Slack guide (TODO doc gap).

Other channels​

  • Reddit — read-only research. docs/integrations/channels/reddit.md (in the repository).
  • HubSpot — CRM lookups. docs/integrations/channels/hubspot.md (in the repository).
  • Google AI — actually an LLM provider despite the path, see LLM providers.

All channels follow the same pattern: connect once at /integrations, agents can use them after that.

What "active" means​

Channels have an Is active toggle. Inactive channels are kept in the DB (so credentials don't get lost) but agents can't use them and platform email won't be sent through them. Disable rather than delete when you want to temporarily turn a channel off.

Next​