Wix, Ghost & webhooks
What It Does
The Evidence Engine writes pages that have to live on your own site, and this is where you say where they go. Beyond WordPress there are three kinds of destination: a Wix blog, a Ghost blog, or a webhook — anything that can receive a post, which covers headless CMSs, Zapier and Make, and anything custom.
Connecting a Wix site
1. Open Connections → Publishing → Add destination, and choose Wix. 2. Address: your public site address, which is where we look for the published page. 3. Credential: your site ID and an API key, joined by a colon — site-id:api-key. • The site ID is the long id in your Wix dashboard address, straight after /dashboard/. • The API key comes from your Wix API Keys Manager, with the Manage Blog permission and access to this site. Only the account owner can create one. 4. Press Test. It publishes a short post you can delete, and hands back its address.
About the author
Wix will not store a post without an author, and an API key is not itself a site member — so we take the author from a post your blog already has. There is nothing to set up and no ID to look up. The one exception is a blog that has never had a single post: publish one from your Wix dashboard and every page after it is automatic.
Connecting Ghost or a webhook
Ghost — the address is your blog's base URL, and the credential is your Ghost Admin API key in its id:secret form. Webhook — the address is the endpoint we POST to, and the secret is optional. We send { title, html, excerpt, publishedAt, source } as JSON, with your secret in both the Authorization: Bearer and X-Webhook-Secret headers. Your endpoint must reply with the address of the page it created — {"url":"https://..."}. Without one we cannot submit the page for indexing, re-measure it, or show you what was built, so we record it as not published rather than claiming a page that might not exist.
Choosing where a project publishes
A project publishes to the destination you choose in its settings, and a campaign can override it. Left alone, we publish only to a connection on that project's own domain — never to whichever connection happens to be first on the account, because that is how one business's pages end up on another's blog. If nothing matches, pages are handed back as finished drafts rather than being sent somewhere they do not belong. There is also an explicit Off, if a campaign should never publish to your site at all.
Every destination row has Manage as well as Test, so a credential can be corrected in place. Leave the credential field blank to keep the one already stored — useful for Wix, which shows an API key only once.