Campaigns, always current
A theme-styled block that shows your latest Laposta campaigns — no widget fighting your CSS, no stale content.
For WordPress → Laposta
Signup forms and campaigns that stay in sync with Laposta, automatically.
Wynko builds forms straight from your live Laposta list — fields, validation, and all — and keeps a campaigns block current in the background. Your API key is encrypted at rest, every signup is rate-limited and re-validated server-side, and it runs the same way across an entire multisite network.
Laposta is the source of truth
Forms and campaigns auto-sync with your list, so nothing drifts out of date.
Encrypted API key
Stored encrypted at rest, verified live, and never displayed back to you.
Multisite-native
Per-site settings, logs, and alerts, with a clean per-site uninstall.
Built-in spam protection
Rate limiting, a honeypot, and full server-side re-validation on every signup.
What’s in the envelope
Everything the connection needs. Nothing it doesn’t.
Forms that can’t go stale
Signup forms are built live from your Laposta list, so the fields visitors see always match what Laposta expects.
A clear record of everything
See every sync and signup at a glance — nothing sensitive ever ends up in the log.
Know the moment it matters
Get an email the instant something needs your attention, without your inbox filling up over it.
Your API key, protected
Encrypted at rest, verified before it’s ever used, and never shown back to you or anyone else.
Fast by default
Campaigns load instantly from cache and refresh automatically — with a manual sync whenever you want it sooner.
How it works
Three steps, then it runs itself.
- 01
Connect your API key
Paste it in, or set it as a constant. Wynko verifies it against Laposta before saving anything.
- 02
Build your form or block
Pick a list, place the campaigns block or the signup form, and match the fields your list already has.
- 03
Let it run
Campaigns stay cached and current; signups are validated, rate-limited, and logged automatically.
Questions
Frequently asked
Where do I find my Laposta API key?
Laposta documents this in their help center — paste the key into Wynko → Settings. The plugin makes a live request to verify it before storing anything, so an invalid key is rejected on the spot.
Can I keep the API key out of the database?
Yes, and it’s the recommended setup: define WYNKO_API_KEY in wp-config.php, or set it as an environment variable (a .env file your host loads works too). Either always wins over a stored value. On multisite, suffix your own site’s blog ID — e.g. WYNKO_API_KEY_3 for the site whose blog ID is 3 — to give that site its own key.
Does it work on multisite?
Yes. Settings are per-site, so every site connects to its own Laposta account, keeps its own log, and mails its own alerts on its own hourly cap.
What does the plugin store about my visitors?
Nothing. Signup data goes straight to Laposta — Wynko never stores what a visitor typed. The activity log only records whether a submission succeeded or failed and which form it was, never the email address or any field value.
How many signup forms can I have?
As many as you need. Wynko → Signup forms lists every form on the site, with an "Add form" button to create another.
Does it slow my site down?
Campaign data is cached in a transient — 60 minutes by default, configurable — so a page holding the block doesn’t call the Laposta API on every view.
Ready to send it?
Install Wynko from WordPress.org and connect your Laposta account in a few minutes.