logo
Schedulin

Using Nostr with Schedulin

Schedulin signs your notes with your Nostr key and publishes them to your relays at the scheduled time. There's no app to authorize: you connect by pasting your secret key.

Connecting Nostr

  1. Copy your secret key from your Nostr client. It starts with nsec1…; a 64-character hex key works too. In most clients it's under Settings → Keys or Backup.
  2. On Schedulin's Channels page, start the Nostr connection.
  3. Paste the key into Secret key.
  4. Relays (optional): leave blank to use the defaults, or enter your own as a comma-separated list, e.g. wss://relay.damus.io, wss://nos.lol.
  5. Save. The account appears under its public key (npub1…).

Don't have a key yet?

A Nostr account is just a key pair; there's no sign-up. Apps like Damus (iOS), Amethyst (Android), and Primal generate one for you. Copy the nsec from the app's key settings and paste it into Schedulin.

Keeping your key safe

Your secret key is encrypted at rest and only used to sign the notes you schedule. Keep in mind:

  • Nostr keys can't be revoked. Anyone with your nsec can post as you, forever. Only paste your key into apps you trust.
  • If you'd rather not use your main key, create a separate key for the account you schedule from (for example, a brand account).
  • Remote signers (NIP-46 / "bunker" login) aren't supported yet.

Relays

If you leave the relays field blank, Schedulin publishes to:

  • wss://relay.damus.io
  • wss://nos.lol
  • wss://relay.nostr.band
  • wss://relay.snort.social

A note counts as published as soon as at least one relay accepts it. To change your relays, disconnect the account and reconnect with a new list.

What you can publish

Post typeMediaNotes
Text note—A standard kind:1 note
Note with imagesImagesEach image is added as a link at the end of the note; clients show it inline

Nostr has no hard character limit, but keep notes reasonably short: some relays reject very large events, and many clients collapse long notes.

After publishing

Each published note links to njump.me/note1…, a public web view of the note. The note also appears in any Nostr client that reads one of your relays.

Analytics

Nostr has no central metrics service, so engagement analytics (likes, reposts, zaps) aren't available for Nostr notes. We still record the note and its link.

Troubleshooting

  • "That doesn't look like a valid Nostr secret key": paste the full nsec1… value (not your npub), or a 64-character hex key, with no extra spaces or labels.
  • "No relay accepted the event": none of your relays accepted the note. Some relays are paid or only accept whitelisted users. Reconnect with relays you know accept your posts, such as the defaults above.
  • Note doesn't show in my client: your client may read from different relays. Add one of your client's relays to your Schedulin relay list.

Known limitations

  • Text notes with images only. Replies, reposts, long-form articles (kind:30023), and zaps aren't supported yet.
  • No post-level analytics.
  • The account shows under its npub, not your profile name or picture.
  • Connecting requires your secret key (no NIP-46 remote signing yet).