Automation Builder
Let customers wire a trigger, some conditions and an action so routine work runs itself.
What it adds
A visual builder where a customer connects a trigger to conditions and actions, plus the runtime that executes it and a log of what happened.
What your agent is told to do
5
What your agent is told to do
5-
1
Ship a fixed, curated set of triggers, conditions and actions drawn from what the app already does. A general-purpose scripting environment is not the minimum version, and offering one you cannot support is worse than offering ten steps that work.
-
2
Run automations through the app's existing background job system. If Background Job Dashboard or Scheduled Job Monitor exists, automation runs appear there rather than in a separate queue nobody watches.
-
3
Make the run log the centre of the feature, not an afterthought. A customer whose automation did nothing needs to see which run fired, what data entered each step, and where it stopped.
-
4
Record every action an automation performs in the app's existing audit trail, attributed to the automation and to the customer who owns it, so an unexplained change can be traced back.
-
5
Do not let an automation take an action the owning user could not take by hand. Evaluate permissions at run time against the owner, and pause the automation when those permissions are revoked.
Edge cases it handles
8
Edge cases it handles
8- One automation's action fires another's trigger, which fires the first again. Detect cycles when the automation is saved where the graph makes it visible, and cut off runaway chains at run time with a depth limit that stops the loop and reports it.
- Cap runs per period per customer, and when the cap is hit fail loudly. Silently dropping runs produces a customer who believes their automation is working for weeks.
- Every run needs a log showing the triggering record, the data as it entered each step, the condition results, and the outcome of the action. Without it, debugging is guesswork.
- A connected integration will lose its authorization. Pause the automation, tell the owner why, and hold or discard queued runs deliberately rather than retrying into a wall of authentication failures.
- Offer a dry run that evaluates the trigger and conditions against real data and reports what it would have done without doing it. Nobody should have to test an automation on live customer records.
- Editing an automation while runs are in flight must not corrupt them. Version the definition and let in-flight runs finish against the version they started on.
- A failed action needs a retry policy the customer can understand: how many times, how far apart, and what happens when it finally gives up.
- Deleting the record or field an automation depends on must disable it with a clear reason, not leave it failing quietly on every trigger.
Definition of done
9
Definition of done
9- A customer can build, enable, disable and delete an automation from a visual canvas.
- Runs execute through the app's existing background job infrastructure and are visible in its dashboard.
- Every run has a log showing input data at each step, condition results, and the final outcome.
- Loops are detected at save time and cut off at run time, with the customer told what happened.
- Run caps are enforced and hitting one surfaces a visible failure rather than dropped runs.
- An integration losing authorization pauses the automation and notifies the owner.
- A dry run reports intended actions without performing any of them.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Survey Builder
Survey Builder
Build a multi-question survey, send it out, and read all the answers in one place.
What it does
An authoring tool for multi-question surveys, a respondent flow, and a results view with export.
How it works
- 1 Ship a small, honest set of question types first: single choice, multiple choice, short text, long text, and a rating scale. That covers most real surveys. Defer matrix grids, file uploads, and calculated fields rather than half-building them.
- 2 Render the respondent flow with the app's existing Multi-Step Form and Conditional Form Fields, and reuse Form Field Shell for the inputs, so a survey looks and behaves like every other form in the product.
- 3 Give surveys the app's existing Draft and Publish States. Editing a live survey while responses are arriving is the main way survey data gets corrupted, so publishing must be a deliberate act with a clear boundary.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/survey-builder
Quiz Builder
Quiz Builder
Build a scored quiz with branching questions and a result page that reflects the answers.
What it does
An authoring tool for multi-question quizzes with scoring rules and answer-based branching, plus the taking experience and a result page.
How it works
- 1 Reuse the app's existing form machinery for the taking experience. If Multi-Step Form and Conditional Form Fields exist, the quiz runner is those features driven by the quiz definition, not a second form engine.
- 2 Support a small set of question types that actually score: single choice, multiple choice, and short text with an exact or pattern match. Free-text grading and media questions are a separate scope and should be deferred.
- 3 Give the author a way to see the quiz as a taker would, including a specific answer path, before it is published. A branching quiz cannot be checked by reading the editor.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/quiz-builder
Subtitle Editor
Subtitle Editor
Fix wrong words and bad timing on a caption track next to the video itself.
What it does
A side-by-side editor pairing the video player with an editable, time-aligned list of caption cues.
How it works
- 1 Build this on top of the caption tracks produced by Auto Captions rather than as a standalone tool. Editing a machine track is the main reason anyone opens this screen.
- 2 Show the cue list beside the player, keep the active cue highlighted as the video plays, and make clicking a cue seek the player to its start.
- 3 Let a cue be retimed by dragging its edges on a timeline and by typing exact timecodes. Dragging is faster; typing is the only way to be precise.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/subtitle-editor
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.