INTEGRATIONS · Email & messaging
Email & messaging
Most work arrives as a message. Edrak connects to Outlook, Gmail, Teams and Zoom, so the email that starts a workflow can start the mission, in the inbox your team already uses.
What Foundry reads
- Incoming mail, parsed into structured requests
- Threads and attachments, with their history
- Messages and channel context
- Meetings, transcribed into decisions and actions
What Atlas writes back
- Drafted replies, held for your review
- Status updates posted where the team works
- Actions filed to the system of record
- Every send under explicit authority
A message is a trigger, never a blind spot. Foundry grounds the response; Atlas moves the work it started.
How the connection behaves
The same rules as every Edrak connection
- Reads under permission
- Retrieval respects the source system's access model. People and agents see only what they are allowed to see.
- Writes under authority
- Actions execute only where authorized, with approvals where your rules require them.
- Audited end to end
- Every read and write lands on the audit log with its authority, evidence and author.
One connection among many.
Native connectors and MCP, all behind the same governance plane.
Explore Integrations & MCP →