Handsentby BuildnodeSign in
Handsentby Buildnode

Mail merge from your own Gmail.

One personalized email per person, sent from your inbox at a human pace, with follow-ups that stop the moment someone replies.

Free while in early access.

How it works

  1. 1

    Connect your Gmail.

    Handsent sends through the Google account you choose. Mail lands in your Sent folder; replies land in your inbox.

  2. 2

    Pick a list and write the email.

    A Google Sheet, a CSV, or your CRM through the API. Merge fields fill in names and details. Save it as a template.

  3. 3

    Send like a person.

    Handsent paces sends across the day, threads follow-ups under the original message, and stops the sequence as soon as someone answers.

Built for the people you already talk to

Handsent is for customers, leads who asked to hear from you, and business contacts you have a lawful basis to reach. It is not a tool for unsolicited mail, and it is built to make that hard:

  • Daily and hourly caps per inbox, and a send window in your timezone.
  • A mailing address and unsubscribe line are required in every campaign.
  • “STOP”, “unsubscribe” and bounces suppress the address across your whole workspace.
  • One-click unsubscribe headers so Gmail can show its native unsubscribe.
  • No tracking pixels, no rewritten links.
  • Every send and every action is in the audit log.

What Handsent can see

Handsent asks Google for three permissions and uses each for one visible feature:

PermissionUsed for
Send email on your behalfSending the campaigns and test emails you start
View your email messagesReading only the threads Handsent started, to detect replies, bounces and unsubscribe requests, and reading the Gmail draft you chose as a template
See, edit and create your spreadsheetsReading the sheet you connected as a list and writing each row's status back to it

Handsent never reads your inbox, never sells or shares your data, and deletes your Google tokens the moment you disconnect an inbox. Privacy policy Terms

For teams and integrations

Workspaces with roles, org-owned API keys with read/write/admin scopes, signed webhooks for every event, a REST API and an MCP server so your CRM or assistant can add contacts, start a campaign, or read the audit log.