Point one project at a Todoist board, so CONTEXT reads the tasks on it. The board is named in the file, and its token is named in the environment.
Open the configuration page. If it is not open, run revetly config and
open the address it prints.
On the project's card, select Add source.
Choose Todoist.
Enter the board's name in Todoist project.
Enter the token in Key for the todoist connector. Leave the variable-name box above it alone.
Select Save.
You should see Access token: set on the card.
On the same line, read the board the card says it reads.
You should see Todoist: <BOARD> … on the card.
Select Test connection on the Todoist line. Revetly answers with what it reached, and puts any advice after it.
You should see api.todoist.com answers; … on the card.
In revetly.toml at the project root, add Todoist to what this project
reads:
# revetly.toml
[connectors]
enabled = ["pm", "docs", "conversations", "deliveries", "todoist"]
Revetly replaces this list rather than merging into it, so it restates every source already read.
In revetly.toml, name the board this project reads:
# revetly.toml
[connectors.todoist]
project = "<BOARD>"
Replace <BOARD> with the name of the board this project reads.
Read back which board Revetly will read:
revetly doctor --offline
[PASS] todoist: settings project = '<BOARD>'
[PASS] delivery criteria todoist declares no acceptance-criteria field …
Read which variable the token is read from:
revetly check
connector 'todoist': TODOIST_API_TOKEN is not set in the environment — …
In .env beside it, put the token that line named:
# .env
TODOIST_API_TOKEN=<TODOIST_TOKEN>
Replace <TODOIST_TOKEN> with a personal API token from Todoist.
Test the connection to Todoist:
revetly doctor
[PASS] todoist: reachable api.todoist.com answers; <COUNT> project(s) visible
[PASS] todoist: scope reads <COUNT> project(s): <BOARD>
TODOIST_API_TOKEN.