Alerts — IFTTT / WhatsApp

Reach WhatsApp, SMS, email, and hundreds of other services by pointing a Webhook alert at an IFTTT trigger.

About alerts

An alert watches your incoming log stream and fires a notification whenever an entry matches all of its conditions. Each alert can have multiple delivery channels. Use the Test button to fire a sample notification immediately, and the Alert Log to review delivery history.

Match conditions
ConditionHow it matches
LogspaceRestrict to a specific logspace, or leave blank to match all.
LevelExact match — e.g. ERROR only fires on error-level entries.
Program containsCase-insensitive substring match on the program field.
Message containsCase-insensitive substring match on the message field.
How it works

IFTTT's Webhooks service accepts an HTTP POST and can forward it to any Then That action — including WhatsApp, SMS, email, push notifications, and smart home devices. BunnyLogs sends the POST via a Webhook alert channel, so no extra integration is needed.

Setup
  1. In IFTTT, create a new applet with Webhooks as the If This trigger. Use an event name such as bunnylogs_alert.
  2. Choose any Then That action — WhatsApp, SMS, email, etc.
  3. Copy your IFTTT Webhooks URL:
    https://maker.ifttt.com/trigger/bunnylogs_alert/with/key/YOUR_KEY
  4. In BunnyLogs, go to Alerts, create or edit an alert, and add a Webhook channel.
  5. Paste the IFTTT URL and customise the body to pass value1, value2, value3:
{"value1": "{level}: {message}", "value2": "{program}", "value3": "{logspace}"}
WhatsApp example

IFTTT's WhatsApp action uses value1 as the message body. The payload above sends the level and message text directly to your WhatsApp number.

SMS example

Use the IFTTT Android SMS or iOS Notifications action with value1 as the notification text.

Available placeholders
PlaceholderValue
{level}Log level (e.g. ERROR)
{message}Log message text
{program}Program / source name
{timestamp}ISO 8601 timestamp of the log entry
{logspace}Name of the logspace
{uuid}UUID of the logspace
Notes
  • The payload is sent as HTTP POST with Content-Type: application/json.
  • Any 2xx response from IFTTT is treated as success. Non-2xx responses are logged as failures in the Alert Log.
  • IFTTT applets are not real-time — there is typically a polling delay of a few minutes on free plans.