View Categories

Asana

Configure the Asana action to let your Noem.AI chatbot create tasks in a specific Asana project based on natural-language requests. After configuring, you will reference this action by its Function Name inside the bot’s Instructions so the AI knows when to call it.

What this action does #

  • Creates a new task in a chosen Asana project.
  • Populates the task name (title) and description from details the bot extracts during the conversation.
  • Optionally includes user/context fields (e.g., reporter email) if you instruct the bot to add them to the description.

Configuration #

  1. Function Name
    • A short identifier used in your bot’s Instructions to invoke this action.
      Example: asana_create_bug.
    • Usage in Instructions:


      “When a user reports a bug, call function asana_create_bug.”

  2. Function Description
    • Describe when and how the bot should use this action. Be explicit about triggers and required fields.
      Example:
      “Use asana_create_bug when the user reports product issues (e.g., errors, crashes, broken links). Ask for title, steps to reproduce, expected vs. actual result, environment (OS, browser), and priority. Confirm details before creating the task.”
  3. Asana Personal Access Token
    • Generate a Personal Access Token in your Asana account settings.
    • Paste the token here. Use a workspace/user with permission to create tasks in the target project.
    • Keep tokens secure and scoped to least privilege.
  4. Test — Click Test to validate the token.
  5. Asana Project ID
    • Open your Asana project in the browser and copy the project ID from the URL.
      Format example: https://app.asana.com/1/XXX/project/[PROJECT_ID]/XXX
    • Paste the ID here.
  6. Test — Click Test to confirm the project is accessible with the provided token.
  7. How to Name the Task
    • Tell the AI what to collect for the task title. Keep it concise and structured.
      Guidelines & examples:
      • Bugs: “[Bug] <Product/Area>: <Brief issue>”
        Example: [Bug] Checkout: 500 error on submit
      • Requests: “[Feature] <Area>: <Outcome>”
        Example: [Feature] Dashboard: export to CSV
      • Support items: “[Support] <Topic>: <Key detail>”
  8. What to Fill the Task Description With

Specify exactly which fields the bot should assemble in the description and their order.
Recommended template (bugs):

Reporter: {{user.email}}

Summary: {{short_title}}

Steps to Reproduce:

1) …

2) …

Expected Result:

Actual Result:

Environment: OS {{os}}, Browser {{browser}}, App Version {{version}}

Priority: {{priority}}

Attachments/Links: {{urls or uploaded files}}

Conversation Link: {{chat_url}}

Feature request template (example):

Requester: {{user.email}}

Problem/Job-to-be-done:

Proposed Solution:

Impact/Use Cases:

Priority/Deadline:

Related Screens/URLs:

  1. Save
    • Click Save to store the configuration.

Add decision rules in your bot’s Instructions #

Include clear, testable rules so the AI knows when to call the Asana action and what to gather:

  • Intent mapping:
    “If the user reports a bug or feature request, use asana_create_bug (bugs) or asana_feature_request (features).”
  • Parameter extraction:
    “Capture title, steps, expected vs. actual result, environment, priority, and user email.”
  • Confirmation:
    “Before creating the task, restate the title and key details and ask for confirmation: ‘Create this Asana task now?’”
  • Failure/fallback:
    “If required fields are missing after one clarification, create the task with what we have and mark missing fields as TBD.”

Example instruction snippet:

When a user says anything like “there’s a bug,” “file a ticket,” or “create a task,”

call function `asana_create_bug`. Name format: “[Bug] <Area>: <Issue>”.

Fill the description using the bug template. Include the user’s email if available.

Ask for confirmation before submitting.

Testing #

  1. In Actions → Asana, press Test to verify token and project access.
  2. Open the chatbot preview and say: “Create an Asana task: Checkout returns 500 after clicking Pay.”
  3. Ensure the bot asks for missing details, confirms, then creates the task.

Check Asana for the newly created task with the expected title and description.

Where should we send your invitation to?