Shared inbox triage in Slack
Each weekday morning, Leta sorts the shared inbox, saves reply drafts in Gmail and posts what needs an answer to your team channel.
Combine Slack + Gmail and move email into channels where your team already talks. Just ask Letaido's AI agent and watch it do the work.
Use this Slack Gmail integration for inbox triage, lead alerts, follow-ups and client updates.
Each weekday morning, Leta sorts the shared inbox, saves reply drafts in Gmail and posts what needs an answer to your team channel.
Every weekday morning, the agent reads the past day's emails asking about pricing or a demo and posts the real leads to #sales.
Each weekday, Leta finds emails you sent that got no reply, saves a follow-up draft in each thread and DMs you the list in Slack.
Tag @Letaido in a Slack thread with an email address; Leta drafts an email from the thread in Gmail and replies when it's saved.
Every Friday, Leta reads the past week's messages in a client's Slack channel and their replies, then saves an update email as a Gmail draft.
Slack's own tools move emails into Slack. Jobs that need judgement sit on top.
| Option | Emails into Slack | Slack to Gmail | Runs on its own | Reasons over the data | Each email as it arrives |
|---|---|---|---|---|---|
| Yes | Yes | Yes | Yes | No | |
| Slack for Gmail add-on | Yes | No | No | No | No |
| Slack channel email address | Yes | No | Yes | No | Partly |
| Slack Workflow Builder | Yes | Yes | Yes | No | Partly |
| Zapier, Make and similar | Yes | Yes | Yes | Partly | Partly |
| Option | What starts it | Best for | Watch out for |
|---|---|---|---|
| Letaido AI agent | A schedule, someone mentioning @Letaido in Slack, or when you ask | Jobs that need judgement: triaging a shared inbox with reply drafts, posting real lead emails to #sales, follow-ups for unanswered emails, emails drafted from a Slack thread or channel | Gmail has no event triggers in Letaido, so emails reach Slack on the job's schedule, not as they arrive. Gmail needs your own Google Cloud OAuth client. These jobs save drafts, they don't send |
| Slack for Gmail add-on | You, from the Slack icon in Gmail's side panel | Sharing one email with a channel or a teammate, with a note and its attachments | One email at a time, by hand. Up to 1 MB of headers and body, 30 MB with attachments, and 20 attachments. A Google Workspace admin may need to approve it |
| Slack channel email address | An email sent or forwarded to the channel's own address, for example by a Gmail filter | Posting every email that matches a filter into a channel or DM | Channel and DM addresses need a paid Slack plan; forwarding to your own Slackbot DM works on all plans. Each email is posted as it is, with no sorting or summary. Slack does not specify delivery timing |
| Slack Workflow Builder | A new Gmail message, or a form someone fills in Slack | Gmail templates such as posting a new Gmail message, or filling out a form in Slack to send a Gmail message | Only on paid Slack plans. Each workflow does one fixed thing. A new Gmail message can start it, but Slack doesn't say how quickly it posts |
| Zapier, Make and similar | A Gmail event such as a new email, a new labeled conversation or a new attachment | Fixed recipes such as sending new Gmail emails as Slack channel messages, DMs for new emails, or a daily email digest with AI steps | You build and fix one workflow per job. Zapier checks Gmail for new mail every 15 minutes on its lowest plan. Adding judgement means extra AI and digest steps |
A job can start when someone mentions @Letaido in Slack, like “Turn a Slack thread into an email draft”.
Saved as an automation, like these jobs: every weekday at 8am, every weekday at 9am or every Friday at 3pm.
Type it once in chat.
Allow all read operations once per app; approve each kind of write once.
Join channel · Unpin message · Get message · Invite to channel
Get message · Send message · Update label · Send draft
Yes. Slack's own Slack for Gmail add-on shares one email at a time with a channel or teammate, and a channel email address posts every email you forward to it. Letaido's AI agent, Leta, adds jobs on top that need judgement, like triaging a shared inbox or posting only the real lead emails to #sales.
Connect Slack and Gmail once in Letaido. Gmail connects with your own Google Cloud OAuth client. Invite the Letaido bot to each channel it should read or post in, then describe the job in chat, or paste a prompt from a job on this page.
No. Gmail has no event triggers in Letaido, so emails reach Slack on the job's schedule, not as they arrive. A job can also start when someone mentions @Letaido in Slack, or when you ask. To post every matching email, forward it to a Slack channel email address.
No. The jobs on this page save drafts in Gmail, such as reply drafts, follow-ups and client updates. You read, edit and send each one yourself.
Yes. Tag @Letaido in the thread with an email address, and Leta reads the thread, saves a Gmail draft to that address with what was agreed and the next steps, and replies in the thread. Mention jobs need the app_mention event switched on in your Slack app.
Yes. Zapier runs a fixed recipe you build, like sending each new Gmail email as a Slack message, and you build and fix one workflow per job. Leta runs a job you describe and can sort emails, skip newsletters and pitches, and draft replies before it posts.
Allow all read operations once per app; approve each kind of write once.
Connect Slack and Gmail, then ask for a job like "Triage our shared inbox every morning and post what needs a reply in Slack". Leta gets it done on your schedule, or the moment you ask.
Get Letaido