Glento on Zapier: The Beta Is Open
When we opened up the Glento API, we said a no-code connector was in review and that we would post the day it landed.
It has landed, in beta. Glento is now on Zapier, by invite, while the public listing finishes review.
What it does
- Two triggers: a task was created or updated, and a task was deleted.
- Four actions: create, update, complete and delete a task.
- A search, to find an existing task before you act on it.
- Included with Pro. No separate plan, no per-Zap pricing.
Zapier reads and writes the synced copy of your tasks, and syncing is what Pro pays for. Keep Glento free and your tasks never leave your device, which is the default we chose on purpose. What you get on each plan has the breakdown.
What people wire up
The point of an integration is not the integration. It is the five minutes a day you stop losing to copying things between windows.
Email that turns into a task. Star a message, and it lands in Do First with the subject as the title and the body in the notes.
Form responses that become work. A client request form arrives as a Schedule task with a due date and a tag, instead of as another notification you will read twice.
Finished work that announces itself. Completing a task posts to your team channel, so nobody has to ask where things stand.
The weekly admin you keep re-adding. A scheduled trigger files the recurring chores before the week starts, so your Monday matrix is already sorted when you open it.
Why this is a beta
Everything above works. We have used all of it. The beta is not about the code.
Zapier will not list an app publicly until a few people are running real Zaps with it, which is a sensible rule and one we are a couple of users short of. So the integration is open by invite in the meantime, and if you build something with it you are the reason the public listing happens.
That is the whole ask. There is no waitlist and nothing to fill in.
Joining takes about a minute
- Open the invite link on the integrations page while signed in to Zapier. Glento appears in your apps.
- Add Glento to a Zap, as the trigger or as an action, and click Connect.
- Sign in and approve. You see exactly what is being asked for before anything is granted.
There are no API keys to copy and no password to hand to anyone. The connection keeps itself alive, and it stops the moment you remove it in Zapier.
Two things to know
Due dates are days, and days need a timezone. When a Zap sets a due date or a start date, Glento needs to know which timezone that day belongs to, so your task lands on the day you meant rather than the day a server happened to be having. The field is right there in the action.
Repeating tasks are handled carefully. A Zap can read and edit a repeating task like any other, but it will not change the repeat itself or complete a task that belongs to a series. A half-applied change to a recurring series is worse than one you make in the app yourself.
The AI assistant connection is live
This is the other half, and it is not a beta. Glento now speaks MCP, so you can connect Claude, Cursor, ChatGPT, OpenClaw, Hermes Agent or anything else that speaks it, and ask what is urgent without leaving the conversation. Included with Pro too.
If something breaks
Tell us. Write in with what you were building and what it did instead. A beta is worth running only if the reports come back, and the list of what gets built next is mostly written by people who wrote in.
