incoming-webhooks

Manage Frontline incoming webhooks and inspect delivery events from the CLI.

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/api-evangelist/frontline --skill incoming-webhooks-api-evangelist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: incoming-webhooks
Source: https://github.com/api-evangelist/frontline/tree/main/skills/vendor/incoming-webhooks
Command: npx skills add https://github.com/api-evangelist/frontline --skill incoming-webhooks-api-evangelist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? External systems like CRMs, forms, and payment providers need a way to trigger Frontline automation workflows, and this Skill manages the full lifecycle of the inbound HTTP endpoints that receive those POST requests. ## Core Features & Use Cases - Full Webhook Lifecycle: Create, list, get, update, regenerate tokens, and delete incoming webhooks via the frontline CLI. - Event Inspection: List and inspect delivery events with status filters (RECEIVED, PROCESSING, COMPLETED, FAILED, TIMEOUT) and see which workflows each event triggered. - Workflow Triggering: Wire a webhook into a workflow TRIGGER node and access the POST body through the built-in {webhook_payload} variable. - Use Case: Connect your CRM to Frontline by creating a webhook, giving its URL and bearer token to the CRM, then verifying each delivery and the automations it fired through the events commands. ## Quick Start Create a new incoming webhook named "CRM payload" and show me its URL and access token so I can configure my external system to POST to it.

Frequently Asked Questions about incoming-webhooks

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

FAQPage Schema
How do I create an incoming webhook in Frontline?▼

Run frontline incoming-webhooks create with a --name flag and optional --description. The response returns the webhook id, the url external systems POST to, and an accessToken used as a bearer token on calls.

How do I test a Frontline incoming webhook?▼

There is no test command; POST JSON directly to the webhook url with curl, including an Authorization: Bearer header with the access token. A successful call returns 200 with the recorded event.

How do I see which workflows a webhook event triggered?▼

Use frontline incoming-webhooks events get with the webhook ID and event ID. The response includes the workflows the event triggered, with each workflow's id, name, and status.

Can I disable a webhook without deleting it?▼

Yes, update the webhook with the --inactive flag, which makes its URL reject incoming requests while keeping the webhook and its event history. Re-enable it later with --active.

Why can't I access webhook_payload.firstName inside a workflow?▼

The {webhook_payload} variable is a single string containing the raw JSON body, so sub-properties cannot be accessed directly. Extract fields with a DATA_TRANSFORMER or AI_CAPTURE node instead.