Webhooks & external triggers
Connect a script or another system to deployment and job workflows through incoming webhooks, with execution visible in Openship.
Open the guideHow it works
Configure a hook for the supported action, such as redeploying a project or invoking a job. Use its required token or signature mechanism rather than exposing an unauthenticated command endpoint.
Repository webhooks also feed automatic deployments and Actions events. The triggered operation follows the normal authorization and execution pipeline, with its own status and logs.
What you can do
External automation
Connect scripts, another CI system, or event sources.
Authenticated hooks
Use the configured token or signature verification.
Visible outcomes
Follow triggered operations in run history.
Explore more
Ship it your way.
Self-hosted and free, or managed on Openship Cloud — the same workflow either way.