GitHub runners and webhooks
Review captured self-hosted runners and outgoing webhooks without changing their GitHub configuration.
Open Workspace > Integrations, select the connected GitHub account, and choose Automation. You need workspace Admin or Owner access and the Platform feature.
Choose Self-hosted runners for the machines your organization provides to run GitHub jobs. Choose Egress webhooks for outgoing notifications sent by GitHub to another service. These panels show captured configuration and status; manage the resources on GitHub and sync the connection after changes.
Find self-hosted runners
- Choose Self-hosted runners and use Search self-hosted runners to find a runner.
- Set Runner status to Online, Offline, or All statuses.
- Use Sort runners to order by Runner name, Status, or Operating system, then select an ascending or descending Sort order.
- Review the runner's name, connection status, and operating system. Check other result pages when needed.
The status reflects the captured evidence and can differ from the machine's current connection. Choose Clear filters to clear the search and restore the default list and ordering.
Review outgoing webhooks
- Choose Egress webhooks and use Search egress webhooks to narrow the list.
- Choose Webhook scope to separate Organization webhooks from Repository webhooks.
- Use Webhook active state to show active or inactive webhooks, or leave all states visible.
- Use Sort egress webhooks to order by Target host, Scope, or Event count. Choose the order and review other result pages.
- Read the target host, scope, repository, event count, and state together. The event count describes the webhook's configured events.
Choose Clear filters to restore the default view. A captured Active state alone does not confirm that every notification reached its destination. To review notifications received by Sorena, use Activity > Deliveries.
If no rows match, clear the filters before checking the capture status. An empty confirmed capture differs from permission-limited or unavailable evidence. Use the retry action for a loading failure, or check GitHub access when the section reports missing permission.
Screenshots show a demo workspace.