Asana

Turn feedback into tasks. Automatically create Asana tasks when feedback is submitted, and keep statuses synchronized between Quackback and Asana. When a task moves between sections in your Asana project, the linked feedback post updates too.

Note: On Quackback Cloud, integrations are available on the Business and Enterprise plans. Self-hosted installs include every integration.

Overview

The Asana integration enables:

• Create Asana tasks from feedback posts: automatically create a task when new feedback is submitted
• Link posts to tasks: link feedback posts to Asana tasks for traceability
• Status sync: keep feedback status in sync with Asana task sections via inbound webhooks

Prerequisites

• The Owner or Admin role in Quackback (or a custom role that can manage integrations)
• An Asana account with access to the target workspace
• Self-hosted only: an Asana OAuth application (created at Asana Developer Console)

Self-hosted: create your Asana app

Note: On Quackback Cloud, skip this section. Quackback provides the Asana app for you, so you go straight to connecting.

Self-hosted instances connect through an app you create. Do this once before you connect.

Create an Asana OAuth application

1. Go to Asana Developer Console
2. Create a new OAuth application
3. Copy the Client ID and Client Secret

Save the app credentials in Quackback

1. Go to Admin > Settings > Integrations > Asana

2. Enter the following credentials:

   • Client ID from your Asana OAuth application
   • Client Secret from your Asana OAuth application

Setup

1. Connect your workspace

1. Go to Admin > Settings > Integrations > Asana
2. Click Connect to Asana
3. You'll be redirected to Asana to authorize the application
4. Review the permissions and click Allow

After authorization, Quackback automatically detects your Asana workspace.

2. Select a project

Back in Quackback:

1. Choose the Asana project where tasks should be created
2. Only active (non-archived) projects are shown

3. Configure status mappings

Map Asana sections to Quackback statuses:

1. Go to the Asana integration settings
2. Configure status mappings between Asana section names and Quackback statuses
3. Each Asana section name can be mapped to a corresponding Quackback status, or set to ignore

Status sync works via Asana webhooks. When a linked Asana task is moved to a different section, the corresponding Quackback post status updates automatically.

4. Configure events

Choose which events trigger Asana actions:

Note: The Asana integration creates tasks only for post.created events. Status changes and comments are handled through status sync rather than by creating new tasks.

5. Save and test

1. Click Save
2. Submit test feedback to verify a task is created in Asana

Task format

When a new feedback post triggers task creation, the Asana task includes:

• Name: The feedback post title
• Notes (HTML): The post content, followed by metadata including the author, board, vote count, and a link back to the post in Quackback

The task is created in the selected project within your connected Asana workspace.

Status sync

When status sync is configured, Quackback registers a webhook with Asana to receive task change events. Asana uses sections within a project as status indicators. When a linked task is moved to a different section:

1. Asana sends a compact webhook event to Quackback
2. Quackback fetches the task details via the Asana API to determine the current section
3. If a status mapping exists for that section name, the linked feedback post's status is updated

The webhook uses Asana's handshake protocol: the initial setup request includes an X-Hook-Secret header that Quackback echoes back. Subsequent events are verified using HMAC-SHA256 via the X-Hook-Signature header.

The webhook is filtered to only receive task change events related to section membership, keeping traffic minimal.

On post delete

When you delete a feedback post with a linked Asana task, you can complete the task at the same time. The delete dialog shows a checkbox for each linked task.

To pre-check this by default, enable the On post delete toggle in the Asana integration settings. You can always override the default per delete.

Manage the integration

Pause

Temporarily stop the integration:

1. Go to Admin > Settings > Integrations > Asana
2. Toggle Enabled off
3. Task creation and status sync pause, but the connection remains

Reconnect

If you see connection errors:

1. Click Reconnect
2. Re-authorize in Asana

Tokens are refreshed automatically when they expire (Asana access tokens last about one hour).

Disconnect

To fully remove the integration:

1. Go to Admin > Settings > Integrations > Asana
2. Click Disconnect
3. Confirm the action

Note: Disconnecting revokes the OAuth token with Asana and removes the registered webhook.

Who is shown as the creator?

Quackback creates tasks in Asana as the account that connected the integration, so Asana shows that person as the creator. To change the creator (for example, to a shared bot account), disconnect, sign in to Asana as the other account, and connect again.

Troubleshooting

Tasks not being created

1. Check integration status: look for errors in settings
2. Verify project selection: ensure an Asana project is selected
3. Check event mappings: confirm post.created is mapped
4. Workspace access: the connected Asana account must have access to the selected project

Status sync not working

1. Check status mappings: ensure Asana section names are mapped to Quackback statuses
2. Verify webhook: the Asana webhook may need to be re-registered
3. Section-based status: Asana uses sections (not custom fields) as the status indicator for sync

"Authentication Failed" error

Asana OAuth access tokens expire after about one hour and are automatically refreshed. If refresh fails:

1. Click Reconnect
2. Re-authorize the app in Asana

Related articles

• ClickUp: ClickUp task integration
• Linear: Linear issue integration
• Integrations overview: All integrations