First-party integrations
Reach the Endstack agent remotely through its built-in email, Messaging, and Slack integrations.
First-party integrations are built-in ways to contact your Endstack agent when you are away from the desktop. Endstack supports email, iMessage/RCS/SMS through Messaging, and Slack.
Where to find them
Configure all three under Settings → Integrations.
Each integration has its own controls and setup requirements:
| Integration | What it provides | Setup details |
|---|---|---|
A {slug}@endstack.co inbox, approved remote-trigger senders, and the Mail app | Set up email | |
| Messaging | iMessage, RCS, and SMS access through an assigned agent phone number | Set up Messaging |
| Slack | Agent @mentions and direct messages from a connected Slack workspace | Set up Slack |
How remote conversations appear
First-party integrations map a remote sender to an Endstack identity before starting agent work:
- Email uses an approved-sender whitelist to decide which incoming messages can trigger the agent.
- Messaging uses phone pairing so text conversations map to your identity.
- Slack uses a per-user pairing code, and only members with an Endstack seat can use the connected Slack workspace.
Messaging and Slack conversations appear in endOS as external channels. An inbound email that triggers the agent typically appears there as well.
First-party and app integrations
These built-in connections are separate from App integrations. To connect third-party services such as GitHub, Supabase, Linear, Notion, or Gmail through Composio, see App integrations.