Workflow Trigger: Number Validation in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

The Number Validation trigger fires when a contact's phone number is checked against the carrier database. Use it to keep SMS lists clean, tag bad numbers, and stay TCPA-compliant.

What it does

The Number Validation trigger runs a workflow based on the result of Sparkforge's phone-number validation check. It fires when a contact is created and the validation runs, letting you route the contact based on whether the number is mobile, landline, or invalid — before the first SMS goes out.

Trigger name: Number Validation

When it fires: When a contact is created and validation runs against the contact's number. It does not fire on Twilio error codes after a send.

How to configure

Enable validation at the agency level. Go to agency settings > phone integration settings and enable number validation for each location.
Build the workflow. Add Number Validation as the trigger.
Set the filter. Use the Number is filter to pick the validation status that should fire the workflow (mobile, landline, invalid, etc.).
Add actions. Tag, route, notify, or remove based on the result.

Filters

Filter	Description	Required
Number is	Validation status that triggers the workflow	No

Use cases

SMS list hygiene. Auto-add valid SMS-capable numbers to active campaigns; skip invalid or non-SMS numbers.
Lead qualification. Tag form leads as invalid when their number fails validation, so reps don't waste time.
Internal alerts. Notify the team when a validation fails on a high-value lead so someone can verify manually.
Compliance. Block SMS sends to numbers flagged as landline or invalid to protect TCPA posture.
Auto-tagging. Apply Do Not SMS or Mobile-only tags based on the validation result for cleaner segmentation.

Frequently Asked Questions

When does the Number Validation trigger fire?

When a contact is created and Sparkforge runs the validation check against the contact's phone number. It does not fire on downstream Twilio error codes.

Do I need to enable validation before the trigger works?

Yes. Turn on number validation in agency phone integration settings for each location. The trigger only fires when validation actually runs.

Can I block SMS sends to landlines automatically?

Yes. Filter the trigger on landline status and route those contacts away from SMS workflows or tag them so SMS sends skip them.

Which number types can be validated?

Mobile, landline, and VoIP. The validation result tells you whether the number can receive SMS so workflows can branch accordingly.

Does this help with TCPA compliance?

It helps. Filtering out invalid or non-SMS-capable numbers reduces the risk of unwanted SMS sends, which is a key TCPA exposure point.