Connect Asana and Postmark
Start a client’s workflow in Asana and act in Postmark, or the other way round, on the client’s own accounts.
Each app by itself: Asana integration and Postmark integration, with how to connect it, its scopes and its limits.
What the pair is used for
- A client contact who never opens Asana can be emailed each task added to their project, with its name, description, due date and section, from the agency’s verified Postmark sender.
- Completed tasks can go out the same way as a running report of finished work, one email per task as it is ticked off.
- A Postmark bounce can open an Asana task in a project you choose, so fixing a customer’s bad address becomes somebody’s job.
Every way Asana 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 Asana to Postmark
| When this happens in Asana | This runs in Postmark | How fast | Starter |
|---|---|---|---|
| A task is added to a project | Send an email | Within 5 minutes | Install the starter |
| A task is added to a project | Send a template email | Within 5 minutes | Two steps on the canvas |
| A task is completed | Send an email | Within 5 minutes | Install the starter |
| A task is completed | Send a template email | Within 5 minutes | Two steps on the canvas |
From Postmark to Asana
| When this happens in Postmark | This runs in Asana | How fast | Starter |
|---|---|---|---|
| An email bounces | Create a task | Within seconds | Install the starter |
| An email bounces | Update a task | Within seconds | Two steps on the canvas |
| A link in an email is clicked | Create a task | Within seconds | Two steps on the canvas |
| A link in an email is clicked | Update a task | Within seconds | Two steps on the canvas |
Set up the starter
Send an email in Postmark when a task is added to a project in Asana
- 1Install the starter into the client from Templates → Library. It lands switched off.
- 2Connect the client’s Asana, for “A task is added to a project”
- 3Connect the client’s Postmark, for “Send an email”
- 4Fill in Asana: Project ID (For example the number after
/project/ in the link) - 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 5 minutes: Asana is checked every 5 minutes.

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
- A task is added to a project: Consultation with Emma Collins
- Text
- A task is added to a project in Asana. Task: Consultation with Emma Collins Description: Kitchen tap leaking under the sink Due on: 2026-09-14T10:30:00Z Section: Consultation with Emma Collins Completed: true
- To
- emma.collins@example.com
Setup notes for this pair
- The task’s description goes into the email in full, so anything written there for the team reaches the recipient. The last line prints Asana’s completed value (true or false); drop it from mail meant for a client.
- The Section line reads the first section the task sits in.
- The bounce starter fills only the Asana project, so give the task a name from the bounced address and the email’s subject after installing.
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 finished tasks
Send an email in Postmark when a task is completed in Asana
| Postmark value | Filled from |
|---|---|
| From | [Postmark: From] |
| Subject | A task is completed: [the task’s name, from Asana] |
| Text | A task is completed in Asana. Task: [the task’s name, from Asana] Description: [the task’s notes, from Asana] Due on: [the task’s due on, from Asana] Section: [the task’s name, from Asana] Completed: [the task’s completed, from Asana] |
| To | [Who it goes to (Postmark)] |
Send an email for new tasks
Send an email in Postmark when a task is added to a project in Asana
| Postmark value | Filled from |
|---|---|
| From | [Postmark: From] |
| Subject | A task is added to a project: [the task’s name, from Asana] |
| Text | A task is added to a project in Asana. Task: [the task’s name, from Asana] Description: [the task’s notes, from Asana] Due on: [the task’s due on, from Asana] Section: [the task’s name, from Asana] Completed: [the task’s completed, from Asana] |
| To | [Who it goes to (Postmark)] |
Create a task for bounced emails
Create a task in Asana when an email bounces in Postmark
| Asana value | Filled from |
|---|---|
| Name | [the email’s subject, from Postmark] |
| Project | [Asana: Project ID] |
Asana 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.