How-to
Keep test submissions out of your CRM
FormPulse checks work by really submitting your form, on demand or on a schedule. That's the only honest way to know it works. Here's how to make sure those test submissions don't end up as fake leads, emails, or CRM rows.
Use an obvious test name and email
Give your monitor a test payload a human or a filter can spot at a glance, something like “FormPulse Canary” for the name and a dedicated address like canary@yourdomain.com for email. That way, even if a submission does land somewhere, it's obviously not a real customer.
Add a hidden source field and a skip rule
Add a hidden field to your form, for example source with the value formpulse, and set FormPulse's canary fields to fill it in. Then add one rule in Zapier, your CRM, or your form backend: if source equals formpulse, skip the notification, the CRM row, or the Zap. This is the single most reliable fix.
Point at a staging or copy of the form when you can
If your form tooling supports it, monitor a staging version or an internal copy of the form instead of the live production one. Same markup, same submit flow, zero risk of a real lead or email showing up anywhere.
Remove the monitor when you no longer need ongoing checks
Every monitor runs on the same fleet schedule, about every 6 hours, so there's no per-monitor frequency to adjust. If a form doesn't need continuing coverage anymore, remove the monitor and use a free check after future deploys to confirm things still work. If you do want ongoing coverage, that fixed cadence plus the filter and hidden-field tips above is how FormPulse is meant to run.
FAQ
Does FormPulse really submit my form?
Yes. We fill out the fields you configure and click submit, exactly like a visitor would. That's the only way to know the whole path (submit button, thank-you page, delivery webhook) actually works.
Will this create a fake lead in my CRM?
It can, if your form is wired straight to a live inbox or CRM with no filtering. Use the obvious test payload and the hidden source field plus a skip rule below to keep it out.
What if I can't add a hidden field or a skip rule?
Use a clearly fake name and email so it's easy to spot and delete, and consider pointing FormPulse at a staging copy of the form instead. If you don't need ongoing checks on this form, remove the monitor and use a free check after your next deploy instead.
Can I tell FormPulse not to send emails at all?
FormPulse doesn't control what your form does after submit, we only submit it and watch for a confirmation. Filtering out test rows has to happen on your form's side, using the tips above.
Still not sure what to filter on?
Run a free check first and see exactly what FormPulse submits, then set up your skip rule from there.