Ranksy

Automations for Shopify apps

Every warning sign becomes a task with an owner.

Ranksy rules watch your merchants for the moments that cost revenue: a frozen charge, a trial about to end, a health score falling, a 2★ review. When one happens, the rule opens a task for the right teammate or tags the merchant, and logs exactly why.

Start 7-day free trial

No credit card. Add your app in 2 minutes.

See how it works

Works with Claude, ChatGPT, Cursor and your own agents

app.ranksyapp.com/stockwise/automations

Illustrative · sample data

Automations · Stockwise

New rule
RulesHistory
Rule · triggerOn7d firedOpen
  • Failed chargeLifecycle event · FrozenOn32
  • Trial endingTrial ending · 3 daysOn94
  • Health dropHealth dropped · below 40On22
  • Bad reviewReview posted · 3★ or lessOn11
  • Gone quietGone quiet · 14 daysOn53
  • Save the cancelLifecycle event · ChurnedOff——
  • Near usage capNear usage capOff——
10 ready-made rules, off until you turn them onChecked every minute against your Partner API dataCaps, cooldowns and a log of every run

Trusted by 330 teams431 team apps

4.2M API calls426K MCP callsprocessed in the last 30 days

How it works

Pick a moment. Narrow it down. Decide what happens.

Each rule belongs to one app and has three parts: a trigger, conditions and actions. Ranksy shows how many merchants it matches before you turn it on.

  1. 01

    Choose a trigger

    Pick the moment that matters, such as a frozen charge, a low review, a trial ending or a merchant going quiet. There are seven triggers in all.

  2. 02

    Add conditions

    Narrow it with the same filters as the customer list: plan, MRR, country, Shopify Plus, tags, health, store age and more. A live count shows how many merchants match.

  3. 03

    Set the actions

    Create a task from a template with the merchant's details filled in, add a tag, remove a tag, or do several at once.

  4. 04

    Turn it on and check the log

    Ranksy checks the rule every minute. Every run is logged as fired, skipped or error, with links to the merchant and the task.

One rule, start to finish

A charge fails. Minutes later, Dana has the task.

This is the Failed charge template with one condition added, so it only acts on merchants paying $50 or more.

Illustrative · sample data

  1. When

    Lifecycle event

    Charge frozen

    From the Partner API, synced every 4 minutes

  2. If

    Conditions

    Paid onlyMRR at least $50

    Matches 11 merchants today

  3. Then

    Actions

    Create task

    Payment failed: {shop}, check in

    High · due in 1 day · rule owner

    Add tag

    billing-risk

    Up to 10 actions per rule

Result

app.ranksyapp.com/stockwise/tasks/2841

Payment failed: Saltmarsh Supply, check in

billing-risk
Merchant
Saltmarsh Supply
Priority
High
Due
Oct 15
Assignee
Dana
Source
Rule: Failed charge

Shopify froze the charge for Saltmarsh Supply on Oct 14. Plan: Pro ($149 MRR).

  • Email ops@saltmarsh-supply.com about updating billing
  • Profile: app.ranksyapp.com/stockwise/customers/saltmarsh-supply

Rules create tasks and change tags. To get a message when a merchant installs or uninstalls, use Ranksy's Slack and Google Chat notifications, which are set up separately.

Task templates

Tasks that arrive with the context filled in.

An automatic task is only useful if the person who gets it can act without digging. Write the title and body once with variables like {shop}, {plan}, {mrr} and {health_reason}, and each task fills them in for that merchant, including a link to their record.

  • 15 variables, from {shop_domain} and {trial_ends_at} to {review_rating}
  • Priority, due in N days, and an option to skip weekends
  • Assign to the rule owner, a set teammate, or leave it unassigned
  • Up to 10 actions per rule, including one task
app.ranksyapp.com/stockwise/automations/health-drop/edit

Illustrative · sample data

Create task · Title

{shop} health fell to {health_score}/100 ({health_reason})

Body

{shop} health is {health_score}/100: {health_reason}.

- Check recent usage on their profile: {customer_url}

- Reach out at {email} before they churn

Priority

High

Due in

1 day

Assignee

Rule owner

Skip weekends

Preview · Oak & Ember

Oak & Ember health fell to 37/100 (cancelled, access ending)

Oak & Ember health is 37/100: cancelled, access ending.

- Check recent usage on their profile: app.ranksyapp.com/stockwise/customers/oak-ember

- Reach out at team@oakandember.example before they churn

High · due in 1 day · Dana

Guard rails

Turn a rule on without burying your team.

The worry with any automation is the morning it opens 400 tasks. Ranksy rules have limits built in. A new rule looks back at most 90 days, so old installs don't all fire at once. A merchant who already has an open task from a rule doesn't get a second one. And when a rule hits its daily cap, the rest become one summary task.

  • One open task per rule per merchant; a repeat goes in that task's activity log and can only raise its priority
  • Per-merchant cooldown, 30 days by default
  • At most 10 runs per rule and 25 per app each day
  • Overflow becomes one task: "Rule X matched N more merchants today"
app.ranksyapp.com/stockwise/automations/gone-quiet/edit

Illustrative · sample data

Rule settings · Gone quiet

Cooldown per merchant

Default

30 days

Look back

Up to 90 days

0 days (new events only)
Only merchants with tracked activity

When the daily cap is reached

Gone quiet matched 7 more merchants today

Source: Rule: Gone quiet · Priority: Medium

Run history

Every task can answer "why am I here?"

When a rule creates a task, or decides not to, Ranksy writes it down. The History tab lists every evaluation with its outcome and the reason it was skipped, linked to the merchant and the task. Claude and Cursor can read the same log through the MCP server.

  • Fired, skipped or error, for every run
  • Skip reasons: condition not met, cooldown, duplicate task, daily cap
  • Links to the merchant record and the task it created
  • Fired in the last 7 days and open tasks on every rule
app.ranksyapp.com/stockwise/automations?tab=history

Illustrative · sample data

RulesHistory
  • 09:15Saltmarsh SupplyFailed chargeFiredTask created → Dana
  • 09:15Harbor GoodsFailed chargeSkippedCondition: MRR under $50
  • 03:41Oak & EmberHealth dropFiredTask created → Dana
  • 03:41Northwind SupplyHealth dropSkippedCooldown, 12 days left
  • 03:41Little Fern ToysHealth dropSkippedOpen task already exists
  • Oct 13—Gone quietSkippedDaily cap reached, summary task created

Board triggers

Move a card and let the next step happen.

A rule can start when a task moves between board columns. Drag "Save attempt" to Waiting on merchant and a rule can tag the merchant or open a check-in task. Board rules chain one level deep, and a loop guard stops rules from setting each other off.

  • Trigger on a move from one column to another
  • Tag or untag the merchant when a deal changes stage
  • One level of chaining, with a loop guard
app.ranksyapp.com/stockwise/tasks?view=board

Illustrative · sample data

In progress

Waiting on merchant

Save attempt: Oak & Ember cancelled Growth

High · Dana

RuleTask movedAdd tag: save-in-progress

Ten ready-made rules

Ten common follow-ups, already written.

Each template creates a task and ships switched off. Turn one on, adjust the conditions, and check the match count first.

  • WHEN Health dropped · < 40

    Health drop

    A high-priority task, due next day, when an installed store's health falls below 40.

  • WHEN Lifecycle · Frozen

    Failed charge

    Follow up with a paying merchant after Shopify freezes their charge.

  • WHEN Trial ending · 3 days

    Trial ending

    Nudge active stores three days before their trial ends.

  • WHEN Lifecycle · Uninstalled

    Early uninstall

    Ask new merchants who uninstall what was missing.

  • WHEN Lifecycle · Churned

    Save the cancel

    A save task when an active customer cancels their plan.

  • WHEN Review · ≤ 3★

    Bad review

    Reply and reach out when a linked review is 3★ or lower.

  • WHEN Lifecycle · Downgraded

    Downgrade

    Find out why a merchant moved to a cheaper plan.

  • WHEN Lifecycle · Installed

    High-value install

    Welcome each new install. Add plan or Shopify Plus filters to keep only the big ones.

  • WHEN Near usage cap

    Near usage cap

    An upsell task when a store gets close to its usage cap.

  • WHEN Gone quiet · 14 days

    Gone quiet

    Check in with paying stores that haven't opened your app in 14 days.

Spec sheet

Every trigger, condition and action.

Triggers (7)

Lifecycle event
Any of 15 events: installed, reinstalled, trial started, free plan selected, subscribed, trial converted, trial cancelled, upgraded, downgraded, frozen, unfrozen, churned, uninstalled, shop closed, shop reopened. You set which events.
Review posted
A review linked to a merchant is at or below a rating. You set the star threshold.
Near usage cap
A merchant approaches their usage-billing cap.
Trial ending
A trial ends in a set number of days. You set the days before.
Health dropped
The health score crosses below a threshold; re-arms once it recovers 5 points above it. You set the threshold.
Gone quiet
No app open for a set number of days. You set the days.
Task moved
A task moves between two board columns. You set the from and to columns.

Actions (3)

Create task
Title and body template with variables; priority; due in N days; skip weekends; assign to rule owner, a teammate, or nobody. Max one per rule.
Add tag
Any of the app's tags
Remove tag
Any of the app's tags
Per rule
Up to 10 actions

Conditions

Any customer-list filter
Search, install status, plan (current or ever), traffic source, other apps installed, review status and rating, revenue range, install date range, access ending, test stores, paid only or paid for N months, last seen, tasks (open, overdue, none), health range, tags, plans, countries, Shopify Plus, dev store, store age.

Variables (15)

In task titles and bodies
{shop}{shop_domain}{email}{country}{shopify_plan}{plan}{mrr}{installed_at}{trial_ends_at}{health_score}{health_reason}{event_date}{review_rating}{customer_url}{rule_name}

Limits and timing

Evaluation
Every minute (health-drop rules effectively daily, since scores update nightly)
Runs
Max 10 fired per rule and 25 per app per day; overflow becomes one summary task
Duplicates
One open task per rule per merchant
Cooldown
Per merchant, 30 days by default
Look-back
Up to 90 days when a rule is turned on
Scope
One app per rule

API and data

API
Read rules and run history over MCP (rules-list, rule-runs-list) and REST. Rules are edited in Ranksy.
Data needed
Partner API for lifecycle, trial, billing and cap triggers. Your app's identify/track calls for Gone quiet and the activity parts of Health dropped.

MCP server

Ask Claude why a task exists.

The MCP server can read your rules and their run history, so Claude or Cursor can explain any automatic task, or why a merchant was skipped. See the MCP server.

Add Ranksy to Claude

Claude · via Ranksy MCP

Why did Ranksy open a task for Oak & Ember this morning, and who else did that rule skip?

rule-runs-list { app_slug: "stockwise", rule_id: 14 }

  • Oak & Emberfired · task → Dana
  • Northwind Supplyskipped · cooldown
  • Little Fern Toysskipped · open task

The Health drop rule fired at 03:41, after Oak & Ember's score fell from 67 to 37 when they cancelled Growth. Northwind Supply matched too, but they're in a 30-day cooldown, and Little Fern Toys already has an open task from this rule.

Questions

What people ask first.

Can a rule send an email or a Slack message?

No. A rule's actions are create a task, add a tag and remove a tag. The task's assignee is notified in Ranksy and gets a due reminder by email. Install, uninstall and performance alerts to Slack or Google Chat are set up separately under notifications, not as rules.

Will turning on a rule flood us with tasks for old merchants?

No. A rule looks back at most 90 days when you turn it on, and the templates start with no look-back at all. Each rule fires at most 10 times a day and each app 25 times; anything over that becomes one summary task. A merchant gets one open task per rule, with a 30-day cooldown by default.

How is this different from an install or uninstall alert?

An alert tells you something happened. A rule decides whether it matters and who handles it. Rules run on Ranksy's merchant records, so a condition can check health score, MRR, tags, review rating, Shopify Plus, store age or open tasks before acting. The result is a task on that merchant's record with an owner and a due date, and every run is logged with the reason it fired or was skipped.

How often do rules run?

Every minute. Partner API data syncs every 4 minutes, so a frozen charge or uninstall usually becomes a task within minutes. Health-drop rules effectively run once a day, because health scores are recalculated nightly.

Can Claude or the API create or edit rules?

They can read them. The MCP server and REST API list rules and their run history, so an assistant can explain why a task exists. Creating and editing rules happens in Ranksy.

Which plans include automations?

Both. Starter ($39/month, 3 apps) and Studio ($89/month, 10 apps) include automations, tasks and the CRM, with rules set per app. Rules run on Partner API data, so connect it first. The 7-day free trial needs no credit card.

Keep reading

Where to go next.

Catch the next frozen charge while it's still a task.

Connect the Partner API, turn on the templates that fit your app, and check the match count before the first rule runs.

Start 7-day free trial

No credit card. Add your app in 2 minutes.

Works with Claude, ChatGPT, Cursor and your own agents