Email from your own mailbox
Connect your own mailboxes, at Gmail or Google Workspace, Outlook or Microsoft 365, or any other provider, and Hermoso sends one-to-one email from them: a single message, or a sequence of timed follow-ups to people on your lead list. The mailbox, the lead list and every sequence are kept on the brand, so Claude, ChatGPT, Cursor, a teammate and the web app all pick up the same sequences with nothing to set up again. This is email between you and one person at a time. For newsletters and campaigns to a whole list, use the Klaviyo or Mailchimp connection.
Connect a mailbox
In the app, open Automations, Email and add a mailbox, or open Connectors and choose Gmail, Outlook or Any mailbox: all three open the same dialog. Type the email address: Hermoso works out the provider and its servers from it, so in most cases only the password is left. Most providers want an app password, and the dialog gives your provider's steps and the page where it makes one. Each way of connecting says what it does: an app password, or the mailbox's own password, sends email and shows replies in your Inbox. The server names, ports and security are filled in under Server settings, where you can still change them; when Hermoso cannot work them out, that section opens with the standard ports for you to fill in. Hermoso signs in to sending and to incoming mail before it saves anything, sends nothing while it checks, and says which of the two failed and why: a wrong password, an app password needed, sign-in not allowed for the account, or a server that cannot be reached.
The settings come from, in order: the address's own domain (Google, Outlook, Yahoo, iCloud, Zoho, Fastmail, GMX, AOL and others), the domain's mail servers (Google Workspace, Microsoft 365, Zoho, Fastmail, Namecheap Private Email, GoDaddy, Titan, IONOS, Rackspace, Hostinger, OVHcloud, Migadu, Purelymail, mailbox.org and others), the settings the domain publishes for mail apps, its DNS service records, and last a test connection to its usual server names, which is offered only once the server has answered. No password is sent while it looks. An agent asks the same question with detect_mailbox_settings and connects with connect_connector (provider smtp) and just the address and password.
Gmail and Google Workspace connect with an app password, which sends email and shows replies in your Inbox:
- Turn on 2-Step Verification in your Google Account.
- Open App passwords and create one named Hermoso.
- Paste the 16-character password into the dialog.
An agent connects one with connect_connector (provider gmail) and the address and app password. Google's guide to app passwords has more.
Outlook and Microsoft 365 connect with a Microsoft sign-in instead (the dialog offers it as soon as it sees a Microsoft address). It sends email and shows replies in your Inbox. Microsoft does not accept an app password from other apps. An outlook.com address and a work or school address both work.
A brand can hold several mailboxes. Hermoso reads only the threads it started, never the rest of the inbox, and opens folders read only: it never marks, moves or deletes your mail. list_email_mailboxes shows every connected address, whether it sends and receives or sends only, what it sent in the last 24 hours against its daily ceiling, and the links to connect another.
How many emails go out a day
You set the pace on the sequence: Send up to N emails a day (dailyCap on save_email_sequence, 50 unless you change it, 1 to 2,000), across the mailboxes the sequence uses. Start slow and build up is optional and off unless you turn it on: with ramp (start, days) the sequence sends start emails on its first day and a little more each day until it reaches its pace. Both can be changed at any time, in the app or by an agent, and enroll_email_leads takes them too.
Each mailbox also has one daily ceiling across every sequence and every one-off email sent from it. It starts from what the mailbox's provider allows in a day (500 for Gmail, 2,000 for Google Workspace, 1,000 for iCloud Mail, 200 where the provider publishes no number), so it normally needs no change. set_email_mailbox changes it: up to 2,000 for a mailbox connected with an app password or its own server details, and up to 400 for one connected with a Google or Microsoft sign-in. In the app it is under the mailbox's Settings, Advanced.
What goes out today is the smaller of the two, and the sequence says so in one line when that is less than you asked, for example 40 of 50 today: ann@acme.com has reached its daily ceiling. Only real emails count: Hermoso never sends practice mail between mailboxes.
Automatic pauses
A mailbox, and the sequence the trouble came from, pauses on its own when:
- 2.5% of its emails over the last 7 days bounced (once 25 have gone out), or 3 bounced among its first 25;
- the mail server refused 10% of its sends (once 10 were tried);
- a recipient reported an email as spam, the provider answered that sending is blocked or suspended, or the server refused the sign-in. These pause it at once.
For a mailbox you connected with its own server details, the bounce pause can be switched off in its settings (Pause this mailbox automatically when too many emails bounce, or autoPauseBounces: false on set_email_mailbox); Hermoso records who switched it off and when. A mailbox connected with a Google or Microsoft sign-in always pauses for bounces. The other pauses stay on for every mailbox.
The reason is shown in words on the mailbox and the sequence, and an email.paused alert goes to your alert channels. Resume it with set_email_mailbox (status active) or set_email_sequence_status. A mailbox paused for a refused sign-in is checked again before it may send.
list_email_mailboxes shows every connected address, how many emails it sent in the last 24 hours, and the link to connect another.
Send one email
send_email sends a single message: to, optional cc and bcc, subject and body. The body is plain text or simple markdown (paragraphs, bold, links, bullets) and goes out as you wrote it. Pass html instead of body for rich text: paragraphs, bold, italic, links and bulleted or numbered lists are kept, everything else is removed, and the email carries a plain-text copy of the same words. In the app, every email body is written in a box with those same buttons. Hermoso adds no tracking pixel and never rewrites a link.
- Attachments are links to files, up to 10 and 25 MB in total. For a file on your computer,
upload_filereturns a link you can pass. - Replying in a thread: pass
replyTowith the id of an email Hermoso sent, or of a reply fromlist_email_replies, and leave the subject out. Hermoso continues only threads it started. - Several mailboxes: say which one sends with
mailbox. - Limits: 500 recipients on one message, and a subject of at most 255 characters. A message over a limit is refused with the limit, never shortened.
The answer carries the ids your mailbox stored for the message, so it can be found and answered later.
The lead list
Each brand has one list of people to email: address, name, company and any extra columns you add.
add_email_leadsadds people from rows you pass, or from a Google Sheet whose first row names the columns. An address is only ever on the list once.list_email_leadsshows the list, each person's status and where they are in each sequence.update_email_leadchanges a person's details or status, andremove_email_leadstakes people off the list.
A lead marked unsubscribed, bounced or do_not_contact is never emailed again, by a sequence or by send_email, and adding the same address again does not undo that.
Find leads from buying signals
find_leads looks for companies and people showing a reason to buy now. It is a single search you ask for: it runs a handful of public lookups, returns what it found and keeps nothing afterwards. Nothing runs on a schedule.
- What it looks for: companies that just started advertising on Facebook or Instagram (new_ads_meta) or are running LinkedIn ads on a topic (new_ads_linkedin), people asking for a product like yours or complaining about a competitor on Reddit and Threads (posts_reddit, posts_threads), recent TikTok and YouTube posts on a topic (posts_tiktok, posts_youtube), companies hiring for a role (hiring), companies that announced funding (funding), and any web search of your own (web).
- What you pass:
description(who you sell to, in plain words), orkeywordsandcompetitors, orsignalswith a type and any query of your own.country,days(how recent, 30 by default) andlimitnarrow it. - What comes back: one row per company, most recent first, each with the public post, ad or page that is the signal, its link, its date and why it matched.
find_leadswithsearchIdandidreturns one row in full for the next 30 minutes. - What it costs: about 1 credit per lookup, at most 8 lookups a search.
maxCredits(10 by default) is a hard budget: the search stops before passing it, returns what it found and names the lookups it did not run.dryRunreturns the price and the plan with nothing run. - A lookup that fails is reported as "could not read" with the reason. It is never shown as "no leads".
find_company_contacts then reads the public business address from each company's own website: its homepage and its contact and about pages. It returns the addresses the company publishes for contact (email links, and role addresses such as hello@, sales@ or press@), each with its role, the page it was found on and the date. A page that says "no solicitation" is flagged and that company is left out. It never guesses an address, never tests a mail server and never looks people up on LinkedIn. It costs no credits.
Its leadRows go straight into add_email_leads, and the addresses into enroll_email_leads. Both still need listConfirmed: true. Only email an address that is openly published as a business contact, on a page with no "no solicitation" note, with a message relevant to that role.
Sequences
A sequence is a first email and its follow-ups. save_email_sequence creates or edits one:
- Steps: up to 10. The first has a subject and a body. Each follow-up has
waitDays(whole days after the step before it) and a body. A follow-up with no subject is sent as a reply in the same thread. - Merge fields: write
{{first_name}},{{company}}or any column of your lead list where it should appear. A lead with nothing in a column a step uses is held and told to you. It is never sent a half-filled email. - Sending window: the days and hours it may send, in the time zone you give (Monday to Friday, 09:00 to 17:00 unless you change it).
- Several mailboxes: pass
mailboxesand they take turns, the one with the most of its day left going next. A person always hears from the mailbox that wrote to them first, and every follow-up stays in that thread. - Each lead's own time zone: with
leadTimeZoneon, the hours are read in each lead'stimeZonewhen they have one. - Emails a day:
dailyCap, the most the sequence sends in 24 hours across its mailboxes, from 1 to 2,000 (50 unless you change it), with an optional slow start (ramp). See How many emails go out a day. - A/B versions: a step may carry up to three other versions (
variants). Each person always gets the same one, andlist_email_sequenceswith an id shows sends and replies per version. - Review before sending: with
reviewon, every email waits as a draft.list_email_draftsshows the exact words;review_email_draftsapproves each (with your edits, if any), skips that one email so the person carries on with the rest of the sequence, or removes the person from the sequence. - When someone replies: a reply always stops the sequence for that person. With
onReplyit also moves them into another sequence, from the same mailbox, optionally only when the reply mentions words you choose. - The end of every email: one line telling the reader how to opt out (you can reword it), then your name and postal address and an unsubscribe link, which cannot be removed. Set the name and address with
set_email_sender; no sequence starts without them.
enroll_email_leads puts people into a sequence, which is what starts the emails. set_email_sequence_status pauses and resumes it, stop_email_lead ends it for one person, and delete_email_sequence removes it. list_email_sequences shows who is at which step, who replied, who bounced, and what goes out next and when. run_email_sequences runs everything that is due right away.
A step is never sent twice, and nothing is sent to a person after they reply.
Replies, bounces and complaints
Hermoso reads the answers to what it sent, in the inbox and the junk folder. A reply stops that person's sequences and marks them replied. A reply asking to be left alone marks them unsubscribed. A message that could not be delivered marks the address bounced, and a spam complaint unsubscribes the person and pauses the mailbox. An automatic out-of-office reply is recorded and changes nothing. Email replies also show in the Inbox, with the mailbox that received each one, and you can answer there in the same thread.
list_email_replieslists the replies and bounces with their text.get_email_conversationreads one thread in order: what was sent and what came back.
Hermoso reads only the threads it started, never the rest of the inbox.
Opting out and the do-not-email lists
The unsubscribe link in every sequence email takes a person off at once. Where the mailbox allows it, the email also carries the one-click unsubscribe that large mail providers show beside the sender. When someone replies that they want no more email, they are taken off every sequence automatically, and you can do it yourself with stop_email_lead (reason unsubscribed).
Every unsubscribe, spam complaint and bounce goes on your account's do-not-email list, so no brand on the account writes to that address again. manage_email_suppressions lists the lists and adds addresses or whole domains (@example.com) to the account's or the brand's list. An entry the person made, or a bounce, cannot be removed there.
Bought or rented lists are not allowed. Adding more than one address at once, and enrolling people in a sequence, asks you to confirm that the addresses were not bought or rented and that each person either asked to hear from you, or has a business email address published openly with no "no solicitation" note and your message is relevant to their role. In the app it is a tick box; an agent passes listConfirmed: true. Hermoso records who confirmed and when.
Each lead can record why you may email them (basis: a customer, opted in, a publicly posted business address, or other). A lead whose address looks to be in Canada or Germany is noted when you enrol it, as information. You are the sender of these emails and are responsible for having consent or another lawful reason to email each person.
Check a domain and an address before you send
Four free tools check the setup that decides whether your email reaches the inbox. They read public DNS records and fixed rules only, so they need no connection and cost no credits. The same checks run on the free pages at hermoso.ai/tools.
check_domain_email_healthreads a domain's MX records (who receives its mail), SPF (which servers may send as it, counted against SPF's limit of 10 DNS lookups), DKIM (its signing keys; passselectorwhen you know it, otherwise common selectors are tried), DMARC (its policy and where reports go) and blocklists (its mail servers on public spam lists whose terms allow this lookup). Passchecksto run only some. Every finding says what to change.check_email_addresschecks one address: whether it is written correctly, whether its domain can receive mail, and whether it is a throwaway inbox, a role address such as info@, a free provider or a likely typo, with the fix. It never contacts the mail server, so it cannot tell whether that one mailbox exists.generate_dns_recordwrites an SPF or DMARC record from plain choices (your sending services, report addresses, the policy), ready to paste at your DNS host. With a domain, the SPF record's includes are read and counted.check_spam_wordsscans a subject line and email text for wording and formatting that read as spam. Sender reputation and authentication matter more than words, so a low score is not a promise of the inbox.
Each tool answers in plain sentences and also returns the structured result. A DNS lookup that fails is reported as "could not tell", never as a missing record.
In the web app
Automations, Email shows the connected mailboxes with what each can do, its daily ceiling and any pause, the sender details, the emails waiting for review, each sequence with how many people are waiting, replied or finished, the lead list and the latest replies. You can connect a mailbox, pause it, add leads, write a sequence with versions and a reply rule, approve drafts, enrol people and pause it there.