> ## Documentation Index
> Fetch the complete documentation index at: https://docs.inflection.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrate with Asana

> Tag an Asana task and the Inflection agent reads the brief, builds an Inflection email, and posts the result back to the task.

The Inflection agent in **Asana** meets content ops where briefs already live. **Tag a task** and the agent reads the brief, builds an Inflection email, and posts the result back to the task — no copy-pasting between your project tracker and the platform. It's a focused, workflow-triggered surface centered on email creation.

## Why use Asana

**Briefs become assets automatically.** The task you were going to write up anyway becomes a drafted email.

**Content ops stays in one place.** Writers and PMs work in Asana; the email shows up on the task.

**Trigger-based, hands-off.** No new tool to learn — a tag, assignment, or section change kicks off the build.

## What you can do here

### Build an email from a tagged task

The agent reads the task's brief and generates an Inflection email asset, posting a link/preview back as a task comment for review.

**Why it matters:** the brief-to-email handoff that used to be manual now happens the moment a task is ready.

<Info>
  **How it runs**

  * Write the email brief in the Asana task description.
  * Trigger the agent: assign the task, add a tag (e.g. "AI: build email"), or move the task to a new section.
  * The agent replies on the task with the generated email.
</Info>

### Build from a design (tenant skill)

Where enabled, a companion skill builds an Inflection email from a **Figma** design (`inflection-email-from-figma`) — useful when design hands off comps rather than copy.

<Info>
  **Availability:** the Asana → email flow is delivered as a connected-agent / skill and may be enabled per tenant — check with your CS team.
</Info>

## Step 1 — Create a Personal Access Token in Asana

<Warning>
  Please note that the actions done by Inflection Agent in Asana (comment in the ticket) will reflect as coming from the user account that made the PAT. It is advisable to create a new user in Asana (like "Inflection Bot") and use that account to create the PAT. This way all actions on tickets will be made by "Inflection Bot".
</Warning>

[Watch the Personal Access Token walkthrough on Loom](https://www.loom.com/share/4c1441067b2043a39ee0a135f416f703)

1. Navigate to [https://app.asana.com/0/my-apps](https://app.asana.com/0/my-apps)
2. Create a new Personal Access Token
3. Give it a relevant name
4. Copy the token — keep it safe, you won't be able to see it again

## Step 2 — Connect Asana in Inflection

[Watch the connection walkthrough on Loom](https://www.loom.com/share/3263c280b40940dd88a5ec86af50fd10)

1. Go to the Connections tab: [https://app.inflection.io/connections](https://app.inflection.io/connections)

2. Click **+ Add new connection**

3. Select **Asana** → enter a name for the connection → paste the PAT you copied from Asana

4. In the AI Agent triggers, add your Asana project ID where the Campaign Ops Agent will work on tasks

   <Tip>
     Your project ID is the string of numbers in your project's URL — it looks like `https://app.asana.com/0/projectID/list`
   </Tip>

5. Set the trigger condition — choose when you want the agent to pick up tasks:
   1. When the task is assigned to someone
   2. When a tag is added
   3. When a section is changed

You're good to go! Whenever a trigger condition is met, the agent picks up the task, builds emails, and comments back on the Asana ticket.

## Use cases & inspiration

**Editorial calendar → emails.** Each content task, once briefed and tagged (or assigned), comes back with a drafted email ready for review.

**Design-led campaigns.** Hand off a Figma comp and get a matching Inflection email to refine.

## Good to know (limitations)

**Email-focused.** The Asana surface centers on building emails from a brief — audiences, segments, and journeys live in the in-app chat / MCP.

**Tenant-scoped today.** Delivered as a connected agent / skill; availability and exact trigger behavior vary by tenant.

**Drafts for review.** The generated email is a starting point you refine and approve before sending.

## Prompting best practices

**Write the brief like you mean it.** Audience, goal, key message, and CTA in the task description produce a better first draft.

**One task, one email.** Keep each task scoped to a single email for a clean result.

## Report unexpected outcomes

Share issues in your Inflection Slack channel with the task link, your goal, and screenshots of the brief and the generated output.

## Share your use cases

Tell us how Asana fits your content workflow — what triggers and outputs would help most.