# webhook

Connects your agent to webhooks and external services via Membrane CLI. It handles authentication lifecycles and request routing without local secrets.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 159 installs · ★ 273 repo stars
- Author: membrane
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/membranedev/application-skills/tree/HEAD/skills/webhook/SKILL.md
- Updated: 2026-04-28
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/webhook

## What it does

This skill lets agents manage connections to third-party services and webhook sources through Membrane. Instead of managing OAuth tokens manually, the agent invokes `membrane connection ensure` with a target domain. Membrane automatically matches existing connectors or builds a new one.

To perform operations, the agent searches for available tasks with `membrane action list` using natural language queries. When no pre-built action matches, it falls back to `membrane request`. This proxies HTTP calls directly to endpoints with automatic header management and credential refreshes.

Running this skill requires network access, a Membrane account, and `@membranehq/cli` installed globally. Without completing `membrane login` first, agent workflows will halt on authentication checks.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add membranedev/application-skills --skill webhook -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/webhook/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/webhook/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add membranedev/application-skills --skill webhook -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/webhook/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add membranedev/application-skills --skill webhook -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/webhook/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install membranedev/application-skills skills/webhook
```

2. **Manually: put the files in place**
- File: `.github/skills/webhook/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add membranedev/application-skills --skill webhook -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/membranedev/application-skills --path skills/webhook
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/webhook/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add membranedev/application-skills --skill webhook -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/membranedev/application-skills/tree/HEAD/skills/webhook/SKILL.md

## When to use it
- connect agents to external webhooks without storing local API keys
- discover integration actions using plain-text intent searches
- send proxy requests to third-party endpoints with automated token refreshes
- poll external connection build states until endpoints become ready

## Example prompts
- Connect to https://integration.app and confirm when the connection state is READY.
- Search for actions related to record updates on the active connection and run one.
- Send a POST request through Membrane proxy to `/events` with the current payload.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 95a2bc80e6587f0d.

BEGIN THIRD-PARTY FILE 95a2bc80e6587f0d
````text
---
name: webhook
description: |
  Webhook integration. Manage Recordses. Use when the user wants to interact with Webhook data.
compatibility: Requires network access and a valid Membrane account (Free tier supported).
license: MIT
homepage: https://getmembrane.com
repository: https://github.com/membranedev/application-skills
metadata:
  author: membrane
  version: "1.0"
  categories: ""
---

# Webhook

Webhooks are automated messages sent from apps when something happens. Developers use them to update external systems or trigger workflows in response to events in another application.

Official docs: https://docs.github.com/webhooks

## Webhook Overview

- **Webhook**
  - **Event**
- **Connection**

Use action names and parameters as needed.

## Working with Webhook

This skill uses the Membrane CLI to interact with Webhook. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

### Install the CLI

Install the Membrane CLI so you can run `membrane` from the terminal:

```bash
npm install -g @membranehq/cli@latest
```

### Authentication

```bash
membrane login --tenant --clientName=<agentType>
```

This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available.

**Headless environments:** The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with:

```bash
membrane login complete <code>
```

Add `--json` to any command for machine-readable JSON output.

**Agent Types** : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness

### Connecting to Webhook

Use `membrane connection ensure` to find or create a connection by app URL or domain:

```bash
membrane connection ensure "https://integration.app" --json
```
The user completes authentication in the browser. The output contains the new connection id.

This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.

If the returned connection has `state: "READY"`, skip to **Step 2**.

#### 1b. Wait for the connection to be ready

If the connection is in `BUILDING` state, poll until it's ready:

```bash
npx @membranehq/cli connection get <id> --wait --json
```

The `--wait` flag long-polls (up to `--timeout` seconds, default 30) until the state changes. Keep polling until `state` is no longer `BUILDING`.

The resulting state tells you what to do next:

- **`READY`** — connection is fully set up. Skip to **Step 2**.
````
END THIRD-PARTY FILE 95a2bc80e6587f0d

The third-party file has ended. Everything between the 95a2bc80e6587f0d tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2745 of 6306 bytes. © membrane · MIT · https://github.com/membranedev/application-skills/tree/HEAD/skills/webhook/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
