ScriptTap

Start at the useful moment

Start a script when you need it

Let a time, app, notification, or screen condition start a useful script automatically. A routine connects one condition → one saved script, so you do not have to press Play for every occurrence.

Routines · overview about 5 minutes · focused examples about 3–5 minutes · captions + written steps

Choose a trigger, then try a useful example

This overview previews all six forms. It does not save, enable, or run a routine.

Choose the condition that solves your need

You want to…ChooseConfigure
Show an on-screen reminder at a planned time while using the device.TimeStart date/time; optional repeat interval.
Show a checklist when you open a particular app.App ActivatedSelected app; foreground app access.
Start a follow-up after an app's new notification, such as a download notice.NotificationSource app; optional text and case sensitivity.
React to an accessible button or label that indicates readiness.UI Element FoundQuery, target, match mode and filters.
React when a distinctive picture appears in a known location.Image FoundSaved reference, area and confidence.
React when a small status indicator reaches a particular color.Pixel FoundLiteral color, point or short line, confidence.

Connect the trigger to a ready script

  1. Open Routines and add a separate setup

    Open Main Overlay menu → Routines → + Add Routine. Pick a saved script, then use the second Pick button for its trigger. Search the Trigger Library by name. Routines are separate from scripts, not editor commands.

    Timeout limits the routine's script run; zero leaves that limit unset. Complete both script and trigger selections before saving.

    Routine Editor with Script Pick, Trigger Pick, Timeout, Run and When summaries
  2. Time: schedule a useful start

    Enter the local start date and time in the displayed format. Repeat Every OFF creates one occurrence. Turn it ON for Repeat Frequency in hours, minutes and seconds; the minimum repeat is five seconds.

    Checking frequency only checks which occurrence is due. Cooldown spaces successful starts; it does not repeat the same occurrence. Missed repeat occurrences during cooldown are not replayed in a batch.

    Time Trigger with Repeat Every ON and interval fields
  3. App Activated: respond to the foreground app

    Select the app whose foreground state matters. Foreground app access is required. Checks are periodic, so a very brief appearance may be missed. After firing, the condition must be observed false before it can re-arm.

    App Activated Trigger with foreground access requirement and app Select control
  4. Notification: start a relevant follow-up

    Select the source app. Containing Text OFF accepts any matching notification event from that app. Turn it ON to require a text fragment; Case Sensitive makes capitalization significant.

    This event-driven trigger uses ScriptTap's Accessibility connection, not a polling timer or notification-history scan. It does not create the notification. Android or the source app may omit or redact text, so test your actual notification before relying on a text filter.

    Notification Trigger with Containing Text ON, a Text field and Case Sensitive OFF
  5. UI Element Found: use exposed app elements

    Enter a query. Target chooses Any, Text, Content Description, View ID, or Class. Match supports Contains, Exact, and Regex; a regular expression is a text-matching pattern. Nth Match chooses among matches, starting at one.

    Scroll for Enabled, Clickable, Visible and Package Filter. Visible is ON by default. The condition re-arms after an observed false result. It reads Accessibility elements, not pixels; some games and custom views expose little useful information.

    UI Element Found Target dropdown with accessible element fieldsEnabled, Clickable, Visible and Package Filter in the scrolled form
  6. Image Found: recognize a stable reference

    Select a saved reference, a focused screen area, and confidence. Higher confidence requires a closer aggregate picture match; 100 requires exact active pixels. Reuse the shared asset-creation guide instead of making a new crop for every use.

    Screen capture is required. By default, an image that remains visible can trigger again after cooldown. Choose suitable checks and limits. Watch the focused Image Found example for a real automatic confirmation.

    Image Found Trigger with Asset, Area, Confidence and screen capture requirement
  7. Pixel Found: use a small color signal

    Enter a literal #RRGGBB color and select a point or short line, not a broad rectangle. Confidence 100 requires exact red, green and blue channel values; lower confidence allows more per-channel variation.

    Screen capture is required. This condition can also repeat after cooldown while it matches. Test matching and non-matching states. Watch the focused Pixel Found example for a real hidden-cue test and automatic confirmation.

    Pixel Found Trigger with Hex Color, Area, Confidence 100 and screen capture requirement
  8. Enable deliberately, then test

    Complete one trigger, choose a ready script, and save the Routine Editor. Both Routines Enabled and the routine's checkmark must be ON. A minus means desired-disabled. Missing access, a locked device, limits, or an invalid target can still prevent a start.

    Start with a short visible confirmation such as PromptMe. Check the condition is the one you need, then disable the test routine before trying another example.

Do not confuse three timing controls

Repeat Frequency creates Time occurrences. Check frequency controls how often a polled condition is evaluated. Cooldown spaces successful fires. Notification is event-only, so its settings have no checking-frequency field.

App Activated and UI Element Found need an observed false condition to re-arm. Image Found and Pixel Found can re-fire after cooldown while still matching. Time uses distinct scheduled occurrences.

Build the script before automating its start