Meet tiq: Scheduled Automation for Salesforce, Made Calm
tiq is the clean-break successor to Mass Action Scheduler: pick a source, an action, and a schedule, then trust it runs. Launching July 13 as an unlocked package and fully open source.
Every org has a few of these. Email the owner of every opportunity that's gone quiet for 30 days.Re-run a flow over yesterday's failed records.Recalculate a field on ten thousand accounts, every Sunday at 2 a.m., forever. The logic is simple. The records are known. The schedule is obvious.
And yet the tooling to actually run it has always felt like plumbing. You wire up a scheduled Apex class, or you lean on an aging package whose UI predates Lightning, and you cross your fingers that the batch finished, because finding out what happened means reading a debug log.
There's a new tool for exactly this job. It's called tiq, it's Salesforce-native, and its whole personality is the opposite of cross-your-fingers. It launches July 13, 2026 as an unlocked package and fully open source, and it's built for the same people, doing the same work, who read this site.
Steps to a job
3
Run states, color-coded
5
Lines of Apex required
0
Target launch
Jul 13
Built on Mass Action Scheduler
A Clean Break from Mass Action Scheduler
If you've run bulk scheduled automation on Salesforce, you know Mass Action Scheduler. tiq keeps the engine idea that worked and rebuilds everything around it.
tiq's execution model is a clean-break rewrite derived from Doug Ayers' Mass Action Scheduler: the proven Source, Action, Schedule loop, brought forward. Three decisions shaped what changed.
01
Feature 01
Rebuilt on React, not bolted onto Lightning
A modern client on Salesforce's current APIs, not another Aura or Visualforce relic.
The engine was always the good part of Mass Action Scheduler. The UI was the part people apologized for: it predated Lightning and showed it. tiq is a React and shadcn/ui client talking to Salesforce's current data APIs, with no Aura, no Visualforce, and no iframes. That foundation is what makes the calm, fast, legible screens in the rest of this post possible. We kept the engine's ideas and threw the old UI out.
02
Feature 02
Focused by subtraction
Fewer source and target types, chosen on purpose.
A clean break means dropping things. Gone: Workflow, Process Builder, Quick Action, and Email Alert targets; Apex Iterable sources; and the everything-on-one-wall-of-fields config screen. What's left is the path that held up in production: a report, list view, or SOQL source, running a Flow or invocable Apex action. Less surface area means less to get wrong, and every screen gets to stay calm.
03
Feature 03
Static values and a real run-as account
The two additions that change how jobs get built and secured.
Two things Mass Action Scheduler users kept asking for. First, static-value field mappings: map an action input to a source field or to a fixed value, with no formula gymnastics. Second, a real run-as service account, a Named Credential with its own scoped identity, instead of borrowing the scheduling user's session. Jobs run as a known principal, and an audit can see exactly who touched the records.
The point isn't nostalgia. It's the same dependable idea, rebuilt to feel like 2026: approachable, trustworthy, precise.
How a job works
Source, Action, Schedule
tiq organizes everything around the job to be done, not the API behind it. A job is a short, honest sequence, revealed one decision at a time.
A tiq job is three answers. You give them in order, and the tool only asks for the next thing once you've committed to the last: progressive disclosure instead of a wall of fields.
1
Source: which records?
Point tiq at a report, a list view, or a SOQL query. That's your target set. No source set means nothing runs, and tiq tells you the count before you go further.
2
Action: what should happen to them?
Run a Flow or an invocable Apex action against every record in the set. Map source fields (or static values) to the action's inputs. The same automation you already build in Flow Builder, now pointed at a batch.
3
Schedule: when, and how often?
Run it on demand, or on an hourly / daily / weekly / monthly cadence (cron when you need it). Set it once; tiq carries it.
Reading a run at a glance
The Calm Control Room
tiq runs actions across thousands of records, unattended. The entire design exists to make that feel safe: legible at a glance, never a surprise.
The heart of tiq's design is its run-state palette. Most of the screen stays cool and quiet so the signal carries; saturated color is spent only on what a job is actually doing. At any moment you can read what's scheduled, what's running, what succeeded, and what needs you, without hunting.
That's the trust contract: consequences are legible. Before a job commits, tiq shows you the record count and what it's about to do. Preview, then confirm. The power is never hidden, but it's never a surprise either.
Roadmap
Where tiq Is Right Now
tiq is in active development and on track to launch July 13, 2026. Here's the road there, and what lands on day one: an unlocked package and open source.
tiq roadmap Calendar · Live
↑ Today
Mar1
2026Past
Planning & design
Product direction, data model, and the full design system: locked.
May15
2026Now
Foundation
The walking skeleton: a themed React app on Salesforce, the actions list, and the engine port underway. We are here.
Jun22
2026Upcoming
Configuration wizard
The guided create-and-edit flow: source, action, field mapping, and schedule, one step at a time.
Jul4
2026Upcoming
Scheduling & monitoring
The cron write-path and near-real-time run status, logs, and dashboards.
Jul13
2026Upcoming
Launch: unlocked package + open source
tiq ships as an unlocked package with a one-click install link, and the full source goes public on GitHub.
Mar1
2026Past
Planning & design
Product direction, data model, and the full design system: locked.
May15
2026Now
Foundation
The walking skeleton: a themed React app on Salesforce, the actions list, and the engine port underway. We are here.
Jun22
2026Upcoming
Configuration wizard
The guided create-and-edit flow: source, action, field mapping, and schedule, one step at a time.
Jul4
2026Upcoming
Scheduling & monitoring
The cron write-path and near-real-time run status, logs, and dashboards.
Jul13
2026Upcoming
Launch: unlocked package + open source
tiq ships as an unlocked package with a one-click install link, and the full source goes public on GitHub.
Why announce before launch?
Because the best tools earn their audience before launch, not after. If scheduled bulk automation is part of your job, tiq is being built for you. Watch this space between now and July 13, and bring your feedback when the source goes public.
Coming July 13
Watch This Space
tiq launches on July 13, 2026 as an unlocked package and fully open source: a calmer, clearer way to run scheduled automation across your records, built by people who care about the same things this site does: clarity, trust, and not shipping bad automation.
Want the fuller pitch and a first look at the brand? Visit the tiq teaser page →, and keep an eye on Professor Flow for the launch.
