Integrations · Linear
At-risk accounts become work in Linear, synced both ways.
An alert tells you an account is at risk. Someone still has to do something about it. Keep opens an issue for each at-risk account and, with Linear connected, that issue lives in Linear too — edited from either side.
What happens when an account becomes at risk
Keep opens an issue titled with the account and the MRR at stake. The description carries the reason, the last time anyone was seen, the renewal date, the contact, the steps of the playbook that just started, and a link back to the account in Keep. Priority follows the risk: an account that pays and renews within 7 days is urgent.
If the account is still at risk later, or gets worse, Keep adds a comment to the same issue instead of opening another one.
When the account comes back
When the account leaves risk while still paying, Keep counts it as recovered. An issue nobody started closes itself with a note saying why; one someone is working on stays open and gets the note, because that person may know something the numbers do not.
If the customer cancels instead, the issue is never closed as done — it gets a note, since the work did not go away, it failed. Closing an issue by hand is not counted as a recovery.
What syncs, and what Keep reads and writes
| — | Keep and Linear |
|---|---|
| Connection | OAuth with read and write scopes. Issues are created by the Keep app, not by whoever clicked connect. |
| Team | One Linear team per workspace, chosen after connecting and changeable later. |
| Syncs both ways | Title, description, status, priority, assignee, labels, due date, archive. Comments on linked issues. |
| Reads | The team's issues, workflow states, members, and labels, so the pickers in Keep match Linear. |
| Writes | Issues Keep opens or you edit in Keep, and comments. Nothing outside the chosen team. |
| Webhook | Changes made in Linear arrive by webhook, signed with HMAC-SHA256 and rejected outside a one-minute window. A daily pass catches anything a webhook missed. |
| Stores | Access and refresh tokens, encrypted with AES-256-GCM. |
How to connect
Authorize Linear
Approve Keep in Linear. There is no key to paste.
Pick a team
Issues from at-risk accounts go to that team, and its existing issues show up in Keep.
Work where you already work
Change status, assignee, or priority in Linear or in Keep; the other side follows.
Questions
- Which side wins when both change the same issue?
- Keep is the source of truth. A change made in Keep is saved first and then sent; a change from Linear is applied only if it is newer and Keep has nothing unsent. If Linear is down, the edit waits and goes out later.
- Do I need Linear to use issues and playbooks?
- No. Keep has its own issues and playbooks. Linear is for teams that want that work in the tool they already use.
- What happens to issues if I disconnect?
- Keep revokes its access in Linear and stops syncing. Issues already created stay in Linear.
- Which plan includes Linear?
- Every plan. All Keep features, including every integration, are in all plans; the difference between plans is monitored MRR.
Other integrations
Turn revenue at risk into work someone owns.
Connect your billing and Linear, and the next at-risk account arrives as an issue.