webhook

Send HTTP webhook calls to preconfigured connector endpoints with JSON payloads.

9|1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/flaz78/9Lives --skill webhook-flaz78
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webhook
Source: https://github.com/flaz78/9Lives/tree/main/workspace/skills/webhook
Command: npx skills add https://github.com/flaz78/9Lives --skill webhook-flaz78

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of manually wiring external API calls by letting you trigger HTTP webhooks that are already configured in 9Lives Connectors.

Core Features & Use Cases

  • Webhook invocation by ID: Call only webhook endpoints that exist in the current Live’s allowed set, using the connector-provided URL and credentials.
  • Controlled payload handling: Optionally provide a body payload; if omitted, the webhook’s bodyTemplate can be used (with JSON merge semantics when both are objects).
  • Header and API-key safety: Automatically injects the connector API key into the x-api-key header while allowing additional optional headers.

Quick Start

Use the webhook skill to call a preconfigured webhook with ID "customer_sync_01" and send a JSON payload that contains the customerId and action fields.

Frequently Asked Questions about webhook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I send HTTP requests to external APIs using preconfigured webhooks?

To send HTTP requests to external APIs using preconfigured webhooks, select an existing webhook ID and optionally provide a JSON payload. The skill automatically applies the connector URL, API key, and body template.

How does webhook payload merging work when sending data to external systems?

Webhook payload merging works by combining your provided JSON body with the connector's bodyTemplate. If both are objects, JSON merge semantics apply; if omitted, the template is used alone.

Can I use custom HTTP headers and API keys for webhook automation?

You can use custom HTTP headers for webhook automation, but the API key is automatically injected into the x-api-key header. This ensures secure credential handling while allowing additional optional headers.

Do I need an existing connector setup to trigger webhook automation?

You need an existing connector setup to trigger webhook automation. The skill requires selecting a webhook ID from the current Live's allowed set and uses the connector-provided URL and credentials.

What is the best way to automate notifications and data syncing via HTTP webhooks?

The best way to automate notifications and data syncing via HTTP webhooks is to invoke preconfigured connector endpoints by ID. This removes manual API wiring and handles payload templates automatically.

What are the limitations of calling preconfigured webhook endpoints?

Limitations of calling preconfigured webhook endpoints include being restricted to only webhook IDs existing in the current Live's allowed set, and dependency on connector-provided URLs and credentials for execution.