Sandbox integration check in CI/CD
Check the integration in CI/CD — with no real publications to the channels.
The problem
An integration with Crosslybot is code, and it can break: the payload format changed, the token expired, the signature drifted. Finding out about it from the absence of posts in production is a bad option.
How Crosslybot solves it
The /v1/sandbox/test endpoint accepts the same payload as the production webhook, validates it and returns a result — but publishes nothing. Put the call in CI/CD as a smoke test and catch breakage before release.
Crosslybot provides a /v1/sandbox/test endpoint for checking the integration in CI/CD. It accepts the same payload as the production webhook, validates it and returns a result — but publishes nothing to the channels.
Put the sandbox call in the pipeline as a smoke test: if the payload format changed, the token expired or the signature drifted, the step fails and stops the release. An integration break is caught before production, not from silence in the channels. The sandbox works on any plan, including Free.
How to set up
Take a test payload
Prepare JSON identical to what your integration sends to the production webhook.
Add a step to the pipeline
In CI/CD, add a step: a POST to /v1/sandbox/test with this payload and the endpoint token.
Check the response
The sandbox returns a validation result. A failed step = a broken integration, the release stops.
Deploy with confidence
A green smoke test means the payload, token and signature are fine.
What's inside
No real posts
The sandbox validates the payload and returns a result, but publishes nothing — the channels aren't cluttered with tests.
The same contract
The endpoint accepts a payload identical to production — the test checks exactly what will go to production.
Free even on Free
The sandbox check is available on any plan — the smoke test costs nothing.
Result
An integration break is caught in CI/CD before release, not from silence in the channels. Deploying the integration becomes predictable.
FAQ
Does the sandbox really publish nothing?
Yes. The endpoint only validates the payload and returns a result. Nothing goes to the channels.
How does the payload differ from production?
It doesn't. The sandbox accepts the same contract as the production webhook — so the test is reliable.
Is a separate token needed?
The token of the same webhook endpoint is used. No separate setup is needed.
On which plan is it available?
The sandbox check works on any plan, including Free.
Ready to try?
Connect the bot in 2 minutes. Free plan — no cards, no signup.
