Add and Manage Servers
Add a server, test the connection, and manage its details and push registration.
Add the first server
On a fresh install, TriggerDeck opens the add-server form. To add another connection later, open More and tap Add Server.
Enter:
- a display name you will recognize later in multi-server switching
- the Zabbix base URL
- an API token with the browsing scope you need
Tap Test Server before saving. TriggerDeck checks the connection and shows the detected Zabbix version. Review the result, then save the server.
In the app
Add-server form
Add a display name, URL, and API token for the server. Use Test Server to check the connection before tapping Save Server.
In the app
Successful server test result
After you tap Test Server, a successful result shows the detected supported version. Check that result before tapping Save Server.
Edit an existing server
Open the server edit screen to:
- update display name, URL, or token
- review push registration state for that server
- copy the server-specific
UNIQUE_UID - open the push setup docs
- remove the server if it is no longer needed
Each server has its own push registration, cached monitoring data, and remembered view state. Check which server you are editing before changing its connection or push setup.
In the app
Edit-server flow with push ready
In Edit Current Server, Ready shows that push is configured for this server. Copy its UNIQUE_UID for Zabbix webhook setup, or open the docs link for setup help.
Where server data stays
- TriggerDeck saves server metadata locally and keeps API tokens in Keychain.
- Saving a server does not route traffic through the hosted backend.
- Changes to a server, including its push registration, apply to that server.