WorkMA Webhooks, CI Gates & Automation
Wire automated testing runners, deployment pipelines, and team alert feeds directly into WorkMA using cryptographically verified per-tenant webhook tokens.
HMAC-Verified Tenant Webhooks
Every CodeProject verifies external webhook payloads using isolated workspace webhook secret keys.
CI Status Enforcement on Merges
Update merge request CI pass/fail status cleanly from GitHub Actions, GitLab runners, or custom scripts.
REST & Workspace API Endpoints
Manage tasks, team notifications, code runner execution, and DLP telemetry cleanly via documented endpoints.
How Setup Works Inside Your Tenant
- Copy your project's signed webhook URL and secret inside Code Nexus project settings.
- Add a single curl/POST step inside your CI workflow emitting `pending`, `passed`, or `failed`.
- Enable `require_ci_pass` so broken builds cannot merge to production branches.
Integration FAQ
Are webhooks isolated per workspace tenant?
Yes. Webhook signing secrets derive deterministically per tenant key, ensuring cross-tenant isolation.
Can any CI provider post build status back to WorkMA?
Yes—GitHub Actions, CircleCI, Jenkins, or custom shell pipelines can notify WorkMA merge requests over HTTPS.