P&A Visual Workflow Automation

Description

Workflow Automation lets you automate WordPress without code. Pick a trigger, such as a form submission, a new post or a new user, then drag actions and logic onto a visual canvas. Your automations run on your own site, with no monthly task limit.

Why use Workflow Automation

  • Visual, no-code builder: snap blocks together and read an automation at a glance.
  • Unlimited and free: no limit on automations, blocks or runs.
  • Fast: automations run in the background, so visitors never wait.
  • Safe to try: Simulate with sample data sends nothing; Logs show what each block did.
  • Private: API keys are encrypted and only administrators can see them.

Automation ideas

  • Send Contact Form 7, WPForms or Gravity Forms leads to HubSpot, Salesforce or Pipedrive.
  • Create a Stripe customer when someone registers.
  • Turn a form into an Asana task for your team.
  • Email your team, or post to Microsoft Teams, when a post is published.
  • Send a WhatsApp Business message after a form is submitted.
  • Raise a Xero invoice from a form.

Triggers

  • WordPress: posts and pages published, edited or deleted; custom post types; new and updated users; comments; media uploads.
  • Forms: Contact Form 7, WPForms, Gravity Forms, Fluent Forms, Formidable Forms, Ninja Forms, Forminator, weForms, WS Form and Elementor Forms.
  • Schedule: hourly, daily or weekly.

Logic and actions

  • If / Else, Else if and Switch with AND / OR conditions; For each, Repeat and While loops; Filter, Wait and Exit.
  • Create, update or delete WordPress posts, set custom fields and terms.
  • Formatter, Variable, Lookup and Parse (JSON, CSV, XML, YAML) to shape data; Notify by email; Log a record.

Integrations

HubSpot, Salesforce, Pipedrive, Stripe, PayPal, Xero, Asana, Klaviyo, WhatsApp Business and Microsoft Teams, plus the AI provider connected to WordPress 7.0 or later. Stripe, Klaviyo and WhatsApp also have an API block for any endpoint.

How it works

  1. Workflow Automation Add New opens the canvas.
  2. Choose a trigger, then drag blocks under it.
  3. Simulate it with sample data.
  4. Publish: it runs whenever the event happens.
  5. Check Settings Logs.

Also: eight builder themes (dark and high contrast included), templates, saved groups, JSON import and export, undo and redo, translation ready, and WP-CLI (wp pawa).

Workflow Automation Professional

The paid Workflow Automation Professional plan adds more than 140 blocks. Start a 14-day trial from Workflow Automation Upgrade.

  • WooCommerce orders, products, customers, coupons and Subscriptions
  • Google Sheets, Drive, Calendar, Docs and Contacts
  • Slack, Discord, Telegram, Twilio, Zoom, Notion, Airtable, Trello, ClickUp, Shopify and QuickBooks
  • Mailchimp, ActiveCampaign, Brevo, MailPoet and FluentCRM
  • OpenAI, Anthropic Claude, Google Gemini, Groq and OpenRouter
  • MemberPress, Paid Memberships Pro, LearnDash, LifterLMS, Tutor LMS, BuddyBoss, bbPress, AffiliateWP, GiveWP, Easy Digital Downloads and The Events Calendar
  • Instant triggers from Stripe, PayPal, HubSpot, Shopify and more, and incoming webhooks
  • Parallel branches, Try / Catch, Approval steps, HTTP Request, HTML email and WordPress user management

External services

Workflow Automation has no tracking or advertising. It includes the Freemius SDK, which handles the optional opt-in, the Account page and plan upgrades (see Freemius below); it sends nothing unless an administrator opts in or opens an upgrade or account page. Every other service below is contacted only by its own blocks, and only after an administrator has connected an account for it under Workflow Automation Credentials. Until then nothing is sent to it.

A connected block sends a request to its service only when:

  • a published automation reaches the block (for example after a form is submitted);
  • an administrator uses Run live in the builder, or Test connection on the Credentials screen;
  • an administrator opens the block’s options and the builder loads choices from the account (audiences, pipelines); or
  • an access token has expired and is renewed (Salesforce, Pipedrive, Xero and HubSpot).

What is sent is the account’s credential, to authenticate, and the values the automation’s author put into the block’s fields, which can include data the automation received from your site or its visitors (for example a form submission). Simulate sends nothing. “Help links” are documentation links in the Block guide and the Credentials help: they open only when you click them, and nothing is sent to those sites. Name the services you use in your site’s privacy policy.

Freemius

Licensing and upgrades use the Freemius SDK. Nothing is sent unless an administrator opts in.

  • Data sent: on opt-in, the site address, WordPress, PHP and plugin versions, the administrator’s name and email, and the active plugins and theme.
  • When: after opt-in, on activation, deactivation, update and deletion, and when the Upgrade or Account page is opened.
  • Terms of service: Freemius Terms of Service
  • Privacy policy: Freemius Privacy Policy

Microsoft Teams

Posts a message to a Teams channel through the incoming webhook or Power Automate URL you save. Only Microsoft hosts are accepted: office.com (outlook.office.com, webhook.office.com), logic.azure.com, powerplatform.com, powerautomate.com.

  • Data sent: the message content, to your webhook URL.
  • When: the block runs, or Test connection.
  • Help links: www.microsoft.com, learn.microsoft.com
  • Domains: outlook.office.com, webhook.office.com, logic.azure.com, powerplatform.com and powerautomate.com (and any subdomain of them) are owned by Microsoft; the Microsoft terms and privacy statement below apply to them.
  • Terms of service: Microsoft Services Agreement
  • Privacy policy: Microsoft Privacy Statement

WhatsApp Business (Meta)

Sends text, template and media messages and fetches media through the Meta Graph API at graph.facebook.com. The WhatsApp API block calls any Graph API path you enter there.

  • Data sent: the recipient’s phone number, the message or template values, media links, your access token and phone number ID; for the WhatsApp API block, the path, query and body you enter.
  • When: the block runs, Test connection, or option lists (message templates).
  • Help links: business.whatsapp.com, developers.facebook.com
  • Domains: graph.facebook.com and developers.facebook.com are owned by Meta, the company behind WhatsApp; the WhatsApp Business terms and privacy policy below apply to them.
  • Terms of service: WhatsApp Business Terms of Service
  • Privacy policy: WhatsApp Privacy Policy

Asana

The Asana task, project and workspace blocks manage tasks, projects, sections, users and workspaces through the Asana API at app.asana.com.

  • Data sent: the task, project or section fields you map, and your personal access token.
  • When: a block runs, Test connection, or option lists.
  • Help links: asana.com, developers.asana.com
  • Terms of service: Asana Terms of Service
  • Privacy policy: Asana Privacy Statement

Klaviyo

Creates or updates a profile and tracks an event through the Klaviyo API at a.klaviyo.com. The Klaviyo API block calls any path of that API you enter.

  • Data sent: the profile fields (such as email, phone and name) and event properties you map, and your private API key; for the Klaviyo API block, the path, query and body you enter.
  • When: the block runs, or Test connection.
  • Help links: www.klaviyo.com, help.klaviyo.com, developers.klaviyo.com
  • Terms of service: Klaviyo Terms of Service
  • Privacy policy: Klaviyo Privacy Policy

HubSpot

The HubSpot contact, company, deal, ticket and association blocks manage CRM records through the HubSpot API at api.hubapi.com, which also renews tokens (api.hubapi.com/oauth/v1/token).

  • Data sent: the record fields you map (for example a contact’s email and name) and your access token; on renewal, your client ID, client secret and refresh token.
  • When: a block runs, Test connection, option lists (pipelines), or token renewal.
  • Help links: www.hubspot.com, developers.hubspot.com
  • Domains: api.hubapi.com is HubSpot’s own API domain, owned by HubSpot, Inc.; the HubSpot terms and privacy policy below apply to it.
  • Terms of service: HubSpot Customer Terms of Service
  • Privacy policy: HubSpot Privacy Policy

Salesforce

The Salesforce lead, contact, account, opportunity and case blocks sign in at login.salesforce.com (test.salesforce.com for a sandbox) and call your org’s My Domain host (yourorg.my.salesforce.com).

  • Data sent: the record fields you map and your access token; on renewal, your client ID, client secret and refresh token.
  • When: a block runs, Test connection, option lists, or token renewal.
  • Help links: www.salesforce.com, developer.salesforce.com, help.salesforce.com
  • Terms of service: Salesforce Legal (Master Subscription Agreement)
  • Privacy policy: Salesforce Privacy Statement

Pipedrive

The Pipedrive person, organization, deal, activity, lead and pipeline blocks call the API at api.pipedrive.com; tokens are renewed at oauth.pipedrive.com.

  • Data sent: the record fields you map and your API token or access token; on renewal, your client ID, client secret and refresh token.
  • When: a block runs, Test connection, option lists (pipelines, stages), or token renewal.
  • Help links: www.pipedrive.com, developers.pipedrive.com, pipedrive.readme.io
  • Domains: pipedrive.readme.io is Pipedrive’s API documentation, hosted by ReadMe; it is a help link only and nothing is sent to it.
  • Terms of service: Pipedrive Terms of Service
  • Privacy policy: Pipedrive Privacy Notice

Stripe

The Stripe customer, billing and catalog blocks manage customers, payment intents, invoices, products and prices through the API at api.stripe.com. The Stripe API block calls any path of that API you enter.

  • Data sent: the customer, invoice, product and price fields you map (for example a customer’s email), and your secret API key; for the Stripe API block, the path, query and body you enter.
  • When: a block runs, Test connection, or option lists.
  • Help links: stripe.com, dashboard.stripe.com, docs.stripe.com
  • Terms of service: Stripe Services Agreement
  • Privacy policy: Stripe Privacy Policy

PayPal

Creates, reads and captures orders and reads payments and the merchant through the REST API at api-m.paypal.com (api-m.sandbox.paypal.com in sandbox mode).

  • Data sent: the order amounts, currency and items you map, and your client ID and secret.
  • When: the block runs, Test connection, or option lists.
  • Help links: www.paypal.com, developer.paypal.com
  • Terms of service: PayPal User Agreement
  • Privacy policy: PayPal Privacy Statement

Xero

The Xero contact, invoice, payment, item and organisation blocks call api.xero.com; tokens are renewed at identity.xero.com.

  • Data sent: the contact, invoice, payment and item fields you map, your access token and tenant ID; on renewal, your client ID, client secret and refresh token.
  • When: a block runs, Test connection, option lists, or token renewal.
  • Help links: www.xero.com, developer.xero.com
  • Terms of service: Xero Terms of Use
  • Privacy policy: Xero Privacy Notice

The AI provider connected to WordPress

On WordPress 7.0 or later, the WordPress AI block sends a prompt through WordPress’s own AI Client to the provider the site owner connected under Settings Connectors. Workflow Automation does not choose the provider, store its key or contact it; WordPress does.

  • Data sent: the prompt, its instructions and any automation data in them.
  • When: the block runs.
  • Terms of service and privacy policy: those of the provider you connected, for example OpenAI (Terms, Privacy), Anthropic (Terms, Privacy) or Google (Terms, Privacy).

Links to WordPress.org and form plugin sites

The Block guides of the WordPress and form blocks link to WordPress or form plugin documentation. They open only when you click them; nothing is sent to these sites.

The WordPress blocks and the form plugin blocks work with plugins on the same site and send nothing off the site.

Addresses in the code that are names, not requests: some files contain web addresses that only identify a format. Nothing is ever requested from them: www.w3.org (the SVG namespace in the icon files), json-schema.org (the format of schemas/workflow.schema.json), schema.org (the @type and @context Microsoft asks for in a Teams message card) and www.gnu.org (the license link). assets/platforms/CREDITS.txt names where each platform icon came from (simpleicons.org, telegram.org, wordpressfoundation.org); those are credits, and the plugin does not contact them.

Screenshots

Installation

  1. Upload the pluginsandapps-workflow-automation plugin folder to wp-content/plugins/ (or install the zip via Plugins Add New Upload Plugin). The zip already includes the built canvas (dist/).
  2. Activate P&A Visual Workflow Automation.
  3. Open Workflow Automation in the admin menu, click Add New, and create your first automation.
  4. Connect accounts under Workflow Automation Credentials (Stripe, HubSpot, …) if you need those blocks. You must be an administrator (manage_options).

If you cloned the git repository instead of installing a release zip, the canvas will not load until a developer runs npm ci && npm run build in the plugin folder. Site owners should use the packaged zip.

FAQ

Is Workflow Automation free?

Yes. The plugin, every block listed above Workflow Automation Professional, and every run are free, with no limit on automations, blocks or runs.

Do I need to know how to code?

No. You build automations by dragging blocks onto a canvas and choosing options from menus. Values from the trigger, such as a form’s email field, are picked from a list.

Which form plugins does it work with?

Contact Form 7, WPForms, Gravity Forms, Fluent Forms, Formidable Forms, Ninja Forms, Forminator, weForms, WS Form and Elementor Forms. Each form, and each of its fields, appears in the builder once the form plugin is active.

Will it slow down my site?

Automations run in the background through WP-Cron after the event, so a visitor who submits a form does not wait for your CRM or payment service to answer. On a busy site you can run the queue from a real cron job with wp pawa work.

Can I test an automation before it goes live?

Yes. Simulate walks through the automation with sample data and sends nothing to any service. Run live runs it once for real, and Settings Logs shows what every block did.

Is there a limit on how many times an automation runs?

No. Workflow Automation does not limit automations, blocks, or runs. Check Workflow Automation Settings Automation Usage for how many runs the site started.

What does Workflow Automation store on my site?

Workflow Automation keeps a history of what your automations did, in your own WordPress database: which automation ran, when, what each block returned, and errors. That history can include data an automation received, such as the fields of a form submission or a user’s name and email address. Values whose field names look like secrets (passwords, tokens, keys) are masked in the history. Nothing in this history leaves your site.

  • How much is kept is your choice under Workflow Automation Settings Logs: “Errors only” (the default) keeps failed runs, “All” also keeps successful ones.
  • Old log entries are removed automatically, and you can delete entries or clear the log on the same screen.
  • Everything is removed with the plugin when you tick “Remove all Workflow Automation data from this site” under Settings Data.

If automations on your site handle personal data, say so in your privacy policy.

Can I reuse blocks in several automations?

To reuse blocks, build an automation with no trigger, then choose Save as group under it on the Automations list. It is listed on the Groups tab. In the builder, drag Select a saved group (the first item in the block list) to where the blocks should go, or click it, then pick the group: a copy of its blocks is added to the automation.

Where is the source code of the builder?

The source of the built canvas ships with the plugin (builder/ and each blocks/*/*/block.jsx), with package.json and vite.config.js: run npm ci && npm run build to rebuild dist/. Filters such as pawa_notify_recipient let your own code change what a block does.

Who can manage API credentials?

Only users with the manage_options capability (typically Administrators). The optional pawa_manage_capability filter can open the builder to another role, but credential secrets always require manage_options.

Can an automation create, change or delete user accounts?

Not in the free plugin. It has no block that creates, changes or deletes a user account, gives or removes a role, writes user meta, logs anyone out or sends a password reset. An automation can start when someone registers or updates their profile, and use that user’s fields (for example to send a welcome email), but accounts and roles are managed in Users. Publishing an automation that changes other people’s posts needs the WordPress capabilities for that (for example edit_others_posts), so a role the builder was opened to cannot do through an automation what it may not do in WordPress.

Can an outside service manage my site through Workflow Automation?

No. The free plugin starts automations only from events on your own site (a form submission, a new post, a user registering, a schedule). It has no endpoint that another server can call to start one, and every one of its REST routes requires a logged-in user who may manage automations. Workflow Automation does not install, activate or update plugins or themes, change site settings, or edit code.

Where do I see if an automation ran?

Workflow Automation Settings opens on the Display tab. Run history is under Workflow Automation Settings Logs. Failed live runs are recorded at the default “Errors only” level. Set the log level to “All” to also keep successful runs.

Can I change how the builder looks?

Yes. Workflow Automation Settings Display has a Theme dropdown: Default, Blueprint (a technical grid, crisp outlines, squared corners), Monochrome (black, white, and gray, with one accent color), Platform Logos (Default with each block’s platform logo on it), Puzzle Blocks (interlocking puzzle blocks on a light workspace), Midnight (a calm dark workspace), High Contrast (black on white with heavy edges, for low vision and bright rooms), or Flowchart (pill, rectangle and hexagon blocks joined by arrows). Save the theme, then open or reload the builder. A theme changes how the whole builder looks for every administrator (the block list, the blocks, the canvas, and the toolbar and panels around them); it does not change, save, or run any automation differently. Under the dropdown, Theme options lets you adjust the selected theme: the colors of Events, Control, Actions, and Integrations blocks, the canvas background color and pattern (none, dots, or grid, with its color and spacing), the block list background, block size on the canvas and in the block list, corners and edge, whether platform icons are shown on blocks (a WordPress block shows the WordPress logo; a platform without a logo yet shows its initials), and how a selected block and a drop target are shown. A theme only shows the options it supports. Each theme keeps its own options, so switching themes does not erase what you picked, and Restore theme default settings puts the selected theme back as it shipped without touching the others.

The canvas is blank. What now?

The production zip must include dist/assets/index.js. If you installed from git, build the canvas (npm ci && npm run build) or switch to the official zip. Workflow Automation shows an admin notice when that file is missing.

Can I import and export automations?

Yes. On the canvas, use Export JSON / Import JSON. Files use canvas schema version 1.

Does uninstall remove everything?

Only if you ask it to. By default, deleting the plugin keeps your automations, credentials, run history and settings in the database (only caches are cleared), so you can delete and reinstall it, for example while testing another plugin, without entering your API keys again. Deactivating the plugin never removes data.

To remove everything when the plugin is deleted, tick “Remove all Workflow Automation data from this site” under Workflow Automation Settings Data before you delete it. On multisite each site decides for itself. A site owner can also decide for every site in wp-config.php with define( 'PAWA_REMOVE_ALL_DATA', true ); (remove) or false (keep); the constant takes precedence over the checkbox.

Saved credentials are encrypted with your site’s security keys in wp-config.php. If those keys change before you reinstall, kept credentials can no longer be read and must be entered again.

When removal is on and nothing else still uses the data, deleting Workflow Automation removes its options (including the run tally), credentials, automations, templates, saved groups, logs, custom tables, cron events, and what its blocks stored (for example user tags). Unrelated posts and options are left alone. On multisite every site’s Workflow Automation data is removed, each site in its own context.

While another copy of Workflow Automation is still installed on the site, deleting one copy keeps the shared data, so the other keeps every automation; only caches are cleared. Deleting the last copy removes what is left.

Some triggers subscribe to a webhook at their service. Credentials are never removed while a webhook subscription made with them is still at its service. Deactivating the plugin deletes those subscriptions; if a service could not be reached then, uninstall keeps the record of what is left and the accounts that made it, and removes everything else, so that a reinstall can still delete them. The same rule applies when you delete an account: it stays until its webhooks are deleted.

What happens to an automation that uses a block this site does not have?

It is kept, but it is not started, and a notice and the log say which blocks are missing. Nothing is deleted: once the blocks are available again, the automation runs as before.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“P&A Visual Workflow Automation” is open source software. The following people have contributed to this plugin.

Contributors

Changelog

1.2.5

  • Licensing and plan upgrades through the Freemius SDK, with an optional opt-in (see External services). Nothing is sent unless an administrator opts in.
  • Factory reset under Settings Data deletes every saved credential, the webhooks each one made at its service, and every log. Automations, templates, run history and settings are kept.
  • New Stripe API, Klaviyo API and WhatsApp API blocks: call any endpoint of the service with your saved account (Read with GET, Send with POST, PUT, PATCH or DELETE), for what the other blocks do not do.
  • Suggested privacy policy text (Settings Privacy Policy Guide) says what the run history keeps, for how long, and where to delete it.
  • The puzzle-block builder theme is now called Puzzle Blocks.
  • Saved groups: an automation with no trigger can be saved as a group (Save as group on the Automations list, listed on the new Groups tab) and added to any automation with Select a saved group in the block list. Each copy gets its own block ids, references inside the group keep working, and changing or deleting a group never changes an automation.
  • Deleting logs verifies the request before reading which logs were sent, and a single log is deleted with the same check as a bulk delete.
  • The WordPress list table class is loaded only where a list table is declared.
  • Database queries pass table names through the %i placeholder of $wpdb->prepare().
  • Request values are unslashed before they are sanitized, and the weForms trigger no longer calls unserialize().

1.2.4

  • The builder uses the React that WordPress ships instead of bundling its own copy.
  • Requires WordPress 6.2 or later (the first version that ships React 18).

1.2.3

  • The WordPress Post block refuses attachments, WordPress’s own template and style types, and protected (_) post meta.
  • Block guides suggest only blocks that Workflow Automation itself includes.
  • External services: one entry per service with what is sent, when, and links to its terms of service and privacy policy.
  • WP-CLI commands act only as the user given with WP-CLI’s –user flag and refuse to run without one; the plugin never signs a user in.
  • Three integration blocks are no longer part of Workflow Automation.
  • For add-ons: the host keeps the service-side subscriptions an add-on trigger registers in step with the published automations, and removes them before the account is deleted or the plugin is deactivated. Workflow Automation itself has no trigger that receives requests from outside the site.
  • Rewritten connection help for credentials.
  • Deleting the plugin keeps your automations, credentials and settings unless you tick “Remove all Workflow Automation data from this site” on the new Settings Data tab (or set PAWA_REMOVE_ALL_DATA in wp-config.php).

1.1.0

  • Add-ons install beside Workflow Automation: an add-on adds its blocks, credentials and templates from its own folder and keeps its own version and updates.
  • An automation that uses a block that is not installed is not started, instead of stopping halfway.
  • The block list cached between requests is checked against the plugin folder, so a moved site, a staging copy or a changed set of blocks is always seen.
  • Uninstall: each block declares what it stores; on multisite every site is cleaned; data an installed add-on still uses is kept. Uninstall no longer leaves the event-map flag and a For Each check cache behind.
  • Each block declares the WordPress capabilities it needs; a published automation runs with the authority of the user who published it.
  • The Send Email block (custom emails with attachments) is no longer part of Workflow Automation; the Notify block still emails site users.
  • The WordPress User block is no longer part of Workflow Automation: an automation does not create, change or delete user accounts, roles, user meta or password resets. Automations can still start when a user registers or updates their profile.
  • Admin screens: notices after an action are signed with a nonce, each list action checks one nonce, posted values are sanitized where they are read, and every database query binds its values with placeholders.
  • Scheduled automations, the queue sweep and each inbound poller have their own schedules.
  • Microsoft Teams block: the webhook host must be a Microsoft domain (office.com, logic.azure.com, powerplatform.com or powerautomate.com) or a subdomain of one, never a name that only contains one.
  • The Automation Usage tally is stored as a plain, readable option instead of an encrypted one.
  • Internal: a smaller runner, one workflow normalizer, a class map for host classes, shared OAuth token refresh.

1.0.0

  • Initial version: a visual builder with triggers, control blocks and actions for WordPress, form plugins, email, notifications, and integrations (Microsoft Teams, WhatsApp, HubSpot, Salesforce, Asana, Pipedrive, Stripe, PayPal, Xero, and AI providers).
  • Simulate an automation with sample data before publishing it.
  • Run history with a step journal, retries, and recovery of interrupted runs.
  • Credentials stored encrypted; only administrators can add or edit them.
  • An automation never gives a role that can manage the site and never changes an administrator’s account.
  • WordPress AI block: uses the AI provider connected to WordPress 7.0 or later, with no AI key stored by the plugin.
  • Builder themes and theme options under Settings Display.
  • Export and import of automations as JSON.