How does FormMerge prevent duplicate mail merge emails after rows move?

A 30-day ledger protects the logical notification fingerprint, so known sent, sending, or uncertain messages remain blocked after sorting, copying, or clearing a visible status.

What should I do with SEND_UNCERTAIN?

Check the recipient inbox, then explicitly mark verified sent, reset after review, or keep the notification blocked. FormMerge does not guess or promise exactly-once delivery.

Is FormMerge Pro a newsletter or cold-email tool?

No. FormMerge Pro is for small operational email workflows, not newsletters, cold email, CRM, tracking, or marketing automation.

Google Sheets mail merge

Mail merge from Google Sheets—without blind duplicate sends.

FormMerge Pro requires an exact pending preview and one-time approval before sending. A 30-day protected-message ledger blocks known replays even after rows move or a visible status is cleared; SEND_UNCERTAIN stays blocked until the owner checks the inbox.

Exact preview 30-day replay guard SEND_UNCERTAIN review Watchdog pause

Install from Marketplace Run the copied-sheet test

Mail merge previewRow → Email

Google Sheetcampaign rows

Selected rows42

Name, Email, Plan, Date

Email draftpersonalized

Merge tag{{Name}}

Hi {{Name}}, your {{Plan}} is ready.

1. Configure2. Preview + approve3. Send

Protected operational automation, not campaign software.

Choose a stable business key when available, inspect the exact pending set, then audit sent, blocked, uncertain, error, and resolution events without uploading recipient or message content.

Protect the logical notification

A stable key plus protected recipient/subject/body fingerprint survives row sorting, copying, and cleared visible status.

Resolve instead of guessing

Mark verified sent, reset only after an inbox check, or keep an uncertain notification blocked.

Pause an error storm

Three consecutive trigger failures pause automatic sending until the owner reviews, repairs, and resumes.

A focused workflow, not another bulky form builder.

Each FormSuite add-on does one operational job around Google Forms, Sheets, Docs, or Gmail — then gets out of the way.

Map columns

Use sheet headers as merge tags.

Preview the pending batch

Check exact recipients and output; duplicates block approval.

Approve, send, and track

Use one-time approval, row status, and trigger health.

Moving a simple Form Mule workflow?

Start with a copied spreadsheet and one operational template. FormMerge is independent and does not claim full Form Mule feature parity.

Migration fit checklist

See which one-template workflows fit and which advanced Form Mule features do not.

Not-sending checklist

Check triggers, authorization, quota, recipients, conditions, and uncertain prior sends.

Duplicate-send safety

Understand exact preview, locks, pre-send state, and fail-closed recovery.

Prove the safety path in five minutes.

Use two rows and inboxes you control. Trigger the duplicate blocker, correct one row, inspect the exact pending batch, approve once, send, and verify row plus trigger health.

Open the copied-sheet checklist Get setup help

See 30-day replay protection and uncertain-send handling.

The controlled 31-second proof shows persistent notification protection, explicit SEND_UNCERTAIN resolution, the audit, and watchdog boundary. It does not claim provider-level exactly-once delivery.

Watch protected automation proof Run the copied-sheet checklist

Frequently asked questions

Is this for newsletters?

It is better for operational mail merge: confirmations, updates, notices, and small campaigns.

Can I test before sending?

Yes. Use a copied sheet, inspect the exact pending recipients, subjects, and bodies, remove duplicate payloads, then approve the unchanged preview once.

Where is status tracked?

The sheet records SENT, SENDING, or SEND_UNCERTAIN states. A 30-day audit shows protected replays and manual resolutions; trigger health shows presence, duplicates, last success, last error, repair, and paused state.