Every connector shipped with the FU10 integration work, what it does, and the setup steps you do in the other system before you connect it in the console. Open Admin > Integrations, choose the connector, paste the values, then press Test connection (see Test connection for what each step checks and what its hints mean).
Rules that apply to every connector:
- Credentials are write-only. They are stored sealed in the company's keyring and are never shown again or written to logs.
- Each connector exposes AI agent tools where the vendor allows it. The AI agent only calls the tools you allow in the console.
- Every change is written to the audit log. A connector only sees data of its own company.
- A connector that needs an approval from the vendor (app review, partner program, Meta or Google review) can be installed and tested in a sandbox first. Production use waits for that approval.
The Integrations page
Admin > Integrations is split in two. On the left is a list: your installed integrations first, each with a status dot (green: working, red: failing, grey: not tested yet), then the catalogue grouped by category. Type in the search box to find a connector by name, or press a category chip to show only that category.
Choose an entry to see it on the right:
- What it does: caller pop-up, call log and the number of AI agent tools it offers.
- Data it reads and writes: what it reads from the other system, what it writes there, and what is kept on the PBX (the settings, and the credentials encrypted).
- Permissions and what you need: the console permissions (
integrations:read to view, integrations:write to change) and every setting and credential the form asks for, with the required ones marked.
- Setup steps and a link to the matching section of this page.
For an installed integration the panel also shows its status, when it was last tested, the last error, and the Test connection, Configure and Uninstall buttons.
The install form lists the required fields first. Credentials are masked: press Show to check what you typed. When you configure an installed integration, a stored credential shows as dots; press Replace to enter a new one, or leave it alone to keep it. AI agent tools are listed one per row with their description; only the tools you tick are offered to AI agents.
CRM
| Connector | What it does | Set up in the other system first |
|---|
| Kommo | Caller card with open deals, call log with recording link and AI summary, lead from an unknown caller, AI tools, WhatsApp conversation note | Register MonoPbx as an integration in Kommo (the operator does this once), then sign in with Connect. See Kommo, Bitrix24 and Odoo. |
| Bitrix24 | Same as Kommo | Register MonoPbx as an app in Bitrix24 (the operator does this once), then sign in with Connect. |
| Odoo | Same as Kommo, with open opportunities | Create an integration user and an API key. Odoo 17 and 18 also need the user id. |
| HubSpot, Salesforce, Zoho, Pipedrive, Odoo (template) and Zendesk Support | Caller lookup, search, create contact and call journal through a template | See CRM templates. |
Business systems and helpdesks
| Connector | What it does | Set up in the other system first |
|---|
| Zendesk | Caller pop-up with open tickets, ticket from a missed call or voicemail, call log and AI summary on the ticket, click-to-call | Either create an API token for an agent who can read and create tickets, or (if your operator registered MonoPbx as a Zendesk OAuth client) press Connect on the install: the connection replaces the token. Note your subdomain. Use a sandbox or trial account to test. |
| Freshdesk | Same as Zendesk | Create an API key in the agent profile settings. The agent needs ticket access. |
| ServiceNow | Incidents from calls and voicemail, call notes, caller pop-up | In the Application Registry, create an "OAuth API endpoint for external clients". Get a refresh token once with an authorization code. Enter the instance name, client id, client secret and refresh token, or (if your operator registered MonoPbx as the OAuth client of your instance) leave them empty and press Connect on the install. |
| Jira | Customer lookup, call notes, routing and click-to-call | See Connect Jira. |
E-commerce and orders (read only)
| Connector | What the AI agent can answer | Set up in the other system first |
|---|
| Shopify | Where is my order, product information (lookup by phone or order number) | Create a custom app in the store admin with read_orders, read_customers and read_products. Copy the Admin API access token. Use a development store to test. |
| WooCommerce | Order status and product information | Create a read-only REST API key. For tracking numbers, install the Shipment Tracking extension. |
| Mercado Libre | Order and product lookup | Create an application in the Mercado Libre developers portal. Enter the client id, client secret and a refresh token. |
| Tiendanube | Order and product lookup | Install a Tiendanube app on the store and enter its access token. |
| Amazon Seller Mexico | Order and shipment lookup by phone, order id or buyer message | Register an SP-API application in Seller Central. Enter the client id, client secret and refresh token. Tracking numbers appear for orders fulfilled through Amazon Multi-Channel Fulfillment (the app needs the Amazon Fulfillment role). |
| Liverpool and Coppel | Order and shipment lookup for marketplace sellers | Ask the marketplace for seller API access. Enter the base URL and API key it gives you. |
Payments
| Connector | What it does | Set up in the other system first |
|---|
| Stripe, Mercado Pago and Conekta | The IVR or the AI agent sends a payment link by SMS or WhatsApp, and the provider's webhook sets the result. No card number is ever taken on the phone. See Payment links. | Create a secret API key (Stripe sk_..., the Mercado Pago access token, the Conekta private key). Register the MonoPbx hook address in the provider's dashboard. Use the provider's test mode first. |
| Connector | What it does | Set up in the other system first |
|---|
| Rappi, DiDi Food and Uber Eats | Orders and customer messages in the inbox, "where is my order" answered by the AI agent, the restaurant calls the customer through the platform's masked number. See Delivery platforms. | Ask the platform for partner API access and sandbox credentials. Enter the client id and client secret, then give the platform the MonoPbx hook address. |
Hotels, medical and real estate
| Connector | What it does | Set up in the other system first |
|---|
| Cloudbeds | Room status, housekeeping, wake-up calls, reservation lookup from a call. See Hotels. | Create an API key for a sandbox property. Subscribe the webhook events for reservations. Check the field names with the property before go-live. |
| Opera (PMS) | Room status and room-to-room dialing | Ask your Opera contact for interface access and a test property. Check the field mapping against your property. |
| Doctoralia | Clinic slot search and booking by the AI agent, inside the clinic guardrails. See Clinics and real estate. | Your clinic needs a Doctoralia (Docplanner) partner integration with a sandbox. The clinic's address ids are entered in the connector. |
| Doctoranytime | Clinic slot search and booking by the AI agent, inside the clinic guardrails | Ask Doctoranytime for API access. Enter the API key, practice id and doctor id. |
| Fresha and Booksy | Salon and spa appointment booking and reminders by the AI agent | Get an API key from the vendor. Enter it with the location or business id, the service id and, optionally, the staff id. |
| Calendly | Find, book, move and cancel appointments; confirmation by WhatsApp or SMS | Calendly's Scheduling API needs a paid plan. Create a personal access token and one event type. |
| Cal.com | Same appointment tools as Calendly | Create an API key and pick the event types the agent may book. |
| Inmuebles24 | Real-estate leads answered and called back | Ask Inmuebles24 for lead API access for your advertiser account. Enter the account credentials in the connector. |
Field service
| Connector | What it does | Set up in the other system first |
|---|
| ServiceTitan | Customer and job lookup, job created from a call, technician status. See ServiceTitan and Jobber. | Register an app in the ServiceTitan developer portal. Use your integration tenant. Enter the client id, client secret and ST-App-Key. |
| Jobber | Customer and job lookup, job from a call, technician status | Authorize MonoPbx in Jobber (OAuth). Jobber rotates the refresh token; the connector keeps the newest one. |
Accounting and invoices
| Connector | What it does | Set up in the other system first |
|---|
| Alegra | Customer, invoice and balance lookup; call note on the customer | Create an API token in Alegra (a trial account works for tests). |
| QuickBooks | Customer, invoice and balance lookup; call note | Create an Intuit developer app, connect your company with OAuth (scope com.intuit.quickbooks.accounting). Use the sandbox company to test. Big books are fine: customers are found by phone from a short-lived index kept in memory only. |
| Xero | Contact, invoice and balance lookup; call note | Create a Xero developer app. Scopes: offline_access accounting.contacts accounting.transactions. Contacts are found by phone from a short-lived index kept in memory only. |
| CONTPAQi | Customer and invoice lookup, call notes | Install the on-premise bridge on the Windows computer that runs CONTPAQi. Give the bridge a TLS certificate and a DNS name. |
| Aspel SAE | Customer and invoice lookup, call notes | Same as CONTPAQi, with the Aspel SAE driver. |
| CFDI (SAT) | AI agent checks the SAT status of an invoice and re-sends it after identity checks | Open an account with a PAC (electronic invoice provider). Confirm that the SAT status service answers from the server's address. |
Marketing and parcels
| Connector | What it does | Set up in the other system first |
|---|
| Mailchimp, Brevo and RD Station | Call, chat and SMS outcomes become contact tags, a lead from a call joins an audience, opt-outs sync both ways | Create an API key (Mailchimp, Brevo) or an access token (RD Station) and pick the audience. |
| Estafeta, DHL and FedEx | The AI agent answers "where is my parcel" from a tracking number, read only | DHL: an API key. FedEx and Estafeta: a client id and client secret; set the environment to sandbox to test. |
| Connector | What it does | Set up in the other system first |
|---|
| Slack | Missed call, voicemail and queue notifications, transcripts and AI summaries to mapped channels; click-to-call from a slash command | Create a Slack app and install it. Enter the bot token and signing secret, then map events to channels. |
| Google Chat | Same as Slack | Create a Chat app. Enter the access token and hook token, then map events to spaces. |
Meetings, calendars and collaboration
| Connector | What it does | Set up in the other system first |
|---|
| Zoom | Escalate a call to a Zoom meeting, send the link to the caller | Create a Server-to-Server OAuth app with meeting:write:meeting:admin. Note the account id, client id and client secret. Run Test connection. |
| Google Meet | Escalate a call to a Meet link | Create a Google OAuth client and approve the Meet scopes. |
| Google Workspace | Attach Google Drive files to chats with a permission hint, and send chat messages by e-mail from each user's own Gmail. See Google Drive and Gmail in chats. | Create a Google OAuth client (Web application) with drive.readonly and gmail.send, and register https://<your PBX>/chat/google/callback as its redirect URI. |
| Microsoft Teams (Direct Routing) | Teams users call and receive PSTN calls through MonoPbx | Issue a public-CA certificate for the SBC name, add the DNS record, pair the gateway in Teams and set the voice route and policy. See Microsoft Teams Direct Routing. |
| Teams presence | Teams busy and in-call status changes the extension, and the reverse. See Teams presence and click-to-call. | Register an Entra app with application permissions Presence.Read.All, Presence.ReadWrite.All and User.Read.All. Grant admin consent and create a client secret. |
| Notion | Read-only knowledge source for the AI agent, with citations | Register a public Notion integration. Set the redirect URL and the webhook verification token. Share the pages with the integration. |
| Google Calendar and Microsoft 365 calendar | Calendar presence: in a meeting sets DND or forwarding | Sign in with the minimum read-only scope (calendar.events.readonly or Calendars.Read). Opt in per user. |
| Feature | What it does | Set up |
|---|
| Zapier, Make and n8n | Instant triggers through REST hooks; actions through the public API. See Zapier, Make and n8n apps. | Create an API key with integrations:write and the event permissions the trigger needs. |
| Outbound webhooks | Events to your own system | See Outbound webhooks. |
| BI feed (Power BI, Looker Studio, Metabase) | Read-only CDR, queue, SMS and AI views per company | Issue a credential and connect your tool. See BI feed. |
| Ads call tracking | Pool numbers per campaign, calls credited to campaign, keyword and ad | See Ads call tracking. |
| App marketplace | Partner apps reviewed by the operator, installed with scoped OAuth | See App marketplace. |
| SIEM export (Splunk, Elastic, Microsoft Sentinel) | Audit and sign-in events | Create a Splunk HEC token, an Elastic API key or an Azure data collection endpoint with rule, and enter them on the SIEM export page (setup). |
| Browser extension (Chrome and Edge) | Click-to-call on any number, caller pop-up | Load the unpacked extension in Chrome or Edge. |
| Website widget (call, chat, AI button) | One script tag on your website | Copy the snippet from the console and test it on a page with a live chat channel. |
| Twilio-compatible API | Moves Twilio code to MonoPbx by changing the base URL and credentials | Use an API key. See Twilio-compatible API for what is supported and the gaps. |
Second factor
| Feature | What it does | Set up |
|---|
| Duo MFA | Duo Universal Prompt as a second factor for console and app sign-in, per company, with fallback to the built-in TOTP | In the Duo admin panel create a Web SDK application. Enter its client id, secret and API host under security settings. |
Channels
| Channel | Set up in the other system first |
|---|
| Instagram direct messages | Meta app review for the messaging permissions, and a professional Instagram account linked to a Facebook Page. |
| Apple Messages for Business | Apple Business Register account, and a Messaging Service Provider with the Business ID. |
| WhatsApp Business Calling | Enable Calling on the WhatsApp Business number in Meta Business Manager and subscribe the app to the calls field. |