- Two ways to connect a mailbox: delegated sign-in through Apivom's multi-tenant Entra app, or your own app registration with client credentials (right for shared mailboxes)
- Inbox and Sent Items synced into the customer timeline with Graph delta queries; support mailbox polled into tickets, attachments included; replies sent from the same mailbox with Graph sendMail
- Microsoft Teams notifications: one admin consent publishes the Apivom Teams app in your org catalog, Staff installs it per recipient and Iris alerts arrive as 1:1 chats
- Calendar events with a Teams meeting link created by Halo on the organiser's mailbox (app-only Calendars.ReadWrite, certificate credential)
- Scopes kept minimal: Mail.Send, Mail.ReadWrite, offline_access for delegated mail; your admin consents to exactly what the customer app needs
- 16,548 catalogued Graph routes (8,688 read-only) — Apivom products use the mail, calendar and Teams surface today
Microsoft Graph API Connector
Microsoft 365 through Microsoft Graph: Apivom Iris connects a mailbox (sign in once or bring your own Entra app), Apivom Staff syncs Inbox and Sent Items into the CRM timeline, turns a support mailbox into tickets and replies from it, Apivom Halo books Teams meetings, and Iris notifications reach your people in Microsoft Teams. 16,548 Graph routes catalogued.
What you can do
Use cases
- Customer e-mail on the account timeline — Connect each account manager's mailbox and let Staff file sent and received mail against the right company and contact automatically.
- Shared support mailbox → tickets — Point the support poller at support@ and every inbound message, with attachments, becomes a ticket; the reply goes back out from the same mailbox.
- Alerts where your team already works — Connect Microsoft Teams once as an administrator and Iris notifications — assignments, mentions, deadlines — reach each person as a Teams chat instead of another e-mail.
- Meetings booked by the assistant — Let Halo propose a slot and create the calendar event with a Teams link on the organiser's calendar, so the invitation reaches the customer from your own domain.
Microsoft Graph is the single API over Microsoft 365 — mail, calendar, users, Teams, SharePoint, Intune and more — and Apivom Atlas catalogues its full v1.0 surface, 16,548 routes. Apivom products use the mail, calendar and Teams part today, calling Graph directly with a token held encrypted in your tenant. In Apivom Iris an e-mail channel connects a Microsoft 365 mailbox either by delegated sign-in — the admin authorises Apivom's multi-tenant Entra app with mail scopes and Iris works as that user through Graph /me — or with your own app registration using client credentials, the right choice for shared mailboxes. Apivom Staff then syncs Inbox and Sent Items into the customer timeline with delta queries, polls a support mailbox so incoming mail, attachments included, becomes tickets, and sends replies from the connected mailbox with Graph sendMail. The Apivom Teams Connector lets one administrator connect the tenant: the Apivom Teams app is published in your org catalog, installed per recipient, and Iris notifications arrive as Teams chats. Apivom Halo uses the calendar side: with app-only Calendars.ReadWrite on an organiser mailbox it creates events carrying a Teams meeting link.
Delegated: OAuth code + PKCE through Apivom's Entra app (Graph /me, Mail.Send + Mail.ReadWrite + offline_access). Or your own Entra app: tenant id, client id, client secret, client-credentials token for Graph /users/{mailbox}. Tokens encrypted in your tenant; Apivom products call Graph directly.
Frequently asked questions
Which Graph permissions does Apivom need?
For delegated mailboxes: Mail.Send, Mail.ReadWrite and offline_access, consented by the user who signs in. For a customer app: Mail.Send and Mail.ReadWrite as application permissions (ideally restricted to specific mailboxes with an application access policy). For Teams notifications: an admin consent that lets Apivom publish its Teams app in your org catalog and install it for recipients. For Halo's calendar feature: Calendars.ReadWrite application permission on the organiser mailbox.
Does Iris read my whole mailbox?
It syncs the Inbox and Sent Items folders of the connected mailbox using delta queries, so only changes since the last run are read, and it files messages that match a known contact or company into the timeline. Other folders are not read.
Can I use the rest of Microsoft Graph?
The whole v1.0 catalogue is registered and documented in the AI integration guide (llms.txt), and the Iris integrations hub shows the route manifest and accepts an Entra app registration per the published credential contract. Product workflows exist today for mail, calendar and Teams notifications; other surfaces are scoped per customer.
Does Apivom charge per API call for this connector?
No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.
Where are my credentials stored and who can see the traffic?
Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.
More Atlas integrations
AI integration guide (llms.txt)
Machine-readable markdown — feed it to your AI assistant as integration instructions.