---
title: "Asana Slack integration with an AI agent: create, assign, check tasks | Chickpea"
description: "An Asana Slack integration you talk to. Give a channel an AI teammate connected to Asana, then ask it to create tasks, assign work, and check what is due. Open source."
canonical: https://chickpea.co/connectors/asana
keyword: "Asana AI agent in Slack"
verified: 2026-09-17
---

# An Asana AI agent in your Slack channels.

> Chickpea gives a channel a named AI teammate that holds its own Asana connection: an Asana Slack integration you talk to. Ask it in plain words to create a task, assign it, move the date, or say what is still open, and it answers in the thread, with a link into Asana.

Facts checked against the sources on September 17, 2026. The HTML page is at https://chickpea.co/connectors/asana; every connector is listed at https://chickpea.co/connectors; the site index for agents is at https://chickpea.co/llms.txt.

**Asana** (Asana, Inc., https://asana.com): Find, create, and update tasks, projects, teams, and portfolios. Category: Project management. Lane: Direct API. Sign in: API token.

**Chickpea**: an open source Slack app that gives a workspace named AI teammates, each with its own handle, instructions, memory, connected accounts, schedules, and model, deployed to your own Cloudflare account or a Node host.

## What people ask it
The teammate in these examples is @pm, published to #ops.

### Create
- @pm add a task in Website: update the pricing page, Dana, due Friday
- @pm turn this thread into a task in Launch and assign it to Marco

A new task is a small, reversible write, so it goes straight through. The reply names the project, the owner, and the date it set, with a link to the task.

### Assign and reschedule
- @pm assign the pricing task to Marco
- @pm move Priya's overdue tasks to me and push them to Friday

One task changes on the spot. A change across several tasks comes back as a summary of what would move, and waits for a yes.

### Check status
- @pm what's open in Website, and who has what
- @pm what did we close in Launch this week

Reads never need confirmation. A long answer comes back as a table in the thread. Free-text search across a whole workspace uses an Asana endpoint that Asana limits to its paid plans; listing a project does not.

### Comment and close
- @pm comment on the pricing task that legal signed off
- @pm mark the customer logos task complete

A comment or one completion applies immediately. It can complete a task but never delete one: the connection allows no deletes.

### On a schedule
- @pm every Monday at 9am Pacific, post what's due this week in Website
- @pm every Friday at 4pm Eastern, list what slipped this week

A schedule saves on the spot. It needs a time zone, runs under the Asana connection of the person who asked, and stops rather than runs if that connection is ever disconnected.

### Example conversations

**Create a task**
> **Priya:** @pm add a task in Asana: update the pricing page before the launch. Website project, assign it to Dana, due Friday.
> **@pm:** Done. Update the pricing page before the launch is in Website, assigned to Dana, due Fri Sep 25. Open it in Asana

**What is still open**
> **Marco:** @pm what's still open in the Website project, and who has what?
> **@pm:** Five tasks are open. Two are past due, both Priya's. Nothing is waiting on someone outside the team.
>
> | Task | Owner | Due | Status |
> |---|---|---|---|
> | Pricing page copy | Priya | Sep 15 | Overdue |
> | Customer logos section | Priya | Sep 16 | Overdue |
> | Update the pricing page | Dana | Sep 25 | Open |
> | Launch announcement draft | Marco | Sep 28 | Open |
> | QA pass on mobile | Sofia | Sep 30 | Open |

**Reassign and comment**
> **Dana:** @pm Priya is out this week. Move her two overdue tasks to me, push both to Friday, and leave a comment on each saying why.
> **@pm:** That touches two tasks, Pricing page copy and Customer logos section. Each moves to you, gets a due date of Fri Sep 25, and a comment: "Reassigned to Dana while Priya is out this week." Go ahead?
> Buttons: Yes, update both · Change something

**Every Monday**
> **Sofia:** @pm every Monday at 9am Pacific, post what's due this week in Website here, grouped by owner.
> **@pm:** Saved. Every Monday at 9:00 AM Pacific I'll post the Website tasks due that week in #ops, grouped by owner. First run is Mon Sep 21. Say "pause the Monday digest" any time.

## Connect Asana
1. In Asana, open the developer console at [app.asana.com/0/my-apps](https://app.asana.com/0/my-apps) and create a personal access token. Asana notes that the token acts as the user who made it.
2. In Chickpea Admin, open the teammate, then **Connections**, find **Asana**, and choose **Connect**. Or ask in Slack, `@pm connect Asana`, and follow the link it posts.
3. Choose who uses it. **Team** is one shared token that everyone who can use the teammate acts through. **Personal** means each member pastes their own token, and Asana records their actions as them.
4. Paste the token into the write-only credential field. It is stored once on your deployment and never returned to the browser, the model, or Slack.
5. Ask something. `@pm what is open in Website` is a good first question, because it reads and cannot change anything.

A connection belongs to one teammate. Giving a second teammate Asana means a second connection with its own token, so the finance teammate never inherits what the project teammate can reach.

## What the teammate is handed with Asana
A teammate with an Asana connection is handed a built-in skill for the Asana API: the base URL, the response shape, pagination, and tested recipes for projects, tasks, comments, and search. You write instructions about your team, not about endpoints.

The skill is open source: https://github.com/pejmanjohn/chickpea/blob/main/src/config/connector-skills.ts

## Beside Asana
- **Zendesk:** Escalated tickets become tracked tasks
- **Linear:** Product work in Asana, engineering work in Linear, one teammate that reads both
- **Google Calendar:** Due dates onto calendars
- **Gmail:** A request in an inbox becomes a task with an owner
- All 37 connectors: https://chickpea.co/connectors

## Questions people ask

### Can an AI agent create Asana tasks from Slack?
Yes. Mention the teammate, say what the task is, which project it belongs in, who owns it, and when it is due, and it creates the task through the Asana API and replies with a link. Anything you leave out, it asks about or leaves blank rather than guessing.

### Do I still need the Asana for Slack app?
Keep it if you rely on its notifications, since a Chickpea teammate has no way to hear from Asana when a task changes. The two run side by side; the teammate uses the API with its own token and does not touch the official app.

### Which Asana plan does this need?
Any plan whose account can create a personal access token. Listing projects and tasks, creating, updating, and commenting work on Asana's free tier. Workspace-wide task search is an endpoint Asana reserves for its paid plans, so "find the task about X" needs one; "what is open in Website" does not.

### Can it delete tasks?
No. The Asana lane allows GET, POST, and PUT only, so the teammate can complete a task but never delete one, whatever it is asked. That limit lives in the connection policy, not in the instructions.

### Does everyone act as the same Asana user?
That is your choice when you connect. A team account is one token, and Asana records every action as the person who made it. A personal account means each member pastes their own token and appears as themselves.

### Will it post in Slack when an Asana task changes?
Not on its own. There are no Asana webhooks in this lane. Ask for a schedule instead, such as a Monday morning list of what is due this week, and it posts that to the channel at the time you set.

### Where does my Asana token live?
On your deployment, in a write-only field. It never enters the model's context, the tool arguments, or Slack. If you disconnect the account, the stored secret is removed and any schedule that depended on it is paused.

### Can it use Asana together with Linear, GitHub, or Zendesk?
Yes. A teammate can hold several connections, each granted to it alone, and one ask can read one and write another. Pages for those pairs are on the way; the gallery lists everything a teammate can connect to today.

### Does Asana integrate with Slack?
Two ways. Asana ships its own Slack app for notifications and for turning a message into a task. A Chickpea teammate is the other way: it holds an Asana connection and does what you ask in the channel, through the Asana API. The two run side by side.

### How do I integrate an AI agent in Slack?
Deploy Chickpea to your own Cloudflare account, connect Slack, and ask for a teammate in a sentence. Then connect Asana to that teammate, from Admin or from Slack. It is four steps and one token, and nothing about your team passes through a vendor in between.

### How do I get an Asana personal access token?
Open the developer console at app.asana.com/0/my-apps, create a personal access token, and copy it once. Asana notes that the token acts as the user who made it, so create it from the account the teammate should act as. Paste it into the write-only field when you connect.

### Is this the same as Asana AI Teammates?
No. AI Teammates is Asana's own product: agents that live inside Asana and can reach out to tools such as Slack. A Chickpea teammate lives in Slack, on infrastructure you run, and reaches into Asana through the API with a token you control. Want the agent inside Asana, use theirs. Want it in the channel beside your other tools, use this.

### Does it use Asana's MCP server?
No. The Asana connector is a direct API lane: the teammate calls app.asana.com/api/1.0 with a personal access token, confined to GET, POST, and PUT. Asana's MCP server is built for coding clients and desktop assistants, and this page does not cover it.

## Sources
- [Chickpea docs: connector catalog, the Asana preset and its lane](https://docs.chickpea.co/reference/connector-catalog/)
- [Chickpea docs: connections, team and personal accounts, how a credential reaches a call](https://docs.chickpea.co/agents/connections/)
- [Chickpea docs: authority and confirmation](https://docs.chickpea.co/security/authority-and-confirmation/)
- [Chickpea docs: connect a service](https://docs.chickpea.co/agents/connect-a-service/)
- [Chickpea docs: schedules](https://docs.chickpea.co/agents/schedules/)
- [Chickpea source: the Asana preset (hosts, path, methods, token hint)](https://github.com/pejmanjohn/chickpea/blob/main/src/config/presets.ts)
- [Chickpea source: the built-in Asana API skill and its recipes](https://github.com/pejmanjohn/chickpea/blob/main/src/config/connector-skills.ts)
- [Asana developers: personal access tokens](https://developers.asana.com/docs/personal-access-token)
- [Asana developers: search tasks in a workspace, paid plans only](https://developers.asana.com/reference/searchtasksforworkspace)
- [Asana: the Asana for Slack app](https://asana.com/apps/slack)
- [Asana: AI Teammates](https://asana.com/product/ai/ai-teammates)
- [Asana developers: using the Asana MCP server](https://developers.asana.com/docs/using-asanas-mcp-server)
- [Chickpea source on GitHub](https://github.com/pejmanjohn/chickpea)

## More
- [Ahrefs MCP in Slack](https://chickpea.co/connectors/ahrefs.md)
- [Airtable MCP in Slack](https://chickpea.co/connectors/airtable.md)
- [Jira and Confluence MCP in Slack](https://chickpea.co/connectors/atlassian.md)
- [BugSnag MCP in Slack](https://chickpea.co/connectors/bugsnag.md)
- [Cloudflare MCP in Slack](https://chickpea.co/connectors/cloudflare-api.md)
- [Exa MCP in Slack](https://chickpea.co/connectors/exa.md)
- [Firecrawl MCP in Slack](https://chickpea.co/connectors/firecrawl.md)
- [Fireflies MCP in Slack](https://chickpea.co/connectors/fireflies.md)
- [Gamma MCP in Slack](https://chickpea.co/connectors/gamma.md)
- [Gmail AI agent in Slack](https://chickpea.co/connectors/gmail.md)
- [Gong AI agent in Slack](https://chickpea.co/connectors/gong-managed.md)
- [Google Ads AI agent in Slack](https://chickpea.co/connectors/google-ads.md)
- [Google Analytics AI agent in Slack](https://chickpea.co/connectors/google-analytics.md)
- [Google Calendar AI agent in Slack](https://chickpea.co/connectors/google-calendar.md)
- [Google Docs AI agent in Slack](https://chickpea.co/connectors/google-docs.md)
- [Google Drive AI agent in Slack](https://chickpea.co/connectors/google-drive.md)
- [Google Search Console AI agent in Slack](https://chickpea.co/connectors/google-search-console.md)
- [Google Sheets AI agent in Slack](https://chickpea.co/connectors/google-sheets.md)
- [Google Slides AI agent in Slack](https://chickpea.co/connectors/google-slides.md)
- [Granola MCP in Slack](https://chickpea.co/connectors/granola.md)
- [HubSpot AI agent in Slack](https://chickpea.co/connectors/hubspot-managed.md)
- [Hugging Face MCP in Slack](https://chickpea.co/connectors/huggingface.md)
- [incident.io MCP in Slack](https://chickpea.co/connectors/incident-io.md)
- [Intercom MCP in Slack](https://chickpea.co/connectors/intercom.md)
- [Linear MCP in Slack](https://chickpea.co/connectors/linear.md)
- [LunarCrush MCP in Slack](https://chickpea.co/connectors/lunarcrush.md)
- [Meta Ads MCP in Slack](https://chickpea.co/connectors/meta-ads.md)
- [Monday.com MCP in Slack](https://chickpea.co/connectors/monday.md)
- [Neon MCP in Slack](https://chickpea.co/connectors/neon.md)
- [Notion Slack integration with an AI agent](https://chickpea.co/connectors/notion-managed.md)
- [PostHog MCP in Slack](https://chickpea.co/connectors/posthog.md)
- [Sentry MCP in Slack](https://chickpea.co/connectors/sentry.md)
- [Stripe MCP in Slack](https://chickpea.co/connectors/stripe.md)
- [Supabase MCP in Slack](https://chickpea.co/connectors/supabase.md)
- [YouTube AI agent in Slack](https://chickpea.co/connectors/youtube-managed.md)
- [Zendesk AI agent in Slack](https://chickpea.co/connectors/zendesk.md)
- [All connectors](https://chickpea.co/connectors.md)

## Try Chickpea
- Site: https://chickpea.co/
- Deploy to Cloudflare: https://deploy.workers.cloudflare.com/?url=https://github.com/pejmanjohn/chickpea
- Source, Apache 2.0: https://github.com/pejmanjohn/chickpea
- Docs: https://docs.chickpea.co