Documentation
Everything needed to run CogSend on your own Cloudflare account — the install, using the app day to day, the platforms, how publishing works, and the API.
Get started
- Install and deployOne command that creates the database, the bucket, the secrets and the account, then deploys the Worker — and how to update or roll back afterwards.Read
- ConfigurationThe secrets your instance reads, how to name it, how to keep your deployment separate from upstream and on the right Cloudflare account, and how to get back in when the login is lost.Read
Use it
- Writing and publishingThreads, per-platform overrides, images and alt text, and the difference between publishing now and scheduling.Read
- Posts and InsightsWhat every post can do from the list, how retries work, and the delivery stats that say what broke.Read
- Connecting accountsConnecting Mastodon, Bluesky, LinkedIn, Threads and X, reconnecting when a token expires, and what disconnecting keeps.Read
Connect and secure
- OAuth appsRegister the developer apps LinkedIn, Threads and X require, then check each platform’s limits on text, images and threads.Read
- Connect through ZernioConnect X, Threads, LinkedIn and Bluesky through Zernio’s approved apps instead of registering your own, and what differs.Read
- Cloudflare AccessPut an identity check in front of the whole instance, so even the login page is behind your own provider.Read
- Domains and URLsRename the workers.dev URL, move to a custom domain, and the three things to update when the hostname changes.Read
Publish and automate
Keep it running
Contribute
These pages are written in the app repo, so a change to the app and a change to its documentation happen in the same place. Something missing or wrong? Open an issue, and it will be fixed where it is written.
