Todoist connector setup

This page is the setup half — creating the OAuth app Todoist needs in its own developer console and getting its client id and secret into this deployment. Authorising a connection afterwards is the Authenticate control on the plugin sheet, which is what actually sends you to Todoist.

1. Create the OAuth app in the Todoist developer console

1. Open the Todoist App Console and create a new app — this is your own app, not Botseon's.

2. Under OAuth redirect URL, paste the redirect URL from docs/connectors/README.md — with the quickstart's default BOTSEON_PUBLIC_URL, that is:

   http://127.0.0.1:3000/api/oauth/todoist/callback
   

3. Save. The console shows you a Client ID and a Client secret — copy both now.

2. Scopes

Request the narrowest pair that covers the tools this connector exposes (F-PLUG-1: minimum scopes per capability, read and write requested separately):

• data:read — list projects and tasks; no writes.
• data:read_write — everything data:read covers, plus creating and completing tasks.

3. Enter the app

One command, with the client secret on standard input — there is no flag that takes it and no environment variable that holds it (see docs/connectors/README.md):

printf %s "$CLIENT_SECRET" | botseon oauth-app set \
  --org <organisation id> --slug todoist \
  --client-id <the client ID from step 1> \
  --auth-url https://todoist.com/oauth/authorize \
  --token-url https://todoist.com/oauth/access_token \
  --configured-by <your user id>

It stores the secret encrypted and prints the redirect URL from step 1 back, so you can check the two match. botseon oauth-app show --org <organisation id> --slug todoist says whether an app is configured and under which client id; nothing prints the secret back.

Never put either value in a bot's description, a memory, or anywhere else a model reads as ordinary text.