Add a notification contact
add_notification_contactAdds an email address, chat channel, paging service, Jira project, webhook or phone number to alert on outages and recoveries. Email contacts must open a confirmation link before they receive alerts. A phone number texts or calls through the user's own account with a provider, on every plan, which bills them: twilio (Account SID, Auth Token) and plivo (Auth ID, Auth Token) text or call, vonage (API key and secret) and telnyx (API key) text. The user gives you the credentials and the sender, one of the account's numbers or for texts a sender ID of up to 11 letters and digits (not in the US or Canada). It needs no code: check it with test_notification_contact. sms and voice, through UpHeron's own Twilio account, are no longer added.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"name": "<name>",
"kind": "<kind>",
"destination": "<destination>"
},
"name": "add_notification_contact"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | Yes | Every plan alerts by email and through your own account with a texting provider, which bills you: `twilio` and `plivo` text or call, `vonage` and `telnyx` text (no code to confirm, send a test instead); the other kinds need a paid plan (pay-as-you-go workspaces: email, webhook, twilio, vonage, plivo and telnyx). `sms` and `voice`, texts and calls through UpHeron's own Twilio account, are no longer added (422 `phone_kind_retired`); contacts added before keep working and confirm with a code (`/alert-channels/{id}/confirm`). Push notifications to a device are added in the dashboard. | |
| name | Yes | Your name for the contact, such as "Ops email". | |
| token | No | Telegram bot token, Pushover application token, ntfy access token (optional), Jira API token, Twilio or Plivo Auth Token, Vonage API secret, Telnyx API key, or a webhook's signing secret (optional: `whsec_` and 24 to 64 bytes in Base64; one is made when it is left out). Stored encrypted and never returned, except a webhook's signing secret as `signing_secret` in the response that made it. | |
| options | No | opsgenie: `region` (us or eu, default us). splunk_oncall: `routing_key`. jira: `email` (the account the API token belongs to), `project` (key, such as OPS), `issue_type` (default Task) and `resolve_status` (optional: the status a resolved incident's issue moves to, such as Done). twilio: `account_sid` (AC…), `from_number` and `mode` (sms or call, default sms). vonage: `api_key` and `from_number`. plivo: `auth_id` (MA… or SA…), `from_number` and `mode`. telnyx: `from_number` and `messaging_profile_id` (needed for a sender ID; without `from_number` the profile's numbers send). `from_number` is one of the account's numbers with its country code, or for texts a sender ID of up to 11 letters, digits and spaces with at least one letter (not accepted in the US and Canada), or for twilio a Messaging Service SID (MG…). | |
| destination | Yes | Email address; webhook URL (slack, discord, teams, google_chat, mattermost, rocketchat, ntfy, webhook, zapier: its Catch Hook URL); Telegram chat ID; PagerDuty or ilert integration key, Pushover user key or Opsgenie API key; Splunk On-Call REST endpoint URL; Jira site URL (https://your-team.atlassian.net); or for twilio, vonage, plivo and telnyx the phone number to alert, with its country code (+359…). | |
| error_types | No | Alert about the outages of these kinds of errors only, and their recoveries; null or left out for every kind. timeout, connection (refused, reset, unreachable, no reply), dns, tls (handshake and certificate verification), http_5xx, http_4xx, http_status (other unexpected statuses), content (missing text, a failed JSON assertion, a wrong reply), slow (latency threshold, performance score), heartbeat (missed or failed runs), expiry (certificate and domain monitors) and other. Expiry reminders, vulnerability and port alerts are not filtered. |