The Confluence Data Center contents nobody wants to work through
Your Confluence Data Center, worked while you do something else: 3 reads to go through it, 3 writes to change it, and a card in front of every one of those changes.
Open the content. Check it against something else. Write the change. Move to the next one. That is the Confluence Data Center afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a content until you approve it.
What it can do is exactly what Confluence Data Center exposes to an account you authorise and nothing beyond it: 6 operations, 3 reads and 3 writes. In practice that means it can update a content, delete a content and create a content, and work across the contents and pages.
The Confluence Data Center API stops at Confluence Data Center. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Does it read the contents or ask you for them?
3 of the 6 operations are reads.
Your account, not a guess at it: a companion can search a content, get pages and get a page by ID, and the full list below is the whole list, with nothing inferred from Confluence Data Center's documentation.
The contents are what most of this inventory is about, alongside the pages. A companion can hold all 6 of these operations and forty open tabs in the same pass, which is how an afternoon of Confluence Data Center admin becomes a queue you review.
- Search Content
- Get Pages
- Get Page by ID
What happens before it can update content?
All 3 write operations wait for you.
A companion can update a content, delete a content and create a content, and each one is staged on an approval card first: you see the content, the field and the new value before it lands in Confluence Data Center.
Nothing in Confluence Data Center is sent, changed or deleted on your behalf without that click, and a rejected card leaves the content exactly as it was. The gate is the same one on every surface, described at security.
- Update Content
- Delete Content
- Create Content
Does the content sweep have to be asked for every time?
Yes.
Saved as a routine, the Confluence Data Center contents pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The operations playbook catalogues the other recurring shapes of the planning, the Confluence Data Center contents sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents