Work that should happen even if you forget
Some work should not wait for you to open a page. A weekly digest. A morning pass over open tickets. A script that prepares tomorrow’s jobs. A wake-up for the assistant so it does a job you already described.
Thogits automations are schedule-based. You set when they run. They run.
You set the clock. They hit the same database your pages already show — a morning pass, a weekly chase, a script that prepares tomorrow.
What you can schedule
On a timetable you control, an automation can:
- Fire a reminder
- Wake an agent to do a job (read records, update them, email, or call)
- Run a script against the space
Examples that match how operations and small teams actually work:
- Every weekday at 8:00, wake the assistant to list overdue invoices
- Every Sunday night, prepare next week’s job board
- Once a day, remind the owner of any ticket still open past SLA
- Monthly, run a script that archives completed work you no longer need on the main page
The records stay the system of record. The automation is the clock.
Agents on a clock
The useful combination is schedule plus assistant. You do not have to sit in chat and remember to ask.
Describe the job once. Point it at the types you care about. Put it on a schedule. The assistant works the same records your pages show — lists, boards, dashboards — and the same records you see on web and iPhone.
Phone here means calls. Email is email. Chat is in the product. The scheduled run can use the assistant the same way you would.
External agents on MCP can see and edit records, but MCP does not run automations. Scheduled work is in Thogits. If you want your own agent in the loop, use the API or keep MCP for the data plane and let Thogits own the clock.
What we do not claim
No “when this record changes” triggers
No record-change triggers. No “when status becomes Done, notify Slack” engine as the product. You can still integrate other tools with credentials and OAuth, and you can still write against the API. The automation primitive in Thogits is the schedule.
That keeps the model small enough to trust. A founder can read the list of scheduled jobs and know what will fire. A shared space does not hide a web of if-then rules nobody remembers.
How this sits next to reminders
Reminders are one-shot (or simple) pings on a record. Automations are the repeating, scheduled layer.
- Reminder: “Ping me about this quote on Thursday.”
- Automation: “Every Monday, wake the assistant to chase quotes older than seven days.”
Both attach to the same workspace. Neither replaces the database. If you start from a template, you still add the schedule that matches your week, not someone else’s.
You are not bolting a third-party zap onto a table in a doc. You are scheduling work in the same workspace that holds the records and the pages.
Try it
Put one real job on a schedule — a morning pass, a weekly reminder, a script — and see it hit the same records as your pages. Full Features, pricing, or sign up and give the clock a task.