Before you begin
- Create a Mermail mailbox and confirm the workspace and sender address you want to use.
- If you use a branded address, complete custom domain setup and test both sending and receiving first.
- Connect your assistant to Mermail MCP if you want to use the prompts below. You can also review and send drafts in the Mermail web app.
- Prepare your product description, target audience, and a small contact list or clear research criteria. Exclude people who have opted out.
Optional paid research
The Apify outreach demo shows a paid research option. It is not required when you already have suitable contacts. For wallet-enabled research, use the full OAuth MCP profile and connect Agent Wallet. The workspace owner completes the initial PayBox connection; an API-key connection or agent-inbox profile does not unlock Agent Wallet. Check available research tools, current prices, and your spending limit before approving a purchase. A Mermail subscription does not include third-party research charges.Run the workflow
1
Choose your sender mailbox
Ask your connected assistant to check Mermail and list your mailboxes:Select the exact mailbox and workspace from the result. Use that sender
consistently for research context, saved emails, and any later send.
2
Define your prospect search
If you already have contacts, give the assistant your approved list and its
source, then skip paid service access. Ask it to review the list without
purchasing research or sending emails.For optional Apify research, make the selection criteria explicit instead
of relying on an undefined ranking such as “top”:Public research may return fewer than three suitable contacts. Ask for an
explanation rather than filling missing results with invented details.
3
Complete service access if required
Skip this step if you are using your own contacts. Otherwise, review the proposed Apify purchase and set an explicit spending limit
before authorizing it. If signing is required, follow the console signing
link returned by the assistant and complete the approval in the app.The video shows the user asking for the console signing URL, then returning
to the conversation after signing. You can use the same handoff:After signing, ask the assistant to check the existing payment and service
access before continuing. Payment approval alone does not confirm that
research has completed. See x402 and paid services
for the payment and recovery concepts.
4
Review leads and prepare emails
Check the returned businesses, source links, and recipient addresses.
A public contact address is not proof that it belongs to the business owner.
Approve the contacts you want to use, then ask for personalized emails:Open the saved emails in Mermail. Check the sender, recipient, subject,
personalization, links, and signature. Include a clear way to decline
further contact, and honor those requests before preparing follow-ups.
Public contact details alone do not establish permission to send.
Email preparation and sending stay in Mermail.
5
Approve sending and verify the result
Once the content is ready, explicitly identify the reviewed drafts you want
sent. For example:Check Sent in that mailbox and the returned send results. A saved draft
is not a sent email, and a successful send does not guarantee delivery or
a reply. If a send result is uncertain, inspect the mailbox before retrying
to avoid contacting the same person twice.
Check the outcome
- The sender belongs to the intended workspace and mailbox.
- Every used contact has a source; missing contact details were not guessed.
- Any paid research stayed within your approved limit; existing contacts required no research purchase.
- Only the emails you approved were sent; unapproved drafts remain untouched.
- You can distinguish failed, saved, and sent results for each recipient.
If the workflow stops
For related workflows, return to Usecases overview or read
the Site Analytics guide.