Linear
Actify owns the reasoning behind a roadmap item: the goal, the context, and the customer feedback that justifies it. Linear owns the delivery. The integration connects the two, so the case for a piece of work and its progress are not kept in two systems that disagree.
:::info Rolling out Connecting a workspace is available now. The project features below are being released in stages and are marked accordingly — this page describes the integration as a whole so you can see what approving it will eventually cover. :::
What it does
- Connect a Linear workspace and choose the team new projects will be created in. Available now.
- Link an existing Linear project to an Actify roadmap item, if the work is already underway. Coming soon.
- Create a Linear project from an Actify roadmap item, carrying its title, goal and target date across. Coming soon.
- Track delivery back. When the Linear project's state, target date, lead or progress changes, Actify updates to match. Coming soon.
Linking is optional, and always will be. A roadmap item can live entirely in Actify.
What Actify can access
Actify requests two scopes when you connect a workspace:
| Scope | What it grants |
|---|---|
read | Read access to the workspace. Always present — Linear includes it in every grant. |
write | Create and update projects in the team you choose. |
Actify does not request admin, issues:create or comments:create.
Nothing it does needs admin-level endpoints, and it creates projects, not
issues or comments.
Attribution
Actify connects as an application, not as the person who set it up
(actor=app in Linear's OAuth). Projects it creates are attributed to Actify
rather than to an individual — so the integration keeps working when that person
changes role or leaves.
What is not accessed
- Nothing from Linear becomes feedback in Actify. Issues, comments and project updates are never ingested into the feedback corpus.
- Actify reads projects it is linked to. It does not crawl the workspace.
Which direction wins
Applies once linking is available. Once a roadmap item is linked, the two systems own different fields:
| Field | Owned by |
|---|---|
| Title, goal, context, evidence, artifacts | Actify |
| Status, target date, progress, lead | Linear |
Actify writes the project when it is created and pushes later title and goal edits. It does not write delivery state back afterwards — the fields Linear owns become read-only in Actify, and the project's own page says so. A field that two systems can write is a field nobody trusts.
Connecting
- In Actify, go to Settings → Integrations → Linear.
- Press Connect Linear. You will be sent to Linear to approve Actify.
- Choose the default team new projects are created in. A Linear project has to belong to a team, so this is required before anything can be pushed. You can override it per project.
Connecting is restricted to an organization's owner or admin.
Disconnecting
Settings → Integrations → Linear → Disconnect.
Actify revokes its token with Linear immediately, so the grant disappears from your workspace's authorized applications too.
Projects created in Linear are left exactly as they are — Actify does not delete work. Links between Actify roadmap items and Linear projects will be kept rather than removed, so reconnecting later restores them instead of asking you to re-link everything.
Data stored
- The workspace's id, name and URL key
- The id and name of your chosen default team
- Once linking is available, for each linked project: its Linear id, URL, and the last state, progress, target date and lead Linear reported
Access and refresh tokens are stored encrypted in a secrets vault, readable only by the Actify service. They never appear in an API response or a log.
Questions about this integration: [email protected]