Accounts
An account is a signed-in connection to Linear, Jira, GitHub, Slack, Todoist or TickTick. Triggers don’t hold credentials themselves: each Linear, Jira, GitHub, Slack, Todoist or TickTick trigger picks an account, and uses it both to read issues and to write back comments and status changes. Integration steps and after-step actions pick an account the same way.
- You can add several accounts per platform: work and personal GitHub, two Jira sites, Linear workspaces for different teams.
- One account can feed any number of triggers. Rotating a token in Settings → Accounts & integrations updates every trigger that uses it.
- Credentials are stored encrypted with your OS keychain. See Data & security.
Schedule and webhook triggers don’t use accounts.
Signing in
Section titled “Signing in”- Open Settings → Accounts & integrations (⌘, then the Accounts & integrations tab). Each platform has its own section: click Sign in in it, or Add another account if you already have one there. With no accounts yet, the tab shows a Sign in to … tile per platform instead. You can also sign in from a trigger’s account menu (+ Sign in to a … account…), from the Sign in button next to it, or from the ⌘K palette (Sign in to Linear / Jira / GitHub / Slack / Todoist / TickTick), which opens the sign-in dialog on that tab.
- Enter the credentials. Each platform’s page explains how to create them: Linear, Jira, GitHub, Slack, Todoist, TickTick.
- Optionally set Account name, which is how the account is labelled in trigger editors. Leave it empty to name it after the signed-in user.
- Click Sign in.
Signing in verifies the credentials against the platform before saving. If the check fails, nothing is saved and you see Sign-in failed: <reason> (for example an HTTP 401 from the platform). On success, Jimothy records who the credentials belong to:
| Platform | Verification call | Recorded as |
|---|---|---|
| Linear | GraphQL viewer { id name email organization { name } } |
name, email, workspace = organization name |
| Jira | GET /rest/api/3/myself (Cloud) or /rest/api/2/myself (Data Center) |
display name, login, email, workspace = site host |
| GitHub | GET https://api.github.com/user |
name (or login), @login, email, workspace = github.com |
Default account names look like Linear · Acme (Ada Lovelace), Jira · acme.atlassian.net (Ada Lovelace) (Data Center shows the username) and GitHub · ada.
The Accounts & integrations tab
Section titled “The Accounts & integrations tab”Accounts are grouped by platform, each section headed by the platform, how many accounts it has, and Sign in / Add another account. Each account card shows:
- the account name and a signed in badge (or not verified), and for Slack whether the app is listening;
- who it’s signed in as, e.g.
Ada Lovelace (@ada) · ada@acme.com · Acme, and when it was last verified; - which triggers use it and the pipeline each one runs (paused triggers are marked), or Not used by any trigger yet · Assign to a pipeline, which opens a new trigger for that account;
- Edit / re-sign in (pencil) and Remove account (trash).
Rotating a token
Section titled “Rotating a token”Open the account with the pencil, paste the new token or key, and click Save & re-verify. The new credentials are verified before they replace the old ones, and every trigger using the account picks them up immediately.
An account can’t change platform once created.
Removing an account
Section titled “Removing an account”Remove account deletes the account and its stored credentials. You can’t remove an account that triggers still use; the error lists them:
Still used by "Linear: ENG", "Nightly Linear". Switch those triggers to another account first.The same goes for pipelines whose integration steps or after-step actions use it: Still used by steps in "Feature to PR". Switch those steps to another account first.
A Slack account used by a Slack app notification channel can’t be removed until you remove or change that channel.
Migration from older versions
Section titled “Migration from older versions”Earlier versions stored credentials on each trigger. On first launch after upgrading, Jimothy moves them into accounts automatically. Triggers that used identical credentials end up sharing one account, named Linear, GitHub or Jira · <host> (<email>) (with #2, #3 suffixes if names collide).