LaunchKit · 2026
Back to Skills

Send and close SIGNL4 alerts using the SIGNL4 inbound webhook (team secret in URL).

0
736 downloads
by @rons4

Setup & Installation

openclaw skills install @rons4/signl4

Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:

npx clawhub install signl4

What This Skill Does

Sends and resolves alerts to a SIGNL4 team via the inbound webhook. Authentication uses a team secret embedded in the webhook URL. Alerts can be correlated and closed later using an external ID.

A single team secret in the webhook URL is all that's needed — no SDK, OAuth flow, or persistent connection required.

When to use it

  • Alert on-call engineers when a production service goes down
  • Resolve an open incident without logging into the SIGNL4 app
  • Route alerts to a specific service group during an outage
  • Trigger emergency escalation with a multi-acknowledgment scenario
  • Send location-tagged field alerts to a mobile response team

Example Workflow

Here's how your AI assistant might use this skill in practice.

INPUT

User asks: Alert the on-call team that the payment service is down, with external ID inc-2024-001

AGENT
  1. 1Constructs the webhook URL using SIGNL4_TEAM_SECRET
  2. 2Builds the JSON payload with title, message, external ID, and X-S4-Status set to 'new'
  3. 3Sends a POST request to the webhook via curl
  4. 4Confirms the alert was sent and reports the title and external ID back to the user
OUTPUT

Alert sent to SIGNL4 team: 'Payment Service Down', External ID: inc-2024-001

Requirements

Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.

SIGNL4_TEAM_SECRET environment variableSIGNL4 account