Skip to main content
Every destination type gives you a way to prove the pipeline works before real content flows through it. Use these tools in order of increasing realism.

​
Use draft statuses

Set the connection’s Default status to Draft while you test, so the editor’s button reads Send draft to CMS. A draft send exercises the whole pipeline (generation, sending, the CMS’s response, and reading the item back where supported) without making anything public. A new draft stays Draft in Weelkit until it is published in your CMS, then becomes Published on its own. Sanity keeps Published when an existing live version remains beside a newer draft. Switch the default to Published only after you have verified a draft end to end.

​
Use the webhook test event

For API webhook destinations, choose Send test on the endpoint. Weelkit delivers a webhook.test event to your URL with the same headers and signature scheme as a real delivery, but with article set to null. Use it to verify, in this order:
1

Transport

Your endpoint receives the request over HTTPS and responds with a 2xx status.
2

Signature verification

Your signature verification accepts the test event. If it rejects a genuine test event, fix verification before going further.
3

Null handling

Your handler tolerates article: null without crashing. Real article.version.created events carry a full article object.

​
Use a staging site

For CMS destinations (WordPress, WordPress.com, Sanity, Ghost or a Custom API), connect a staging site first. Run the full flow there: mapping review, Verify test draft, and a real send from the editor. After all test sends and cleanup are settled, disconnect the staging connection. Connect production separately, save its mapping and verify its test draft. Only one CMS connection is active; a different destination does not inherit staging verification.

​
Verify a test draft

The last step of CMS setup is Verify test draft: Weelkit uses your saved mapping to publish a draft and read it back, and shows the result for each field. It proves Weelkit can sign in, write and read back before the connection is ready. The draft stays in your CMS so you can inspect it; choose Delete draft to remove it. Changing the mapping or the publishing defaults means verifying again.

​
Boundaries to respect

Never point a Custom API base URL at internal or private hosts. Private, loopback, link-local, and cloud-metadata addresses are rejected at connect time — Weelkit will not dispatch to them, in test or in production. Use a publicly reachable staging host instead.
Secrets are shown once. Webhook signing secrets and similar credentials are displayed a single time at creation. Store them in your secret manager immediately — if you lose one, rotate it to get a new value.