Gmail

Gmail is a connector: it links a MeDo app to one Gmail account, so the app can search and read conversations, send plain-text email, and move messages between existing labels. Everything the app sees comes from the account you connected.

#What you can build

• A customer follow-up workspace. Find conversations by customer address, keyword, date, or unread status, open the full conversation, and keep follow-up notes and status in the app.
• A project communication page. Pull the conversations that match a project keyword or date window and show them next to the project's own context.
• An inquiry tracker. Save selected incoming messages as inquiries, track open or resolved status, and jump back to the original conversation.
• A review-before-send tool. Compose a plain-text message, preview the recipient, subject, and body, then send only after someone confirms.

Gmail fits when the app needs to work with a real mailbox: support inboxes, sales follow-up, project correspondence. It is not a mail server, and it cannot run an app that sends bulk campaigns — see Limits.

#Build examples

Copy one of these into the prompt box. The first one is the smallest useful starting point.

Use @Gmail to build a private customer follow-up workspace where I can find conversations by customer email address, filter unread messages, and open the full conversation.

Use @Gmail to build a private project communication page with a project keyword and date filter, related email conversations, and project notes saved in the app.

Use @Gmail to build a private customer follow-up tool where I can compose a message, preview the recipient, subject, and email, then confirm before sending.

Use @Gmail to build a private inquiry tracker where I can select incoming emails, save them as inquiries in the app, track open or resolved status, and open the original conversation.

The wording matters: say who the tool is for and what it should do. "A private follow-up workspace for the support team" produces a different app from "a page that lists emails".

#Prepare and connect

You need a Google account with access to the mailbox the app should use. No API key, no Google Cloud project, and no billing setup are involved.

1. Open Skills & Connectors in the sidebar and search for Gmail.
2. Open the Gmail card and click Connect.
3. Sign in to the Google account and approve the access MeDo asks for.
4. The button changes to Connected. That is the success state; you do not need to copy anything back into the app.

If you start building before connecting, MeDo notices and shows a Gmail connection button under its reply. You can connect there instead. If no button appears, use the connector card described above.

#Use it in your app

• The app uses your connected mailbox, not each visitor's own Gmail account. Every visitor who reaches a mailbox view sees the same mailbox. Keep mailbox pages, search, and sending behind your app's own sign-in, and restrict them to the people who should have that access. A page titled "private" is not access control on its own.
• Choose the mailbox scope in the prompt. Naming a customer address, a project keyword, a label, or a date window keeps results relevant and reviewable.
• Mail is read when the app loads or refreshes. There is no background sync and no new-mail trigger, so plan an explicit refresh control instead of expecting live updates.
• Sending and label changes are confirmed first. MeDo previews the recipient, subject, and body before a send, and the target message and label change before a label update.
• App-owned data stays in the app. Inquiry status, internal notes, and follow-up dates belong in your app's own tables, keyed to the real message or thread. They are not Gmail fields.

#Limits and troubleshooting

"Connection required" appears in the app. The Gmail connection belongs to the app owner. Ask the owner to open the connector card and click Connect, then reload.

A send seems to have failed but nothing is in Sent. MeDo does not retry a send automatically, because a retry can deliver the same message twice. Check the Sent folder before sending again.

Search returns fewer messages than expected. Search covers the mailbox scope and the limits described above, and spam and trash are excluded. Widen the date window or use a label rather than assuming messages are missing.

Visitors can see the mailbox when they should not. The connection is shared. Add sign-in and server-side restrictions to the app; see Managing access & roles.

#Related

• Connector catalog — the other connectors and what they are for.
• Skills & Connectors — how Skills are called, priced, and limited.
• Managing sign-in & users — give an app its own accounts before exposing connected data.