Builder actions

After the trigger, a workflow is a sequence of actions. They live in the library that opens when you click the + on a canvas node, split into tabs. Clicking an action already on the canvas opens its settings in the side panel.

Only the actions of the integrations enabled under Joinotify → Settings → Integrations show up — the Telegram one, for example, only exists with the Telegram integration switched on.

WhatsApp messages

Every WhatsApp action asks for the sender (one of the account's numbers) and the recipient, which takes a phone number or a placeholder such as {{ wc_billing_phone }}.

Template message

The action lists the account's approved templates, with language, category and a preview, and asks for a value for each template variable — fixed text or a trigger placeholder. Since 2.6.0 it covers everything Meta offers in a template:

• Image, video or document header — the file comes from a link, a placeholder or the media library. The action will not save without it, because Meta refuses the send. A document goes out with its file name.
• Location header — latitude and longitude, with an optional name and address.
• URL button — the variable completes only what comes after the button's fixed address. For a link to your own site, use the remove_home_url modifier or {{ wc_first_product_review_path }} — see Modifiers.
• Copy-code button of a marketing template, filled with the coupon you provide.
• Code button of an authentication template, which repeats the code from the body when left empty.
• Limited-time offer — the expiration takes a date, a timestamp or a relative time such as +2 days.
• Carousel — each card asks for its own header file, variables and buttons.

The variable values go out on a single line, as WhatsApp requires: line breaks become commas and HTML markup is removed, so a multi-line address or a WooCommerce price does not get the template refused by Meta.

Workflow control

Delays depend on WP-Cron — see Minimum requirements.

Condition

The available conditions depend on the trigger: order status and total, purchased products, payment and shipping method, user role and metadata, form fields and whatever else the trigger registers.

WhatsApp 24-hour window

Offered on every trigger since 2.6.0. At the moment the workflow reaches it, it asks the platform whether a recipient's window is open, closed or unknown (when the platform could not be asked). It takes the recipient — a phone number or a placeholder — and the sender number whose window is read.

The typical use is to send free-form text on the "open" path and an approved template on the other:

graph LR;
  A["Order completed"] --> B{"Window open?"};
  B -- "yes" --> C["Text message"];
  B -- "no" --> D["Template message"];

Loop

Walks a collection — the order's digital files, the purchased items — and runs the body actions once per item, with the {{ loop_* }} placeholders described in Placeholders.

Integrations with other systems

Both are described in Webhooks and HTTP requests.

Contacts

In the library's Contacts tab, since 2.5.0:

They need the Joinotify Cloud sync switched on and go through its queue, so the workflow never waits on Joinotify and a failure is retried. Neither of them starts a Joinotify Cloud flow.

The contact is the trigger's customer or user only when the phone or e-mail typed in the action is theirs; anyone else becomes a separate lead. Marketing consent should only be ticked when the trigger means the person agreed — a form with a consent checkbox, for example — and it goes out with the evidence of where and when.

WooCommerce

Artificial intelligence

AI goes through the WordPress AI Client: the provider and its credentials are set up once under Settings → Connectors, in WordPress itself, and Joinotify uses whatever is there. The plugin has not stored an OpenAI or Anthropic key since 2.3.1.

The builder also generates a whole workflow from a text description. That generator never uses the HTTP request action.

Other channels

Both need the integration enabled and the service's credential under Settings → Integrations.

Removed actions

Test before activating

The builder sends the workflow to a test number, set in the builder itself. When WhatsApp refuses the send, the notice shows the reason Meta gave — closed window, refused template, invalid number — instead of a generic error.

Your own action

Any plugin can register an action, with its settings form, with PHP alone — see Developer resources.