Connect X, notifications and Telegram

Push notifications on your devices#

OwnPost can send reminders and assistant updates as standard web push notifications, with no extra secrets or provider account. Open Settings → Notifications on each device and choose Turn on for this device. The workspace creates its own notification keys on first use.

On a Mac, notifications work in a Safari tab, or use Safari's File → Add to Dock for an OwnPost app with its own Dock badge. On iPhone and iPad (iOS 16.4 or later), open OwnPost in Safari, choose Share → Add to Home Screen, then turn notifications on from the Home Screen app. Chrome, Edge and Firefox work the same way.

Push and Telegram can run together. Quiet hours and the daily limit apply to both. A push notification opens the related draft or task; Telegram keeps its Snooze, Skip and Mark done buttons.

Personal reminders with Telegram#

Telegram is optional. Create your own bot, configure its token and webhook secret, and connect the owner’s private chat using the kit’s connection instructions.

Enable Telegram for a routine when you want a reminder in that chat. Its Mark done button completes the same pending item shown on Home. Completing it in either place records one completion.

Quiet hours and notification limits control reminder delivery. Routine items remain available in the workspace when Telegram is disconnected or reminders are muted; Home shows up to five unanswered items from today that are overdue or due within ten minutes. Push notifications follow the same quiet hours and limits.

Optional X API publishing#

Manual copy-and-publish works without X developer credentials. For API publishing, bring an eligible X app and your own API access. Set its callback URL to your application’s /api/x/callback route.

Configure X_CREDENTIAL_KEY as a base64-encoded 32-byte value, then connect and test from Settings. Publication workflows start disabled and require explicit approval and the appropriate access grants.

Switch to the intended account profile before connecting X. For original posts and threads, approve the exact saved content and connected destination, then choose Publish now or a future API time. A manual reminder or a new MCP key does not authorize publication.

node -e "console.log(require('node:crypto').randomBytes(32).toString('base64'))"

Keep X API usage predictable#

OwnPost uses X API v2 for approved publishing and optional metrics sync. It does not require an X Activity event subscription. Telegram's webhook is separate. Drafting and viewing saved results do not call X.

Insights starts with 25 recent posts. Choose 100 or opt into up to 100 older linked posts when needed. Identical complete syncs reuse results for five minutes with the original measurement timestamp.

As of 23 September 2026, 1,000 standard posts cost $15; URL posts $200; ordinary post reads $5. Qualifying owned reads cost $1 per 1,000 when the authenticated user owns the developer app. Verify current prices in X before budgeting.

A thread makes a publishing request for each part.

1. 1

   Buy X credits and set a billing-cycle spending cap in your developer console. OwnPost does not manage that balance or enforce a dollar budget.

2. 2

   Enable only needed automation features, start with the smaller Insights sync.

3. 3

   If X returns 402, review credits and spending limits. On 429, allow the rate-limit reset. Check X before retrying an uncertain publication.

Going on vacation? Keep your presence going.#

Prepare your posts before you leave, then let your hosted workspace deliver the versions you have approved. This uses the existing publication and assistant controls; there is no separate global vacation switch.

1. 1

   Finish the initial deployment and owner setup. Check your host's scheduler: Cloudflare uses its scheduled Worker, VPS Compose includes a scheduler, and Vercel or Netlify needs an external authenticated call every minute. Keep that hosting and scheduling available while you are away.

2. 2

   Switch to the intended X account profile, connect your eligible X API account, and test the connection. Enable API publication and check the relevant permissions and automation controls.

3. 3

   Prepare and save your posts or threads. Review the exact text, media, and destination account, approve API publication, and choose explicit future delivery times. A calendar plan or manual reminder alone does not send a post. Your hosted scheduler can deliver these approved originals without an AI client staying online.

4. 4

   For AI preparation while you are away, configure a schedule in your external client and keep its runner available. Local scheduling needs the relevant computer and client available; hosted client execution needs its own working setup. Saving a routine in OwnPost does not start the client.

5. 5

   Check a scheduled delivery and any assistant workflow before you leave. Set optional Telegram notifications, quiet hours, and limits to suit your trip. Review delivery that needs attention; check X before retrying an uncertain result. On your return, review the published posts and record their results.

One routine flow, from reminder to done#

Open Assistant → Routines, or choose Daily challenge from Today's routines on Home. Use Add routine for recurring work such as reviewing results, writing, or organizing ideas. Enter a name, instructions, schedule, and timezone, and choose optional Telegram reminders. Every routine uses the same form and saved-routines table.

The configured scheduler creates routine items. Home → Today's routines shows up to five unanswered items scheduled for today in your workspace timezone: overdue items from today and items due within the next ten minutes. Choose View all to open the full routine list, including pending items from earlier dates. Mark done from Home or Telegram completes the same item; completed and skipped items remain in routine history.

Routine analytics count pending, completed, and skipped due items. Completion rate is completed items divided by all due items, including pending and skipped items. The last-seven-days view groups items by their scheduled date in the workspace timezone.

Cloudflare uses a scheduled Worker; Node deployments use authenticated cron calls. If you want scheduled AI preparation, configure a schedule in your compatible client separately and keep that client available.