Publishing and CMS

BaseHub integration

BaseHub keeps content in a repo with branches and instant previews. The BaseHub integration writes into that structure, so content produced in WriteWorks moves through the same review flow as everything else.

What it is

What the BaseHub integration is

The BaseHub connection uses a token you create and writes into the repo and collection you nominate, following the block structure your project defines.

Because BaseHub content is versioned like code, work can land on a branch, be previewed, and be merged when it is right. The integration fits that model rather than pushing straight to what is live.

Repos and branches
Blocks and collections
Field mappings
Draft and committed content
What it does

What you can do with it

Four questions the two data sets answer together that neither answers alone.

Content can go to a branch and be previewed before anyone merges it, which is the whole reason to run a versioned CMS.

How it works

How the BaseHub integration works

About a minute to connect, and nothing to maintain afterwards.

1

Create a BaseHub token

In BaseHub, create a token with write access to the repo you want WriteWorks to publish into.

2

Connect it in WriteWorks

Open Settings, then Integrations, and choose BaseHub. Add the token and pick the repo.

3

Map the collection

Choose the collection and map the draft's parts onto the block fields it expects.

4

Review, merge, track

Content lands for review, is merged when approved, and the live URL is tracked from then on.

Who it is for

Who uses the BaseHub integration

The same connection answers a different question depending on who is asking.

Content that arrives as a reviewable change rather than a surprise in production.

You bring your own account. The BaseHub integration authenticates with your own account at BaseHub, on your own plan and your own quota. WriteWorks reads the data that account already has access to, and nothing else. Disconnect at any time and the stored credential is deleted.

Related

Works well alongside

FAQ

BaseHub integration FAQs

The questions teams ask before connecting it.

What does the BaseHub integration do?+
It writes content from WriteWorks into your BaseHub repo, mapped onto the blocks and collections your project defines, and tracks the published URL afterwards.
Do I need my own BaseHub account?+
Yes. The integration uses a token you create for a repo you already own.
Can content go to a branch instead of production?+
Yes, which is usually the point of using BaseHub. Content can be previewed on a branch and merged when approved.
How do I connect BaseHub to WriteWorks?+
Create a token in BaseHub, then open Settings, Integrations, choose BaseHub, add the token, pick the repo and map the collection.
What if my blocks are unusual?+
Fields are mapped explicitly, so any block structure can be targeted without a workaround.
What happens if I disconnect it?+
The stored token is deleted and WriteWorks stops writing. Content already committed is untouched.

Connect BaseHub and see the whole picture

Measure how 10+ AI platforms answer your buyers, join it to the paid and organic data you already have, and ship the content that flips the citation.

BaseHub Integration | WriteWorks