Gotify notifications
Before you start
- Create an application in your Gotify server and copy its application token. A client token is not interchangeable with an application token.
- Enter the externally reachable server URL, including any installation subpath.
- Open the Gotify client using the account that owns the application. Choose the desired notification priority.
The server must be reachable from CertOne over the public internet. Private-network, localhost and reserved addresses are not supported. Use the final server URL directly; redirects are not followed.
Configuration
| Field | Required | Default |
|---|---|---|
| Server URL | Yes | — |
| Application token | Yes | — |
| Priority | Yes | 5 |
Test and enable
- In CertOne, add a notification target and choose this channel.
- Fill in the configuration and send a test message.
- Check that the message arrived at the intended destination, then save the target.
- Select the saved target in the settings for the notification events you need.
A successful API response means the service accepted the request. It does not prove that the final client or mailbox received it. If a request times out, delivery may already have occurred; check the destination before retrying.
Long messages are shortened to fit the channel limit and include a link to the console for full details.
Troubleshooting
- Use an application token, not a client token. The Gotify server must be reachable from CertOne.
- Check token permissions, account quota, destination ID and server reachability.
- Sensitive credentials are not included in returned error messages.