The ClickHelp project backups nobody wants to work through
ClickHelp exposes 3 operations and a companion can work all of them: create a topic, create a publication and create a project backup. Anything that changes a record waits for your click.
Open the project backup. Check it against something else. Write the change. Move to the next one. That is the ClickHelp afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a project backup until you approve it.
What it can do is exactly what ClickHelp exposes to an account you authorise and nothing beyond it: 3 operations, no reads and 3 writes. In practice that means it can create a topic, create a publication and create a project backup, and work across the project backups, publications and topics.
The ClickHelp API stops at ClickHelp. 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 project backups or ask you for them?
In the tab.
ClickHelp exposes no read operation to a connected account, so a companion opens ClickHelp in the session you are already signed into and reads the screens you would.
The project backups are what most of this inventory is about, alongside the publications. A companion can hold all 3 of these operations and forty open tabs in the same pass, which is how an afternoon of ClickHelp admin becomes a queue you review.
What happens before it can create topic?
All 3 write operations wait for you.
A companion can create a topic, create a publication and create a project backup, and each one is staged on an approval card first: you see the project backup, the field and the new value before it lands in ClickHelp.
Nothing in ClickHelp is sent, changed or deleted on your behalf without that click, and a rejected card leaves the project backup exactly as it was. The gate is the same one on every surface, described at security.
- Create Topic
- Create Publication
- Create Project Backup
Does the project backup sweep have to be asked for every time?
Yes.
Saved as a routine, the ClickHelp project backups 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 ticket queue, the ClickHelp project backups 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