Connect Linear and Postmark
Start a client’s workflow in Linear and act in Postmark, or the other way round, on the client’s own accounts.
Each app by itself: Linear integration and Postmark integration, with how to connect it, its scopes and its limits.
What the pair is used for
- People outside Linear, such as the client’s product owner, can be emailed each issue opened in a team, with its title, description, identifier (ENG-123) and priority.
- A status move sends the same email within seconds, which tells the person who reported a bug that work on it has moved.
- For a software company whose product sends mail through Postmark, a bounce can open a Linear issue titled with the subject of the email that failed, so a broken send reaches the developers.
Every way Linear and Postmark join
A workflow starts from a trigger in one app and runs a step in the other, on the client’s accounts. Where the library has a starter for it, it installs that pairing into a client switched off; any other pairing is two steps on the canvas.
From Linear to Postmark
| When this happens in Linear | This runs in Postmark | How fast | Starter |
|---|---|---|---|
| An issue is opened | Send an email | Within seconds | Install the starter |
| An issue is opened | Send a template email | Within seconds | Two steps on the canvas |
| An issue changes status | Send an email | Within seconds | Install the starter |
| An issue changes status | Send a template email | Within seconds | Two steps on the canvas |
From Postmark to Linear
| When this happens in Postmark | This runs in Linear | How fast | Starter |
|---|---|---|---|
| An email bounces | Create an issue | Within seconds | Install the starter |
| An email bounces | Update an issue | Within seconds | Two steps on the canvas |
| A link in an email is clicked | Create an issue | Within seconds | Two steps on the canvas |
| A link in an email is clicked | Update an issue | Within seconds | Two steps on the canvas |
Set up the starter
Send an email in Postmark when an issue is opened in Linear
- 1Install the starter into the client from Templates → Library. It lands switched off.
- 2Connect the client’s Linear, for “An issue is opened”
- 3Connect the client’s Postmark, for “Send an email”
- 4Fill in Linear: Team ID (Webhooks can be made only with an admin’s API key)
- 5Fill in Postmark: From (For example Northside Plumbing <hello@northside.example>)
- 6Fill in Who it goes to (Postmark) (The address that gets it: yours, or the client’s team)
- 7Switch it on. Within seconds: Linear tells us as it happens.

What it produces
The Postmark step as it runs for an example client, Lakeview Consulting, when Emma Collins asks for a consultation: each value the starter fills in.
- From
- hello@lakeview.example
- Subject
- An issue is opened: Emma Collins
- Text
- An issue is opened in Linear. Title: Emma Collins Description: I’d like a consultation on Thursday at 10:30, with the $500 deposit. Identifier (ENG-123): example Priority (0 none to 4 low): 2 Status ID: new
- To
- emma.collins@example.com
Setup notes for this pair
- Linear gives the status as an ID and the priority as a number (0 none, then 1 urgent to 4 low), so the status-change email does not name the new status. Add the status name, or a line of your own, before it goes to anyone outside the team.
- The issue’s description goes out in full. The bounce issue’s title is the email’s subject only; put the bounced address in its description.
Field mapping, starter by starter
Each value a starter’s step is given, and where it comes from. Words in brackets are filled in when it runs; change any of it after installing.
Send an email for new issues
Send an email in Postmark when an issue is opened in Linear
| Postmark value | Filled from |
|---|---|
| From | [Postmark: From] |
| Subject | An issue is opened: [the issue’s title, from Linear] |
| Text | An issue is opened in Linear. Title: [the issue’s title, from Linear] Description: [the issue’s description, from Linear] Identifier (ENG-123): [the issue’s identifier, from Linear] Priority (0 none to 4 low): [the issue’s priority, from Linear] Status ID: [the issue’s state id, from Linear] |
| To | [Who it goes to (Postmark)] |
Send an email for issue status changes
Send an email in Postmark when an issue changes status in Linear
| Postmark value | Filled from |
|---|---|
| From | [Postmark: From] |
| Subject | An issue changes status: [the issue’s title, from Linear] |
| Text | An issue changes status in Linear. Title: [the issue’s title, from Linear] Description: [the issue’s description, from Linear] Identifier (ENG-123): [the issue’s identifier, from Linear] Priority (0 none to 4 low): [the issue’s priority, from Linear] Status ID: [the issue’s state id, from Linear] |
| To | [Who it goes to (Postmark)] |
Create an issue for bounced emails
Create an issue in Linear when an email bounces in Postmark
| Linear value | Filled from |
|---|---|
| Team ID | [Linear: Team ID] |
| Title | [the email’s subject, from Postmark] |
Linear and Postmark and their logos are trademarks of their owners, used here only to say what Thrum works with; no endorsement is implied.
Thrum is cooking.
Get early access and you’ll be among the first in. Early members get a launch perk.