skills.rest
friday-platform
friday-platformOFFICIAL
Explore all skills by this author →
Website𝕏@HelloFridayAIGitHub

wiring-external-webhooks

Route external service webhooks to Friday HTTP signals with full payload integrity.

97|5|Updated Apr 23, 2026
Search Tags:#github#webhooks#bitbucket#friday#http-signals#tunnel-url
One-click install
npx skills add https://github.com/friday-platform/friday-studio --skill wiring-external-webhooks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wiring-external-webhooks
Source: https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/wiring-external-webhooks
Command: npx skills add https://github.com/friday-platform/friday-studio --skill wiring-external-webhooks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves common pain points of incorrectly configuring external service webhooks to trigger Friday workspace workflows, including using inaccessible internal URLs, losing webhook payload data due to incorrect schema configuration, and misconfiguring tunnel routing that prevents webhook delivery.

Core Features & Use Cases

  • Correct Tunnel URL Guidance: Provides the exact public tunnel URL pattern for webhooks and instructions to retrieve the current live tunnel host, avoiding the common mistake of using internal atlasd routes that are not publicly accessible.
  • Payload Integrity Protection: Explains how to configure JSON schemas for HTTP signals to prevent silent stripping of webhook payload fields, ensuring agents receive full event data from upstream services.
  • Upstream UI Walkthroughs: Includes step-by-step configuration instructions for popular services including GitHub and Bitbucket Cloud to register webhooks with the correct URL and settings.
  • Error Troubleshooting: Covers common tunnel delivery errors and their fixes to quickly resolve webhook routing issues. Use Case: A development team wants GitHub pull request comment events to automatically trigger a Friday agent that drafts Linear tickets for code review feedback. This Skill ensures the GitHub webhook is correctly wired to the Friday HTTP signal with full payload data delivered to the agent.

Quick Start

Use the wiring-external-webhooks skill to connect your GitHub repository's issue event webhook to your Friday workspace's HTTP signal to automatically trigger agent actions for new issue reports.

Frequently Asked Questions about wiring-external-webhooks

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

FAQPage Schema
How do I connect external webhooks to Friday HTTP signals?▼

Routing GitHub webhooks to Friday requires registering the public tunnel URL in your repository settings and configuring the HTTP signal JSON schema to prevent payload field stripping during delivery.

Why does my GitHub webhook payload lose fields when delivered to Friday?▼

Webhook payloads lose fields when the HTTP signal JSON schema is not configured to accept the full event data. Configure the schema to match the incoming webhook structure to prevent silent stripping of payload fields by Friday.

Why are my external webhooks not reaching my Friday workspace?▼

Webhooks fail to reach Friday when using inaccessible internal atlasd routes instead of the public tunnel URL. You must retrieve the current live tunnel host and configure the upstream service to deliver to that public address.

Can I use Bitbucket Cloud webhooks to trigger Friday agent workflows?▼

Yes, Bitbucket Cloud webhooks can trigger Friday agent workflows. You must register the webhook in the Bitbucket UI using the correct public tunnel URL and configure the HTTP signal schema to receive the full payload.

What is the correct URL pattern for delivering webhook events to Friday?▼

The correct URL pattern for delivering webhook events to Friday is the public tunnel URL. Using internal atlasd routes prevents delivery, so you must retrieve the current live tunnel host to configure public webhook routing.

How do I troubleshoot tunnel delivery errors for external webhook events?▼

Troubleshooting tunnel delivery errors involves verifying the public tunnel URL is active, ensuring upstream services target the live tunnel host instead of internal routes, and checking the HTTP signal schema for payload field stripping.

Related Skills

Explore More Software Engineering Skills→
rafael-faerafael-fae
5

meta-webhook-receiver-setup

Set up a FastAPI Meta Cloud API webhook receiver with Nginx and Cloudflare Tunnel.

Community
Advanced
Greenmamba29Greenmamba29

webhook-orchestrator

Routes, transforms, and fans out webhook payloads to multiple services.

Community
Advanced
cpmappstudiocpmappstudio

clerk-webhooks

Listen for Clerk events and route them to downstream systems.

Official
Advanced
yspreenyspreen
33

convex-http-actions

Build HTTP endpoints for webhooks and custom routes in Convex applications.

Community
Advanced