Integrations
Peerdom is your organization’s living map. Integrations pull key signals from the tools you already use and make them visible in context, appearing right next to the teams, roles, and projects that own the work.
At a glance
- Sign‑on (SSO & login management)
- Microsoft Entra ID · Google Workspace · Okta
- Secure access, single identity, optional login restrictions.
- Employee directories (people sync)
- Entra ID · Google Workspace · Okta
- Auto‑import names, emails, avatars; keep profiles current.
- Communication tools (chat)
- Microsoft Teams
- Start the right conversation from the map (peer, role, group).
- Knowledge bases / docs
- Notion (today via links + light automations)
- Keep docs where they belong; link them to owners on the map.
- Automation platforms
- Zapier (and Pipedream via API)
- Trigger cross‑tool workflows without writing code.
- Peerdom API
- Build your own workflows and data pipes.
Start with links (lowest friction), add one‑way sync for key fields, and reach for automations when they clearly save time. Peerdom complements your tool stack; it doesn’t replace it.
Quick links
Sign‑on & Directories
- Microsoft Entra ID SSO — setup & optional group‑based restrictions
- Google Workspace SSO — setup & optional group‑based restrictions
- Okta SSO & Sync — login (SAML) + people sync (API Services)
Communication
- Microsoft Teams - direct messages from Peerdom
Knowledge base / docs
- Notion - connect orientation with execution
Automation
- Zapier ↔ Peerdom - triggers & actions, 7,000+ apps
- Pipedream - low‑code alternative
API
Recommended setup
- Pick sources of truth. Structure & ownership live in Peerdom; docs and task details live in your document/task tools.
- Link first. Add stable URLs from roles/teams/projects in Peerdom to their corresponding docs and boards.
- Sync people, not everything. Use your directory to keep names, emails, and avatars current. Avoid bi‑directional mirroring of rich text.
- Prefer one‑way flows per field. If a status is mastered in another tool, surface it read‑only in Peerdom.
- Own the automation. Nominate an Ops/IT owner, keep a lightweight change log, and store credentials securely.
Capabilities by category
Sign‑on & directories
- Log in with your corporate identity (SSO).
- Restrict login to a specific group if needed.
- Keep people data current by syncing first name, last name, email, and avatar.
Communication
- Launch a chat to a peer, all holders of a role, or members of a group directly from the map.
Knowledge base / docs
- Link Notion pages (or database rows) to roles, teams, and projects.
- Optionally write the Notion URL back to Peerdom automatically.
Automation
- Use Zapier to react to events in Peerdom (e.g., new peer, new team) and perform actions in other tools.
- Use Pipedream/low‑code scripts for advanced or custom flows.
API
- Create API keys in Peerdom and build custom syncs or dashboards with the REST API.
Need help?
If you’d like us to review your setup or propose the simplest approach to connect your tools, contact support@peerdom.org.