Communication · wired today

Gotify, wired into your agent workforce

Messages and calls are where work actually gets decided. The Gotify connector is one of 205 executable connectors and gives agents 2 read-only tools, with the credential held in the vault and every call receipted.

Connecting Gotify takes one credential

You provide server URL, app token from your Gotify account; Quox sends it as an API key sent as a header. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.

Where to get it: Gotify's own API documentation ↗ covers creating and scoping the credential.

What agents can run against Gotify

health

Check a Gotify server's health: the overall application state and its database connection (both 'green' when healthy)

version

Get the Gotify server's build information: semantic version, git commit hash and build date

Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.

How proven is this?

LIVE-PROVEN: every tool on this page was executed with real credentials against a real running Gotify instance (provisioned for the proof, then destroyed), and every call answered successfully. The strongest proof class a connector can carry before it runs inside your own deployment.

Gotify integration FAQ

What can Quox agents do with Gotify?

Agents can run 2 read-only tools against Gotify: health, version. Every call is receipted in the evidence trail.

What does the Gotify integration need?

You provide server URL, app token from your Gotify account; Quox sends it as an API key sent as a header. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.

Do agents see my Gotify credentials?

No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.

How proven is the Gotify connector?