DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to approve each sales email before it leaves with Dontbemichael

Have a Sales Director draft outreach and send only the emails you approve on Needs you.

Credentials. The sales mailbox login is stored encrypted on your computer, so keep the app password limited to sending mail for this mailbox.

Who it is forA business owner who wants AI to write sales or follow-up emails but must review every message before it goes to a customer.

The problemSending AI-written email without review risks wrong prices, wrong promises or messages the owner never wanted sent.

The outcomeEach outgoing email appears on Needs you, where you can edit, approve, ask for changes or stop it, and the team member learns from your edits.

What you need first

  • A Mac or Windows computer
  • A Claude plan you already have, or an Anthropic API key
  • Your business name, kind of business, owner name and headquarters address
  • An app password for each mailbox you want the team to use

Steps

  1. Connect the sales mailbox in Settings, Connections, Mailboxes with its app password.
  2. Open the Sales Director team member's Access tab and add the mailbox with Watch the inbox.
  3. Set the sending choice to Send on approval for that mailbox.
  4. Open Needs you when an email appears, then edit, approve, ask for changes or stop it.
  5. Check the mailbox's Sent folder in your own app to confirm only approved emails went out.

Prompt for your agent

Using the repo agentvivekkumar/dontbemichael, set the sales mailbox <sales mailbox address> to Send on approval for the Sales Director team member. Report the number of drafts waiting on Needs you. Verify that no email leaves until you approve it on Needs you.

Caveat. The README describes a one-time approval option for a kind of email, so check the Sends without asking list on the Access tab before you trust any repeated message type.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page