Launched on Launchit

Integrations

An assistant is only as good as what it can see. Mailient connects to the places your work actually happens, so a decision it makes about your inbox is informed by your calendar, your docs and your team.

Gmail is required — it is the job. Everything else is optional context you can add when it earns its place.

You only need Gmail to start

Connect the inbox, see real drafts to your real threads, and add the rest when you want Mailient to know more. By default nothing sends without your approval, and you can revoke any connection from the service that granted it.

Common questions

Which of these do I actually have to connect?
Gmail, and nothing else. Gmail is the job — without it there is no inbox to work on. Google Calendar, Notion, Slack and Cal.com are optional context you add when you want Mailient to know more, and you can start with none of them.
Does connecting more things mean Mailient acts more on its own?
No. Approval is the default no matter how many things are connected. Connections change what Mailient can see when it decides something, not what it can do without asking you. Autonomous sending exists as a switch you turn on deliberately for one specific background agent, and it is off until you do.
How do these connections actually work?
Gmail, Google Calendar, Notion and Slack use standard OAuth, so you approve the access on a consent screen owned by that service and never give Mailient a password. Cal.com is the exception: it connects with an API key you generate in your Cal.com settings and paste into Mailient, so there is no consent screen for that one.
How do I disconnect something later?
From your Mailient settings, or from the service that granted the access — a Google connection can be revoked from your Google account at any time, and a Cal.com connection is revoked by deleting the API key. Revoking takes effect immediately and does not need to go through us.