Blog Sections Open
Sending SMS Notifications After eForm Submission
A practical pattern for triggering SMS notifications from an Evolution CMS form after the normal eForm submission flow succeeds.
Once a site form becomes part of a real operational workflow, email is not always fast enough. Many teams eventually want a simple SMS notification after a user submits a form. The good news is that eForm can stay the input layer while a separate SMS service handles delivery.
The right design is to keep the form processor and the SMS transport separate.
A reliable flow
- validate and submit the form through eForm as usual,
- on successful processing, call a small custom hook or snippet,
- send the prepared message through the chosen SMS API provider.
That way, form validation stays predictable and the SMS part can evolve independently. If the provider changes later, only the integration hook needs to change, not the whole form layer.
In other words, the clean pattern is not “replace eForm with SMS logic”. It is “let eForm handle submission, then trigger the SMS step after success”.
Making eForm Captcha Work Inside Toggled or Hidden Form Blocks
How to keep eForm validation and captcha behavior reliable when the form lives inside content that is initially hidden or toggled with JavaScript.
Updating TV Values for a Specific Resource Through the Evolution API
A straightforward pattern for changing one resource TV programmatically instead of trying to fake the edit form by hand.