Integrations Overview
Peerdom connects to your identity providers, chat tools, automation platforms, and external APIs. These integrations keep your organizational map in sync with the systems your team already uses.
Available integrations
- Single sign-on (SSO): Microsoft Entra ID, Google Workspace, and Okta provide single sign-on and user sync.
- Communication: Microsoft Teams lets you send messages directly from the map.
- Knowledge: Notion links your documentation to your org structure.
- Automation: Zapier, Pipedream, and n8n automate workflows between Peerdom and other tools.
- API: The REST API and Webhooks let you build fully custom integrations.
Best practices
- Pick your sources of truth. Decide which system owns each piece of data before you connect anything. Peerdom owns structure and roles; your identity provider owns people.
- Link before you automate. Start with manual links between tools. Automate only after you understand the data flow.
- Sync people, not everything. Focus user sync on the fields you need. Syncing unnecessary data creates noise and maintenance overhead.
- Keep flows one-way per field. Avoid bidirectional sync for the same field. If your identity provider owns email addresses, do not edit them in Peerdom.
Frequently asked questions
Can I use multiple integrations at the same time?
Yes. All integrations work independently. For example, you can use Microsoft Entra ID SSO for login, Microsoft Teams for chat, and Zapier for workflow automation simultaneously.
Do integrations require a specific Peerdom plan?
SSO and API access are available on paid plans. Contact Peerdom support for details on which integrations are included in your plan.
Where do I configure integrations?
All integration settings are managed in Organization Settings. You need Owner access rights to enable or modify integrations.
Related
- Single Sign-On (SSO), set up automatic login and user provisioning
- Microsoft Teams, send messages from your Peerdom map
- Zapier, connect Peerdom to thousands of apps
- Notion, link your documentation to your org structure
- API and Webhooks, build custom integrations with the REST API