Joinotify
| 开发者 | meumouse |
|---|---|
| 更新时间 | 2026年10月1日 10:31 |
| PHP版本: | 8.1.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Joinotify — from join and notify — turns things that happen on your site into WhatsApp messages, without writing code. You draw the automation on a canvas: pick a trigger (an order is paid, a form is submitted, a user registers), add conditions, delays and loops, and attach the messages you want sent.
The plugin is free and has no locked features. Building, saving, testing and exporting workflows all work out of the box. Sending messages requires a Joinotify account, because messages are delivered through the official WhatsApp Cloud API — see External services below.
Visual workflow builder
- Drag-and-drop canvas with triggers, actions, conditions, delays and loops
- Branching logic with true/false paths
- Placeholders and custom variables to personalise every message
- Import and export workflows as JSON
- Ready-made workflow templates
- Text, media, audio, documents and stickers
- Interactive messages: reply buttons, option lists and link buttons
- Location messages, contact cards and reactions
- Meta-approved message templates, listed inside the builder with preview, language and approval status
- Real delivery confirmation: sent, delivered, read and failed, with the reason reported by Meta
- Multiple numbers and multiple WhatsApp Business Accounts on the same account
- WooCommerce — order status, refunds, subscriptions, digital product delivery, abandoned carts
- WPForms, Elementor Forms and Flexify Checkout
- WordPress user events
- Telegram and Resend (e-mail) as additional delivery channels
- AI-generated message content through the WordPress AI Client, using the provider set up in Settings → Connectors (optional)
- Message history with per-message status
- Processing queue for scheduled and retried messages
- Debug log with configurable retention
- Passwordless login (OTP) over WhatsApp
- A PHP extension API: register your own actions, triggers, integrations, conditions, placeholders, REST routes and channels with filters only
安装:
- Upload the plugin to
/wp-content/plugins/joinotify, or install it from the Plugins screen. - Activate it. The setup wizard opens automatically.
- Work through the wizard: default country, Joinotify API key, optional AI provider, documentation, usage-data choice.
- Build your first automation from Joinotify → Add new workflow.
wp-admin/admin.php?page=joinotify-onboarding.屏幕截图:
常见问题:
Do I need a paid account to use the plugin?
The plugin itself is free and every feature is unlocked. Building, testing and exporting workflows works with no account at all. Delivering messages requires a Joinotify account, because WhatsApp messages go through Meta's official Cloud API and that access is provisioned per account.
Where do I get the API key?
Create it for your site on the Joinotify panel at https://app.joinotify.com, then paste it in the setup wizard (step 2) or in Settings → General → WhatsApp Cloud API.
Can I send a message to anyone at any time?
No — that is a WhatsApp rule, not a plugin limitation. Outside a 24-hour window opened by the contact writing to you first, only Meta-approved message templates can be delivered. The builder lists your approved templates so you can pick one.
Does it work without WooCommerce?
Yes. WooCommerce is one integration among several; WPForms, Elementor, Flexify Checkout and core WordPress user events all work on their own.
Where is the uncompiled JavaScript?
It ships with the plugin, under app/src, together with the build configuration needed to reproduce app/dist. See Source code and build above, which also lists the source of every third-party library bundled into it.
Is this plugin affiliated with WhatsApp or Meta?
No. Joinotify is not affiliated with, endorsed by or sponsored by WhatsApp LLC or Meta Platforms, Inc. WhatsApp is a trademark of WhatsApp LLC.
更新日志:
2.5.1
- Fixed: the plugin ships its translations again (Brazilian and European Portuguese, Spanish, German, French and Italian). Sites in those languages showed Joinotify in English since 2.5.0. A WordPress.org language pack, once a locale has one, still takes precedence.
- Fixed: counts such as "%d contacts" or "%d days" use the plural form in every translated language instead of the singular.
- Fixed: the labels of the workflow post type are translated.
- New: Joinotify → Audiences & Contacts, a screen for the contact base of your Joinotify account. List, search, filter and export contacts; add them by hand or import a CSV file; edit, opt in, opt out, merge, export or erase a contact; and manage custom fields, tags, saved audiences and the suppression list. The base stays on Joinotify and the API key never reaches the browser. A key restricted to some numbers makes the screen read only.
- New: Joinotify Cloud sync, off by default under Settings → General. Once switched on, it sends this site's customers and events to your Joinotify account: WooCommerce orders and subscriptions, new customers, WordPress sign-ups and profile changes, WPForms and Elementor forms, and Flexify Checkout leads and carts. It says what it sends before you turn it on, lets you leave out forms, carts, order items and full addresses, and tags every contact with the site's name or a tag of your choice.
- New: the sync delivers in batches from a scheduled task, never during a checkout or a page load. A failed batch is tried again. A revoked key, a site removed from the panel or a copy of the site at another address pauses the sync instead of sending test orders to real customers. Its window shows what is waiting, sent or given up on and why it is paused, with a "Try again" button.
- New: "Send existing customers" sends the users and guest buyers the store already has as contacts, once and in the background, without starting any flow.
- New: an optional marketing consent checkbox, unticked by default, for the classic and block checkouts, the sign-up forms and My account. Consent is recorded on Joinotify with its evidence, and an opt-in or opt-out made on Joinotify updates the customer's preference on the site.
- New: each source can add its own tags and send user and order meta into custom fields, and each WPForms or Elementor form can get a rule choosing its phone, e-mail, name, consent checkbox, tags and custom fields.
- New: "Save contact" and "Tag contact" workflow actions, in a new Contacts tab of the action library, create or update the contact on Joinotify from any trigger. They need the Cloud sync switched on.
- New: "Send webhook" workflow action, which posts the trigger's data or a JSON of your own to any public URL, with optional headers and an HMAC signature.
- New: developers can send their own events to Joinotify flows with
joinotify_track( $name, $data, $contact ). - New: WordPress's "Export Personal Data" and "Erase Personal Data" tools cover the sync's consent records and queued events, and erasing also asks Joinotify to erase the contacts this site sent.
- New: after ten minutes of use, the settings screen and the builder ask administrators to rate Joinotify on WordPress.org. "Maybe later" hides the request for a week.
- New: action settings declared with the
placeholdercomponent get the trigger's variable picker. - Changed: the admin screens and the OTP login form draw every icon with Boxicons, and builder steps that only named an icon now show it.
- Changed: focused fields are outlined by a solid border in the primary color instead of a soft glow, so their text no longer moves.
- Fixed: the strings of the Vue admin screens now reach translate.wordpress.org, and language packs load them for every part of those screens.
- Fixed: the "New order" trigger never ran for orders placed with the WooCommerce checkout block.
- Fixed: the WPForms PayPal Standard trigger raised PHP warnings and sent an empty entry id.
- Fixed: the "Connect to Joinotify" button ended in "invalid code".
- Fixed: a workflow step's description could run script in the builder when it came from an imported workflow, a template or an AI-generated flow.
- Fixed: actions added with
joinotify_register_action()lost their description in the action library.
- New: the workflows, message history and processing queue screens export to a JSON file. Export one row from its "Export" action, the rows you selected, or — in the history and the queue — everything matching the current filters. A single workflow downloads as the same file the builder exports, so it can be imported again; several download together in one file. The processing queue gained row selection for this. A history export stops at the 5,000 most recent records and tells you when it does.
- New: the workflows, message history and processing queue tables have an "Items per page" selector with 10, 25, 50, 100 or 200 rows. Each screen remembers your choice, and changing it keeps the first visible row on screen instead of jumping back to page 1.
- New: the
{{ wc_shipping_method_total }}variable returns the shipping cost and method of a WooCommerce order as plain text, for example "R$ 20,00 via SEDEX", or only the method name when shipping is free. - Changed: when WhatsApp refuses a message, its own explanation now appears in the builder test after the description, and the debug log keeps it for every failed send.
- Changed: the tables show 25 rows per page by default instead of 20.
- Fixed: template variables go out as one line of plain text, as WhatsApp requires. Line breaks become commas and HTML is removed, so a multi-line address no longer gets the template refused and a WooCommerce price no longer arrives as raw HTML.
- Fixed: templates built outside the builder — by an extension, the OTP login or a retry queued by an earlier version — were still refused with error 132018 because of line breaks. Every template send now follows the same one-line rule.
- Fixed: saving the test number and running the test announced a refused message in a success notice.
- Fixed: deleting records or cancelling a resend in the message history, or running or cancelling an item in the processing queue, reloaded the table without its filters, so it showed unrelated rows while the filter still looked active.
- Fixed: until someone opened the template picker, template sends were recorded in the message history with only the template name and variables. The first send on a site now loads the template text by itself.
- Fixed:
{{ wc_shipping_address }}was described as the shipping address, but it has always returned the shipping cost and method. Its value is unchanged, so existing messages send what they always sent, but it now arrives as plain text instead of price markup, and the builder describes and previews it as a cost. If you used it for the delivery address, switch to{{ wc_shipping_full_address }}.
- New: the message history shows what a template message actually said. The record keeps the template text with each value filled in, and the details window lists the template's language and the value given to each variable.
- New: while debug mode is on, the debug log records every message delivered — template, text or media — not only the ones that fail. A failed template send always includes the template name, language and values.
- New: login codes sent by template are never written to the history or the log. Developers can hide the values of other templates with the
Joinotify/Api/Template_Dispatch_Logfilter. - Changed: the debug log viewer lays structured details out over indented lines, so they are easier to read.
- Fixed: templates with named variables, such as
{{nome}}, were refused by WhatsApp. - Fixed: login codes and builder test messages were listed under the "API" source in the message history, instead of "OTP" and "Test message".
- Fixed: the message history showed the raw word "template" in the type column instead of a translated label.
- Fixed: the country list in the setup wizard opened behind the wizard itself.
- Fixed: the "Joinotify account" field looked empty after a key was saved, instead of showing the key's masked prefix.
- Removed: the "Plugin updates" row in Settings → About, which repeated what the plugins screen already shows.
- New: how many times a failed message is retried, and how long the first wait is, are now settings under Settings → General → Delivery retries. The default is 5 attempts starting 30 minutes apart, replacing the fixed budget of 120 attempts used until now. Choosing "Do not retry" keeps a failed message out of the queue altogether.
- New: a resend that has not run yet can be cancelled from the message history. Select the records and use "Cancel resend"; they settle as "cancelled", a new status with its own tab. Records whose retry already ran are left alone.
- New: the message history has an Error column, showing why a message failed without having to open the details.
- Changed: the setup wizard now uses the same visual style as the rest of the admin screens.
- Fixed: a message left in "queued" stayed that way forever, even after the retry had succeeded or run out of attempts. Those records now settle as sent or failed.
- Fixed: a test message refused by WhatsApp was announced as a success, in a green notice that carried the failure text.
- Fixed: the reason a send failed never reached the screen. Failures now explain what happened and what to do about it — in particular, sending outside the 24-hour customer service window says so and points to template messages, instead of leaving the cause in the log.
- Fixed: a fatal error could take the whole site down, login page included, whenever the plugin wrote a log entry early in the request. Sites on PHP 8 with debugging enabled were the ones affected.
- Fixed: the workflow post type was never actually registered with WordPress. Workflows themselves kept working, but the permissions declared for them did not apply, so an Editor could open and delete workflows that were meant to be restricted to administrators.
- Fixed: the plugin was reported as incompatible with WooCommerce's High-Performance Order Storage, because the compatibility declaration was sent after WooCommerce had stopped listening. HPOS can now be enabled with Joinotify active.
- No change to the plugin itself: the code, the interface and the translations are the same as 2.3.2. Only the release pipeline that publishes the package to WordPress.org was fixed.
- Changed: the phone number library moved to giggsey/libphonenumber-for-php-lite 9.0.37. The version shipped until now was the last one supporting PHP 7.4, released in February 2025 and no longer updated, which would have frozen the country numbering rules the plugin validates against. PHP 8.1 remains the minimum.
- Removed: the legacy Evolution relay, in full. Messages now go through the official WhatsApp Cloud API only.
- Security: the plugin shipped an embedded slots-manager API key, encrypted with its decryption key on the next line. It was the same credential in every installation and anyone could extract it. Both it and the hand-rolled encryption around it are gone.
- Removed with the relay: the Proxy API and its endpoints, the "Message transport" selector, phone registration by QR code and OTP, the per-number connection check and the WhatsApp group listing. None of them exist on the official API.
- Removed: the scheduled task that polled phone connections every six hours. Upgrading unschedules it.
- Changed:
Transportalways resolves to the official API and gainedTransport::is_ready(), which reports whether the site has a key to send with. TheJoinotify/Transport/Activefilter went away with the transport choice. - Changed:
slots-manager.joinotify.comwas dropped from the external services list, since the plugin no longer contacts it. - Added: a "Source code and build" section in this readme, documenting where the uncompiled frontend source lives, how to rebuild it, and the source of every third-party library bundled into the package.
- Changed: the build step that strips the emoji picker's CDN URL now targets the library constant rather than the address, so no remote asset URL appears anywhere in the plugin.
- Changed: WordPress 7.0 is now required. The AI features run on the AI Client that ships with it.
- Changed: AI content is generated through the WordPress AI Client. Choose a provider and store its key once in Settings → Connectors and every AI action uses it — Joinotify no longer keeps a key of its own, nor calls a provider directly. The OpenAI and Anthropic integrations were removed, so a site using AI has to set the provider up again in Connectors.
- Removed: the "PHP Snippet" action, which executed arbitrary PHP. Saved workflows still open, but that step no longer runs.
- New: the builder warns when a step cannot open a conversation on the official API. Text, media, interactive messages and AI copy only reach a contact within 24 hours of their last reply, so a workflow that starts the conversation has to lead with an approved template.
- Improved: the OTP login template is now picked from the templates approved on your account instead of typed by name, and its language comes from the template itself.
- Fixed: an account with more than 100 message templates lost the rest from the template pickers.
- Changed: translations are delivered by translate.wordpress.org instead of being bundled with the plugin.
- Changed: the Joinotify menu moved below the WordPress items instead of sitting among them.
- Changed: the standalone "Joinotify OTP Login" plugin is no longer deactivated on its own. You are told it duplicates the built-in login and decide what to do.
- Removed: country detection by IP address, which contacted a third-party service that was not declared and was never actually used.
- Removed: the button offering to install the cart recovery add-on from an external download. It had done nothing since 2.0.0.
- Improved: the phone number library was updated, and the builder styles and the setup notice now go through the standard WordPress asset queue.
- New: anonymous usage reporting now actually delivers. Still off by default — nothing leaves the site until you agree in the setup wizard.
- New: the site is identified by a random value generated locally, never derived from your address. It is shown in Settings → About so you can quote it in a support ticket.
- New: reports are batched and sent by a scheduled task, never during a page load. Repeated events collapse to one per day.
- New: the consent screen also shows sample events and explains how the site is identified.
- New: switching usage reporting off deletes anything still queued and asks the service to stop counting the installation.
- New: actions for extensions —
Joinotify/Settings/Saved(with the settings before and after each save),Joinotify/Sender_Selected,Joinotify/Notification_Queue/Item_RetriedandJoinotify/Debug_Log/Recorded. - New: six-step setup wizard shown after activation, covering the default country, the Joinotify API key, an optional AI provider, the documentation, the usage-data choice and the first automation.
- New: anonymous usage reporting, off by default, with the exact payload shown before you agree.
- New: WhatsApp connection through the official Joinotify API, replacing the Proxy API over Evolution.
- New: Meta-approved message templates listed inside the builder, with a dedicated template action.
- New: interactive messages — reply buttons, option lists, link buttons, location, contact cards, stickers and reactions.
- New: real delivery confirmation through account events (delivered, read, failed).
- The plugin is now free software under the GPLv2 and every feature is unlocked — the licensing system and its activation screen were removed.
- Changed: updates are now delivered by WordPress.org; the plugin no longer contacts an update server of its own.
- Changed: the Proxy API is off by default on new installs. It remains deprecated and will be removed.
- Removed: the extension installer that downloaded plugin packages from an external URL.
- Improved: OTP login codes are delivered through an authentication template on the official API.
- Improved: the workflow template library is now served by the Joinotify API at the same address as the account, counts an install when a template is used, and picks up revised templates on its own.
- Fixed: deactivating the plugin left all of its scheduled tasks behind. They are now cleared. Nothing else is deleted — deactivating is not uninstalling.
- Deprecated: the Proxy API setting under Settings → General.
- New: "Loop" action that walks a collection and runs its body once per item.
- New: loop variables available inside the loop body.
- Removed: WhatsApp disconnection notice.
- Fixed: the default country code was not applied to numbers typed without one.
- New: WooCommerce digital product delivery straight from the workflow builder.
- New: attachments on e-mail (Resend) and WhatsApp media actions.