Asana Task Creation
Create Asana tasks in the right workspace, project, and section from work inside the app.
What it adds
A server-side path from an in-app record to an Asana task, with workspace, project, section, assignee, and due date mapping.
What your agent is told to do
5
What your agent is told to do
5-
1
Let an administrator choose the workspace, project, section, default assignee, and due-date rule from what the connected account can see, and re-resolve each of those at creation time rather than trusting identifiers captured at setup.
-
2
Map app users to Asana identities through an explicit administrator-maintained mapping. Do not infer an assignee from a matching email address; the wrong person silently owning a task is worse than an unassigned one.
-
3
Compose the task on the server with a durable link back to the originating record, and keep private customer detail in the app behind that link rather than pasting it into the task where the whole project can read it.
-
4
Key each submission by the originating record and check for an existing task reference before creating, so a retry after a timeout reuses the task instead of creating a second one.
-
5
GitHub Issue Creation, GitLab Issue Creation, Linear Issue Creation, Jira Ticket Creation, and Trello Card Creation are siblings. Capture, redaction, deduplication, and reference storage belong to the shared path; this brief owns only Asana's workspace and project resolution and its user mapping.
Edge cases it handles
8
Edge cases it handles
8- Identity mapping between the app and Asana is the highest-risk part of this feature. Maintain it explicitly, leave the assignee unset when no mapping exists, and name the reporter in the task description instead of guessing.
- Projects, sections, and custom fields get removed or renamed by people who do not know the app depends on them. Resolve each at creation time, omit what no longer exists, still create the task, and warn an administrator about the broken mapping.
- A retry must not create a second task. Persist the returned task reference before acknowledging the job and check for it on every attempt, since a timeout usually means the task exists.
- The link back into the app must survive the record being renamed or moved, so link by stable identifier, and never include internal-only identifiers or customer personal data in the task body.
- Tasks get moved between projects, completed, or deleted inside Asana. Reconcile on read rather than assuming the stored reference still points where it was created, and show a clear state in the app when the task can no longer be found.
- Access tokens expire and refresh tokens get revoked when a member leaves. Refresh proactively, treat an authentication failure as terminal for the attempt, hold the queue, and prompt an administrator to reconnect.
- Rate limits require exponential backoff with jitter and a bounded retry count, with a dead-letter path for submissions that never succeed.
- If task events are consumed back into the app, treat them as at-least-once and possibly out of order: dedupe by event identifier and ignore events older than the state already held.
Definition of done
9
Definition of done
9- A record in the app can be sent to Asana as a task in the configured workspace, project, and section.
- User mapping is explicit and an unmapped reporter yields an unassigned task rather than a guess.
- Removed projects, sections, or custom fields degrade the task gracefully and warn an administrator.
- Retried submissions produce exactly one task.
- Every task links back to the originating record by a stable identifier, with private detail left in the app.
- Token expiry and revocation queue work and prompt a reconnection instead of dropping submissions.
- Tasks moved or deleted in Asana are reconciled on read and reflected accurately in the app.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Direct Messages
Direct Messages
Let two users hold a private conversation inside the app instead of leaving to email.
What it does
One-to-one private threads with message history, per-conversation unread counts, and blocking.
How it works
- 1 Build the conversation list, the thread view, and the unread badge. Keep the first version to one-to-one threads only and defer group conversations, reactions, threading, and file attachments rather than shipping all of them half-finished.
- 2 Reuse the app's existing Read and Unread State and Notification Center rather than inventing a second unread mechanism and a second alert path. A message notification should sit alongside every other notification the user gets.
- 3 Reuse the composer, mention handling, and rendering rules from Comments and Mentions instead of writing a second message editor with subtly different escaping.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/direct-messages
Voice Notes
Voice Notes
Say it instead of typing it, and attach the recording where the conversation is.
What it does
In-app recording of short audio notes attached to a record, comment, or message.
How it works
- 1 Add recording to the places where people already leave text, most likely alongside Comments and Mentions, so a voice note is another kind of comment rather than a separate feed nobody checks.
- 2 Store the recording through the app's existing file upload path so a voice note inherits the same retention and access rules as any other attachment on the record, and disappears with the record when it is deleted.
- 3 Show a live duration and a simple level meter while recording, and let the user review and discard before it is sent. Nobody should be committed to a recording the instant they stop.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/voice-notes
Assign Ownership
Assign Ownership
Make it obvious who is responsible for each record.
What it does
An assignee on records, with a picker, notifications on change, and a history of who owned what.
How it works
- 1 Add a nullable assignee to the relevant records. Unassigned is a real, valid state — do not force a default owner just to avoid the null.
- 2 Restrict the picker to users who can actually access the item, and validate that server-side as well as filtering the list.
- 3 Notify the new assignee when they are assigned by someone else, and record every change with the actor and timestamp.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/assign-ownership
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.