Pick a site. Say what you want. It keeps doing it.
Not in the app yet. It will learn the site once, then run your job on a schedule or when something changes. Today, on a Mac, you start each task yourself from the pill or the orb, and it does it with its own cursor.
- Drafted Maya Chen a reply, your template
- Drafted Sam Ortiz a reply, your template
- Left Jordan Lee for you, not a recruiter
Two replies are drafted in LinkedIn. Jordan's message is left for you.
Any site, learned once
Pick a site and say what you want. It turns the site's own buttons and forms into an API, then reuses it every run.
LinkedInReply to recruiters with my templateon a change
AmazonBuy these headphones under $250on a change
ShopifyPut new orders on my packing sheeton a change
TypeformAdd new sign-ups to HubSpoton a change
ClassroomEvery Sunday, put what's due in my calendaron a schedule
Every automation knows when to run
On a schedule, or the moment something changes on the site: a new message, a price drop, a new order, a form.
- Weekly sales reportMondays at 9:00run started
Recruiter repliesWhen a new message arrivesnew message
Headphones under $250When the price dropsprice drop
Packing sheetWhen a new order comes innew order
Runs on its own, while you do something else
Each run calls the actions it learned for that site, so it's quick. What should wait for you goes in what you ask: “draft the reply”, “put it in my cart”.
Learns the site once
It turns the site's own buttons and forms into actions, then reuses them on every run.
On a schedule or a change
Mondays at 9, or the moment a new message, an order or a price drop shows up.
Every run in its history
What each run did and when, with a check, so you can see it kept at it.
A message arrives. The reply is ready before you look.
Once it's in the app, your automation wakes on the new message and drafts the reply in one call, ready for you to read.
- 10:47:02
A message arrives
A recruiter writes to you on LinkedIn. Your automation wakes up.
always on · new message
- 10:47:03
calls its learned API1 calldraftReply(thread, intro)- getThread(id)her message, read
- fillTemplate(intro)your template, her name
- draftReply(thread, text)draft saved, not sent
1 callNo clickingNot sentIt calls the site's API
One call reads the thread and drafts the reply from your template.
learned once · 1 call
- 10:47:04
It leaves the draft for you
You asked for drafts, so the reply waits in LinkedIn for you to read.
in LinkedIn · a draft, as asked
- 10:47:31
run history3 runsRecruiter replieslinkedin.com · always onDone
- 10:47
- Replied to Maya Chen
- 09:12
- Replied to Sam Ortiz
- Mon
- Left Jordan Lee for you
The run is in its history
You read it and pressed Send. The run lands in its history with a check.
run history · always on
Pick a site, let it keep at it
Always on is not in the app yet. Try what it does today for 10 minutes, no card.
Do anything
Ask it a question or hand it a job, in any app.
Doing jobs for you is in the Mac app. Asking works on Mac, Windows and Linux.