Webhook Handoff

Organization

runxhq

webhook-handoff

Validate a runx execution context and deliver a governed payload once to an n8n Cloud workflow webhook or a Zapier Catch Hook, with exact approval and the receiver's acknowledgement receipted.

Overview

Publisher	runxhq
Repository	`runx`
Skill name	`webhook-handoff`
Stars	105
Forks	109
Bundled files	3
License	Apache-2.0
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
3 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by runxhq on GitHub. Read the source before you install it.

Installation

Install the Webhook Handoff AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/runxhq/runx/tree/main/skills/webhook-handoff
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/runxhq/runx.git /tmp/runx
mkdir -p .claude/skills
cp -r /tmp/runx/skills/webhook-handoff .claude/skills/webhook-handoff

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Webhook Handoff in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Webhook Handoff on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Webhook Handoff is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Webhook Handoff

Hand off governed runx work to a workflow platform without turning it into the authority holder.

This skill is the outbound side of a workflow integration. runx owns the policy decision, execution context, and receipt. The receiving platform owns its webhook, canvas, branching, fan-out, and downstream notifications. platform chooses the receiver and the connector that delivers to it: n8n for an n8n Cloud workflow, zapier for a Zapier Catch Hook.

Runners

preflight: validates and normalizes the handoff context without network.
send: validates the context and delivers it to the chosen receiver.

Use preflight for reviews, CI, and local harnesses; it never needs approval. The send runner first calls native control.prepare_handoff, which validates the execution identity and produces the canonical delivery envelope. It then runs handoff.deliver on the chosen connector, which posts that envelope after exact approval: for n8n to https://<workspace>.app.n8n.cloud/webhook/<slug>, for Zapier to the Catch Hook. Neither platform offers a way to read a delivery back, so the receipt records the receiver's answer with finality acknowledged, not a confirmed readback.

Execution context

execution_context must identify where the handoff came from. Include at least one of:

caller or caller_id
principal or principal_id
workflow or workflow_id
upstream_run_id

When present, these fields must match the top-level inputs:

platform
event_id
idempotency_key (bound to event_id)
handoff_scope
handoff_audience

The receiver gets the normalized delivery object, not an independently reassembled copy of these fields. That object carries the business payload, source context, exact handoff scope and audience, and idempotency binding the receiver must validate before starting its workflow.

Edge cases

Only n8n Cloud hosts are reachable for n8n. A self-hosted instance needs its own connector that declares its host.
Anyone who knows the webhook path can post to it, so have the receiving workflow check handoff_scope and handoff_audience before acting.
Do not put raw provider credentials into payload or execution_context. Pass credential references or let runx hold the provider secret.
If an n8n workflow slug changes, update handoff_audience to the matching n8n:workflow:<slug> value.
The receiver must dedupe by event_id before branching or sending downstream notifications.

Inputs

platform (required): n8n or zapier.
event_id (required): stable id for receiver-side dedupe.
execution_context (required): explicit caller/workflow context.
payload (required): business payload delivered to the receiver.
handoff_audience (optional): defaults to n8n:workflow:runx-governed-effect or zapier:zap:runx-governed-effect.
webhook_host (send runner, n8n only): the n8n Cloud host, such as acme.app.n8n.cloud. A Zapier handoff refuses one.

The webhook URL is the chosen connector's credential: n8n's webhook, bound with runx connector use n8n --credential webhook, which must be on webhook_host; Zapier's catch_hook, bound with runx connector use zapier --credential catch_hook. Either URL goes on stdin and never enters the run's inputs, records or receipts.

event_id is also the Runx mutation idempotency key and the value delivered as idempotency_key; there is no second retry identity that can drift from it.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Webhook Handoff AI skill do?

Validate a runx execution context and deliver a governed payload once to an n8n Cloud workflow webhook or a Zapier Catch Hook, with exact approval and the receiver's acknowledgement receipted.

Why use Webhook Handoff on TypingMind?

Because you install it once and use it with any model. Webhook Handoff is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Webhook Handoff in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/runxhq/runx/tree/main/skills/webhook-handoff. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Webhook Handoff?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Webhook Handoff?

As many as you like. As long as a model supports skills, you can use Webhook Handoff with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Webhook Handoff AI skill free?

Yes. It is published on GitHub by runxhq under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Grilling

mattpocock

CommunityPopular

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

Teach

Teach the user a new skill or concept, within this workspace.

Api Design

Patrones de diseño REST API incluyendo nomenclatura de recursos, códigos de estado, paginación, filtrado, respuestas de error, versionado y rate limiting para APIs de producción.

Accessibility

WCAG 2.2 レベル AA 標準を用いてインクルーシブなデジタルプロダクトを設計・実装・監査します。Web 用のセマンティック ARIA および Web・ネイティブプラットフォーム（iOS/Android）のアクセシビリティトレイトを生成するために使用します。

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Webhook Handoff

Runners

Execution context

Edge cases

Inputs

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now