Integrations

MonoPbx connects to the tools your company already uses in three ways. Pick the one that matches what you need.

You want to...	Use	Needs
Send a call or event to your own system as it happens	Outbound webhooks	integrations:write to manage endpoints
Look up callers in your CRM, record finished calls there, and dial numbers from it	CRM templates	integrations:write to manage integrations; contacts:read to look up contacts
Send and receive SMS through a provider	Connect any SMS provider	integrations:write; messaging:write to send
Keep users in step with a corporate directory	Directory sync	settings:write; users:write for a real run

Every integration is set up by an administrator (or a role with the matching permission), and every change to an integration is written to the audit log. Credentials you enter for an integration are write-only: they are stored sealed with your company's key and are never shown again.

Before you start

• Public HTTPS. Webhook receivers and template-based CRM or SMS providers must be reachable over https at a public name. MonoPbx refuses to call loopback, private-network, link-local and internal host names. For a lab, use a tunnel with a public name.
• Permissions are company-wide. The integration permissions cannot be limited to one department. A department administrator can use the tools inside their department only; they cannot manage integrations.
• Automation. Webhooks are the only automation channel in this release. The REST API covers everything else; it is documented in the API getting started guide.

Next steps

1. Read Outbound webhooks to receive call and presence events in your own system.
2. Read CRM templates to connect a CRM with a short description of its HTTP API.
3. Read Connect any SMS provider to connect an SMS provider without writing code.