Docs

Notification Triggers

Send a notification from a deployment, script or external service by calling a dedicated URL.

A notification trigger is an inbound URL that dispatches a message through the active integrations linked to it. It is useful when an external process needs to notify your team but is not itself monitored by an uptime monitor or heartbeat.

Use a trigger for events such as “deployment finished”, “backup failed” or “manual intervention required”. For recurring jobs that must report on time, use a heartbeat instead.

Creating a notification trigger

1

Choose Notification Triggers

Open the Notification Triggers section in your project and click Create trigger.

2

Set the message

Give the trigger a descriptive name and set a default message. The default is used when the request does not provide a custom message.

3

Link integrations

Attach the active integrations that should receive the message when the URL is called.

4

Copy the trigger URL

Store the generated URL in your deployment or automation system and keep it private if token protection is enabled.

Firing a trigger

Call the generated URL from a script or service. Both GET and POST requests are supported:

curl -X POST "https://api.upcron.io/api/notify/YOUR-TRIGGER-ID"

To send a message for a single call, include the message parameter:

curl -X POST "https://api.upcron.io/api/notify/YOUR-TRIGGER-ID" \
  --data-urlencode "message=Deployment finished successfully"

When the trigger fires, Upcron dispatches the resolved message through its active integrations and records the event, timestamp and fire count.

Rate limits

Set an optional maximum number of calls per second, minute, hour or day. Rate limits protect an integration from accidental loops or repeated deploy callbacks. Leave the limit empty when the trigger should accept every call.

Token protection

Enable token protection when the URL may be exposed outside your controlled infrastructure. Upcron generates the token once after creation. Provide it either as a bearer token:

curl -X POST \
  -H "Authorization: Bearer YOUR-TOKEN" \
  "https://api.upcron.io/api/notify/YOUR-TRIGGER-ID"

or as a token query parameter. Store the token in a secret manager and do not commit it to a repository.

Best practices

  • Use one trigger per meaningful external event rather than one generic URL for everything.
  • Use descriptive names and default messages so a notification is understandable without extra context.
  • Protect triggers that can be called from public or semi-public systems.
  • Use the trigger event count and last-fired time to spot accidental loops.
  • Pause a trigger temporarily instead of deleting it when the external process is under maintenance.

Troubleshooting

Trigger fired but no notification arrived
  • Check that the trigger is active and has an active integration attached
  • Check the integration provider configuration and send a test notification
  • Review the trigger event count and last-fired time
Request is rejected
  • Check that the request uses GET or POST
  • Verify the bearer token or token query parameter
  • Check whether the configured rate limit has been exceeded
Need scheduled silence detection instead
  • Use a heartbeat when a recurring job must report that it ran on time
  • Use a notification trigger for one-off or externally initiated messages