Skip to main content
Triggr lists users and creates users and their extensions on 3CX systems running version 20 or later. Each system needs the licence 3CX requires for the Configuration API (an 8SC or higher AI licence).

​
Set up 3CX

Repeat these steps on each client’s system, with an API client just for Triggr: 3CX keeps one access token active per API client, so tools that share one sign each other out.
1

Add an API client

In the 3CX Admin Console, go to Integrations > API and click Add.
2

Set the Client ID

Use a value not already in use on the system, such as an unused extension number, and tick 3CX Configuration API Access.
3

Set Department and Role

Choose System Owner or System Admin to list and create users anywhere on the system.
4

Save and copy the API key

3CX shows the key only once.
5

Find the FQDN

It’s the 3CX Web Client address without https://, such as yourcompany.3cx.eu, or pbx.example.com:5001 if it has a port. It must serve HTTPS to the internet with a publicly trusted certificate; allow Triggr’s IP addresses through any firewall.
See 3CX’s Configuration API guide.

​
Connect it in Triggr

1

Open the client's configuration

Go to Integrations > 3CX and click Configure on the client’s row in the Per-Client Configuration card.
The Per-Client Configuration card listing Acme Corp and Globex, each Not Configured with Admin Consent Not Required and a Configure button.
2

Enter the API client's details

Enter the ClientID, the API key as ClientSecret and the FQDN, then click Save Configuration.
The 3CX configuration window with ClientID, ClientSecret and FQDN fields, an Allow insecure TLS switch under Advanced, and a Save Configuration button.
Per-client integrations never fall back to the Base Configuration, so every client whose workflows use 3CX needs its own row; the Base Configuration is only for workflows that don’t run for a client. If several clients are departments on one shared system, add a separate API client for each, scoped by its Department and Role. Create User takes 3CX’s user fields as JSON, with Id set to 0. See 3CX’s Create a User reference.

​
Troubleshooting

Configure the client on the Per-Client Configuration card, then run the workflow again.
Check ClientID matches the API client exactly and ClientSecret holds the full API key. If you’ve lost the key, add a new API client.
FQDN must be only the address and port, with no https:// or path, and reachable from the internet with a trusted certificate. Allow Triggr’s IP addresses if a firewall restricts it.
Something other than 3CX answered at the FQDN. Check it points at the 3CX system.
Another tool is using the same API client. Add one just for Triggr.
Check 3CX Configuration API Access is ticked on the API client, and that its Role is System Owner or System Admin, or covers the right Department.
The Number is already used by another extension. Choose a free one.