What Zindua Connect solves for WordPress teams
Most WordPress sites combine multiple plugins for SMTP, OTP, contact forms, and order notifications. This increases maintenance cost and makes delivery debugging painful.
Zindua Connect centralizes delivery through one project key. WordPress keeps feature configuration and verification flow, while Zindua manages channel connectivity, template rendering, and delivery logs.
Setup path used by production teams
Start on zindua.run: create one project, connect email provider and optionally WhatsApp, then prepare template slugs for OTP, contact notifications, and commerce events.
In wp-admin, install zindua-connect.zip, paste your API key, verify connection, and select templates from synced pickers. No provider credentials are stored inside WordPress.
- One WordPress site = one project API key
- Service and WhatsApp connections handled on zindua.run
- Template slugs synced to WordPress pickers
- Delivery events visible in Zindua logs
OTP, forms, and WooCommerce with one delivery pipeline
You can enable OTP login via shortcode or Gutenberg block, route existing form plugins through wp_mail override, or use the built-in Zindua contact form builder.
For WooCommerce, map lifecycle templates (processing, completed, refunded, cancelled) and keep language and variable consistency in one dashboard.
[zindua_otp_login] [zindua_otp_login channel="choice" redirect="/my-account" lang="fr"] [zindua_contact_form] [zindua_contact_form fields="sales" template="sales-inquiry" confirm="contact-received"]
Security model developers care about
WordPress stores your plugin configuration and sends variables. Gmail, Outlook, SMTP, and WhatsApp sessions remain in Zindua infrastructure.
This separation lowers secret exposure in CMS hosting and keeps channel credentials out of wp-config and plugin-level storage.