Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.mistle.dev/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Some integrations require the control plane to receive browser callbacks or provider webhooks. Operators own the platform requirement behind those flows:
  • the control plane must have a stable externally reachable base URL
  • that base URL must be the one used when configuring provider apps or webhook registrations
In TOML, this is services.control_plane_api.public_url.

​
Current Callback And Webhook Shapes

Mistle currently uses these callback and webhook URL patterns:
PurposeURL shape
GitHub App installation callbackhttps://<control-plane-base-url>/p/integration/callbacks/setup/github-app-installation
Source-keyed integration webhook endpointhttps://<control-plane-base-url>/p/integration/webhooks/<target-key>/<endpoint-key>

​
Integrations That Depend On This

These integrations currently depend on callback or webhook reachability:
  • GitHub App installation
  • Slack webhook sources
  • Jira managed webhook sources
Provider-specific setup details still belong in each connection guide. This page only defines the operator-owned platform requirement: the base URL must be reachable from the provider.

​
Running Locally

When you test a self-hosted setup locally, provider callback and webhook delivery still require a public URL that can reach your control plane. In this repository’s Docker Compose workflow, ./up.sh starts a Cloudflare quick tunnel when needed. Use that printed public control-plane URL when configuring provider apps and webhook registrations.