Docs Navigation Open

Email and Webhooks

Use mail, webhooks, and notifications to connect site events with real business workflows.

Email and webhooks are the bridge between user actions and business processes. In Evolution projects this usually starts with forms, orders, registrations, and manager notifications.

Classic Pattern

  • eForm — simple contact, callback, and order forms
  • FormLister — richer validation, controllers, and custom form flows
  • custom snippets or plugins — event-based notification logic

Current Pattern

  • sMailer — package-level mail service for current Evo projects
  • sApi — endpoint layer when the site exchanges JSON with external systems
  • controllers and package services — cleaner webhook processing than parser snippets
evo()->sendmail([
    'to' => 'manager@example.com',
    'subject' => 'New order',
    'body' => $html,
    'type' => 'text/html'
]);

For new builds, keep mail and webhook logic in controllers, services, or package classes where it can be tested and logged. Reserve parser snippets for the page layer.

Previous

Authentication

Separate manager auth, web-user auth, protected content, and passkey flows instead of treating them as one thing.

Next

AI and MCP

Current AI and MCP tooling in Evolution centers on eAi, eMCP, and adjacent workflow packages.