Plivo alerts

Send kwatch incident alerts to Plivo. Use the interactive manager for installation and credential setup. This page explains the provider fields and shows a minimal configuration fragment.

Before you start, have these values ready:

• authId — Auth ID.
• authToken — Auth token.
• from — Sender number.
• to — Recipient phone number.

Credentials, tokens, keys, passwords, and webhook URLs must be mounted from a Kubernetes Secret. Use an exact ${file:/absolute/path} reference for every field marked Secret.

Configuration

Field	Type	Required	Secret	Validation	Default	Description
authId	string	yes	yes	—	—	Auth ID
authToken	string	yes	yes	—	—	Auth token
from	string	yes	no	—	—	Sender number
to	string	yes	no	—	—	Recipient phone number
routes	json	no	no	json	—	Optional JSON route filters.
retry.maxAttempts	integer	no	no	integer	—	Optional maximum retry attempts.
retry.delay	string	no	no	—	—	Optional retry delay, for example 5s.
fallback	string	no	no	—	—	Optional fallback provider name.

Minimal example

alert:
  plivo:
    authId: "${file:/config/plivo-authId}"
    authToken: "${file:/config/plivo-authToken}"
    from: <from>
    to: <to>

Add routes, retry, and fallback when you need delivery filtering or recovery. See the channels overview for guidance, or the complete provider reference for the catalog-wide view.