ClickUp Task Creation
Turn app events into ClickUp tasks in the right list, with fields and assignees mapped.
What it adds
A connected ClickUp account, a per-workspace mapping of app events to a target list, and a background job that creates and updates tasks.
What your agent is told to do
5
What your agent is told to do
5-
1
Find the app events worth pushing outward — a new support ticket, an escalation, an overdue item — and let an administrator choose which of them create tasks, rather than pushing everything.
-
2
Store the connection against the workspace, not the individual who authorised it, and keep tokens in server-side storage the browser never reads. Refresh expiring credentials in the background and mark the connection as needing re-authorisation when a refresh fails.
-
3
Let the administrator pick the destination by walking the account's own hierarchy of workspace, space, folder, and list, fetched live at configuration time. Do not ask the user to paste an identifier they have to find in a URL.
-
4
Persist the mapping between app fields and destination fields by the remote identifier, and re-validate that mapping before each send so a removed field surfaces as a configuration warning rather than a silent drop.
-
5
Reuse the app's existing background-job system for every send, and record the created task's identifier against the source record so a retried job updates the existing task instead of creating a second one.
Edge cases it handles
8
Edge cases it handles
8- The destination is four levels deep — workspace, space, folder, list — and a task created in the wrong list is invisible to the team that needed it. Resolve and store the full path, and re-check it exists before each send.
- Custom fields must be mapped by their stable remote identifiers, never by their display names, because names are renamed freely. Each field also has a type, and sending a free-text value into a numeric or dropdown field is rejected outright.
- Available statuses differ from one list to another, so a status that is valid in one destination does not exist in another. Read the destination's own status set at configuration time and refuse a mapping that no longer resolves.
- A job that times out after the remote side has already created the task will create a duplicate on retry. Send a stable idempotency value derived from the source record and reconcile against the stored task identifier before creating anything.
- The connected account's permissions decide who can be assigned and what can be seen. Do not assign a user who is not a member of the destination, and do not copy internal notes or customer data into a task that a wider audience can read.
- Rate limits will be hit during a backfill or a burst of events. Back off and retry on the provider's own signal, and never spin a tight retry loop that makes the limit worse.
- When the provider is unavailable the app's own action must still succeed. Queue the task creation, show the user that it is pending, and surface a failed send in the record's activity rather than as a dead end.
- Revoking the connection in ClickUp gives no notification. Detect repeated authorisation failures, disable the mapping, and tell an administrator instead of retrying forever.
Definition of done
8
Definition of done
8- An administrator connects ClickUp once per workspace and selects a destination by browsing the account's real hierarchy.
- Field mappings are stored by remote identifier and re-validated before each send, with removed fields reported as configuration warnings.
- A retried or duplicated job updates the existing task rather than creating a second one.
- Task creation runs in the background and never blocks or fails the user's own action.
- Rate limits and provider outages result in backoff and a visible pending state, not lost events.
- Credentials are never present in client-visible code, and a revoked connection is reported to an administrator.
- 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.