State one credential and address for the whole instance. Every project that states none of its own reads the tool through that one.
Open the configuration page. If it is not open, run revetly config and
open the address it prints.
Turn on Advanced settings.
You should see Connections.
Go to Instance settings > Connections.
Select Add connection.
You should see Todoist among the tools offered.
Choose Todoist.
Enter the variable the token is read from in API token variable. Revetly reads the token from that variable rather than from the file.
Enter the token Todoist issued you in Key for the todoist connector.
Revetly writes it to the .env beside revetly.toml, never into the
committed file.
Select Save.
You should see token set on the connection line.
On the card of the project that reads through it, select Add source.
Choose the Todoist row marked the instance's connection.
You should see Test connection on the new source.
Select Save.
You should see the instance's connection on that source's line.
Select Test connection on that source's line. Revetly answers with what it reached, and puts any advice after it.
You should see api.todoist.com answers; … on that source.
In revetly.toml at the project root, state the connection once under
[connectors.todoist]:
# revetly.toml
[connectors.todoist]
token_env = "TODOIST_API_TOKEN"
In .env beside it, put the token that variable names:
# .env
TODOIST_API_TOKEN=<TODOIST_TOKEN>
Replace <TODOIST_TOKEN> with the token Todoist issued you.
In revetly.toml, add the source to the project that reads through it:
# revetly.toml
[projects.beta.connectors]
enabled = ["pm", "docs", "conversations", "deliveries", "todoist"]
Confirm whose connection that project runs on:
revetly doctor --offline --all
[PASS] beta: todoist: connection the instance's connection — …
Confirm the tool answers on that credential:
revetly doctor --all
You should see api.todoist.com answers; <COUNT> project(s) visible in the
terminal.