Add and Manage Servers
Add your first server, verify connectivity, and understand the edit flow for push readiness and server changes.
Add the first server
TriggerDeck starts with a direct server connection. On a fresh install the add-server flow opens automatically. If you already have servers configured, open More and tap Add Server to create another one.
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
Use Test Server before saving. The app checks reachability and reports the detected Zabbix version so you do not save a broken configuration by accident.
Flow shown on screenshot
Add-server form
Open Add Server from More and fill Display Name, URL, and API token. Keep the full form plus Test Server and Save Server actions in view so this step clearly introduces the complete connection input before validation.
Flow shown on screenshot
Successful server test result
After filling server fields, tap Test Server and wait for a green success row with the detected supported version. Keep the result row and nearby action buttons in one frame so readers see exactly what confirms a valid connection before Save Server.
Edit an existing server
The edit flow is where TriggerDeck keeps server-specific maintenance tasks together:
- 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
This matters because TriggerDeck treats each server as its own working context. The push registration, cached reads, and remembered view state belong to that specific server instead of a single global session.
Flow shown on screenshot
Edit-server flow with push ready
Open Edit Current Server and focus on the Push Notifications section where status is Ready. Show UNIQUE_UID, copy hint, and docs link in one frame to explain that push identity and troubleshooting are scoped to the selected server.
What to explain in this step
- TriggerDeck saves server metadata locally and keeps API tokens in Keychain.
- Saving a server does not route traffic through the hosted backend.
- Editing one server should be presented as a scoped action for only that server, including push refresh behavior.