Integrations

Twitter alerts

Automatically publish incident updates from Uptime to your organisation’s Twitter account. Alerts are posted with the Twitter v2 API using your app’s bearer token while respecting channel visibility to keep sensitive data out of public timelines.

← Docs home Manage alert channels

Prerequisites

  • An Uptime plan that allows Twitter alert channels.
  • Access to a Twitter developer account with tweet.write permissions.
  • The Twitter username (handle) that should publish incident updates.

Generate a bearer token

  1. Visit developer.twitter.com and create or select a project/app with Elevated access.
  2. Under App settings → User authentication settings, enable OAuth 2.0 App-only authentication and grant the tweet.write scope.
  3. Create a new App-only Bearer Token. Save the token securely—the Uptime dashboard needs the full value.
  4. Confirm which Twitter handle will be used to post alerts. The account linked to the token must own or be authorised for that handle.

Add the Twitter channel in Uptime

  1. Go to Dash → Alerts → Channels and click New channel.
  2. Select Twitter as the channel type.
  3. Enter the account handle (with or without the leading @). Uptime stores the handle in lowercase for deduplication.
  4. Paste the OAuth 2.0 bearer token you generated in the previous step. The token is required to tweet alerts.
  5. Choose a Visibility level. Public channels omit sensitive values (like IP addresses) from tweets.
  6. Save the channel, then attach it to the monitors that should broadcast incidents via Twitter.

Customise the tweet template

Twitter channels use the same templating engine as other alerts. The rendered text becomes the tweet body, with monitors linked automatically. Keep the result under 280 characters—Uptime truncates longer messages with an ellipsis.

Popular placeholders:

  • {monitorName} — Monitor name.
  • {status} — Current status (DOWN or UP).
  • {incidentDuration} — Human-readable downtime length.
  • {monitorUrl} — Dashboard link (appended automatically if missing).

Visibility settings still apply. Public channels replace sensitive placeholders (like IP addresses) with safe descriptions before tweeting.

Testing & best practices

  • Use the Send test button on the channel to publish a sample tweet and verify the formatting.
  • Consider connecting a staging Twitter account first to review messaging without notifying followers.
  • Rotate the bearer token if it is ever exposed. Update the channel so production alerts continue tweeting.
  • Pair Twitter alerts with maintenance windows to avoid noisy tweets during planned downtime.

Removing the connection

Detach the Twitter channel from all monitors or delete it from Dash → Alerts → Channels to stop posting. You can also revoke the bearer token in the Twitter developer portal for an immediate cutoff.