Payload integration
Payload runs on your infrastructure, with your collections and your access rules. The Payload integration works with that instance directly, creating and updating documents through the API you already expose.
What the Payload integration is
The Payload connection points at your instance and authenticates as a user or API key you create, which means WriteWorks inherits exactly the access rules you already enforce rather than sitting outside them.
Content is written into the collection you nominate with an explicit field mapping. Because Payload is code-first, this keeps the CMS authoritative: the schema lives in your repository, and WriteWorks writes to it.
What you can do with it
Four questions the two data sets answer together that neither answers alone.
Self-hosted or cloud, the integration talks to the Payload instance you point it at, using credentials you control.
WriteWorks authenticates as a user or key you create, so your existing collection-level access control applies unchanged.
Choose the collection and map the fields once; every publish follows that shape.
Existing documents can be improved in place, which keeps the URL and avoids two pages competing for the same answer.
How the Payload integration works
About a minute to connect, and nothing to maintain afterwards.
Create credentials in Payload
Add an API key or a dedicated user with access to the collections WriteWorks should write to.
Connect the instance
Open Settings, then Integrations, and choose Payload. Enter your instance URL and the credentials, which are stored encrypted.
Map the collection
Pick the collection and map the draft's title, body, slug and summary onto its fields.
Publish and track
Approved drafts are written to Payload, and published URLs are tracked for citations and search performance.
Who uses the Payload integration
The same connection answers a different question depending on who is asking.
A CMS that stays code-first, with content arriving through the same API and rules as everything else.
Self-hosted content, scoped credentials, and no third party holding the CMS.
Ship into the real CMS without waiting for a developer to paste anything.
One instance and one key per client, kept apart by brand.
You bring your own account. The Payload integration authenticates with your own account at Payload, 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.
Works well alongside
Payload integration FAQs
The questions teams ask before connecting it.
What does the Payload integration do?+
Does it work with a self-hosted instance?+
What access does it need?+
How do I connect Payload to WriteWorks?+
Can it publish directly?+
What happens if I disconnect it?+
Connect Payload 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.