GitHub webhooks should point to the running Conductor instance or the standalone webhook listener.
Recommended flow
- Get local task dispatch working first.
- Set
WEBHOOK_SECRET.
- Expose the listener through a controlled public endpoint.
- Point GitHub to
POST /api/webhook/github.
What the webhook is for
- issue or PR driven automations
- repo event ingestion
- board updates driven from GitHub state changes
Important constraint
If you expose Conductor remotely, secure the network path first. Local-first only stays simple if the public surface remains small and intentional. Last modified on March 6, 2026
