Skip to main content
Use the @bijection/connectors/asana entrypoint to declare Asana resources.

​
Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

​
Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

​
Tasks

​
pull: Project tasks by modified_since watermark, 404 withdrawal

The following example matches configuration standard.

​
Configuration: standard

Case: asana/tasks/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: asana. Keep credential material in the private credential inventory. Inspect the complete configuration contract below for settings and conditional requirements.
Native admission analysis is available for this exact declaration. Collection: tasks
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. A read-only source of one project’s tasks. Nothing here creates, updates or completes a task: Asana’s task update takes no precondition, so a write could only be unconditional and none is declared. The connection holds an asana credential (asana.credential): a personal access token or an OAuth access token, written Authorization: Bearer <token>. Identity is the token’s user gid from GET /api/1.0/users/me. tasks.pull walks GET /api/1.0/tasks?project=<gid>&limit=100 by the stated next_page.offset, asking for completed_since=1970-01-02T00:00:00.000Z so completed tasks are listed as well as open ones. Each finished pass carries the latest modified_at it read; the next pass adds modified_since five minutes before it, and re-read tasks are deduplicated by modified_at (an opaque version). Asana documents that modified_at moves on renaming, completing, assigning, due-date and custom-field changes and on trashing, and that a move to another container does not move it; only fields it covers are published (name, completed, completedAt, dueOn, assignee). The listing claims no coverage: a task missing from it is not withdrawn. A daily point read of each published task (GET /api/1.0/tasks/<gid>) withdraws it on 404, which Asana documents as “the object specified by the request does not exist”; missing access is a documented 403 and withdraws nothing. Asana answers every exceeded limit (150 or 1,500 requests per minute by plan, 50 concurrent reads, cost limits) with 429 and Retry-After, which is the declared backoff. The Events API is not declared. Its first request and any expired sync token are answered 412 with the next token inside the 412 body, which the engine’s incremental protocol cannot accept as a baseline, and an event has no identity of its own while one task can appear in several events of one response. Declared from Asana’s published reference; nothing here has run against Asana or been qualified.

​
Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

​
Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.