Skip to main content
Technical Preview

Overview

A client-mode connector for a curated work-management slice of the Asana REST API: Default BASE_ADDRESS is https://app.asana.com/api/1.0. Topics use devops/asana/<object>/<verb>.
Auth is Bearer personal access token or OAuth 2.0 access token (Authorization: Bearer …). Prefer Hub secret ASANA_ACCESS_TOKEN (aliases ASANA_PAT, ASANA_TOKEN). Status remains blocked until an authenticated live smoke succeeds.

Basic Syntax

Events

Auth

  1. Create a personal access token in Asana developer console, or obtain an OAuth 2.0 access token.
  2. Set connector BASE_ADDRESS to https://app.asana.com/api/1.0.
  3. Pass access_token on MQTT JSON payloads so the Bearer header resolves. For path params, also pass user_gid / task_gid / project_gid.
  4. Store secrets in Hub / GET SECRET "ASANA_ACCESS_TOKEN" (aliases ASANA_PAT, ASANA_TOKEN). Never commit real credentials.
  5. Successful smoke: GET /users/me → HTTP 200 with data.gid. Invalid tokens → HTTP 401.

Example payloads

getUser (smoke):
createTask:
updateTask:
createWebhook:

Server / inbound companion

POST /webhooks is client-mode registration (MQTT → Asana). Asana then POSTs events to your target URL (handshake with X-Hook-Secret). Receiving those callbacks into MQTT requires a separate companion ENABLE_SERVER connector — not included in AsanaRestApi.lot.

Deploy notes

Sources

Last modified on October 21, 2026