=== WP Connectr: Power Automate integration ===

Contributors: nhance, reenhanced
Tags: power automate, microsoft flow, logic apps, microsoft, dataverse
Requires at least: 6.8
Tested up to: 6.9
Requires PHP: 7.4
Stable tag: 2.4.1
License: GPLv2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html
Connect WordPress to Microsoft Power Automate with this certified connector.

== Description ==

Connect your WordPress site to over 1000 services through Microsoft Power Automate. Microsoft certifies this Power Automate connector for WordPress.
Power Automate is a Microsoft low-code service. Use flows to copy files, receive notifications, and collect data between applications and services.

Power Automate provides workflow automation, similar to Zapier, IFTTT, and Integromat.

Connector use requires a Power Automate premium license. You can start a free trial at https://make.powerautomate.com/

Reenhanced is a Microsoft partner. The company started in 2005 and connects WordPress to Microsoft products.
Our products serve over 250,000 users around the world.

This plugin is open-source. Your team can examine its source code. Reenhanced provides support.
The free plugin does not require an external service other than Power Automate. Pro uses a separate service for license validation and updates.
Protect connection credentials and restrict access. Test updates before you install them on a production site.

Use the provided actions with this plugin to:

- Manage WordPress users.
- Manage posts, including supported custom post types.
- Manage attachments and upload files to the Media Library.
- Manage comments.
- Manage taxonomies.
- Manage terms.
- Use supported Advanced Custom Fields (ACF) and Secure Custom Fields integrations.

**WP Connectr Pro: Power Platform solutions**
WP Connectr Pro is a separate add-on. It requires free WP Connectr and an active ACF-compatible plugin, even if you do not import solutions. The bootstrap accepts ACF, ACF Pro, or Secure Custom Fields (SCF). The installed version must provide the APIs each workflow needs. ACF Pro is not a blanket requirement. Pro 4.0.0 declares PHP 8.1 or later.
Get Pro at https://reenhanced.com/product/wp-connectr-pro/

WP Connectr Pro provides these functions:
- Import solution definitions into new or existing post types or user-role field groups.
- Generate selected Dataverse-to-WordPress flows for eligible imported definitions.
- Map supported Dataverse columns to WordPress attributes and ACF fields.
- Load CSV records and migrate selected definitions between WordPress sites.
- Deliver supported WordPress events to Power Automate flows.

Test the required ACF APIs and field types in your installed version. Do not assume that every compatible-fields plugin provides the same APIs.
Generated flows transfer data from Dataverse to WordPress. Reverse synchronization requires a separate flow and controls to prevent repeated updates between systems.

New imported post types are non-public and not publicly queryable. REST access uses the protected wp-connector/v1 namespace. They use standard post capabilities, not isolated per-table permissions. Existing types keep their visibility and access settings; re-imports and plugin updates do not make them private. CSV post import defaults to Published, and generated post sync creates published records. Review status separately from type visibility.

Build the frontend with established WordPress themes, page builders, blocks, or PHP. Configure roles and server-side record access before exposing data. Pro supplies starter templates and an advisory Security report, not a complete frontend or Dataverse security.

To see how Pro works, open **Power Automate > Usage Guide** and read the Pro overview guide. Pro adds a full site-building guide to the Usage Guide. To try Pro on a demo site, [start a trial at wpportals.com](https://wpportals.com/request-a-demo/).

== Frequently Asked Questions ==

= How do I import a Power Automate solution? =
Solution import requires WP Connectr Pro. Get Pro at https://reenhanced.com/product/wp-connectr-pro/.

1. Activate free WP Connectr and an ACF-compatible plugin with the required APIs. Install and activate Pro, then activate its license.
2. On Power Automate > Solutions, analyze the solution ZIP. Review tables, columns, targets, and mappings before importing. This creates definitions, not records.
3. Load initial records on Import Data. We recommend [Record Exporter for Dataverse](https://record-exporter.reenhanced.com/) for CSV preparation. Preserve primary GUIDs and test a small import.
4. On Solutions > Generate Solution, select eligible components and preview flows and written columns. Remove create-only bulk flows for CSV-loaded records.
5. Import the generated ZIP into Power Platform. Bind connections and check activation immediately. Keep unreviewed flows off. Test matching, updates, and deletion before enabling production sync.
6. Build the frontend with established WordPress tools. Design and test access before exposing records or fields.

For account mappings, read the user targets and roles section of the Pro site-building guide in **Power Automate > Usage Guide**. Provisioning does not provide SSO or automatic account revocation.

= Can I edit imported fields in ACF? =
Yes. Pro imports field groups into ACF. Open Custom Fields > Field Groups to edit them in ACF.

= Can I use triggers? =
WordPress event triggers require WP Connectr Pro. The free plugin alone does not deliver these events.

= How do I get WP Connectr Pro? =
Purchase WP Connectr Pro at https://reenhanced.com/product/wp-connectr-pro/.
Pro extends the free plugin with solution import, flow generation, and supported WordPress event triggers.

= Why are my custom post types missing? =
The plugin discovers custom post types that have REST access enabled.
Add this setting to your custom post type registration:
```php
'show_in_rest' => true,
```

Your post type registration page can also provide this setting. Review the REST namespace and permissions before enabling it. Under the usual wp/v2 namespace, published records can become readable without authentication. Pro's REST override enables REST but does not move the type into the protected connector namespace.
Check the connection user's permissions before you test the resource. Read the security and access guide in **Power Automate > Usage Guide**.

= How can I get support? =

Send support requests to [support@reenhanced.com](mailto:support@reenhanced.com).

== Changelog ==

2026-10-23 - version 2.4.1
* Added the wp_connectr_guide_slugs and wp_connectr_guide_instance filters. A plugin can add its own guide to the Usage Guide. WP Connectr Pro uses these filters for the taxonomy frontend guide

2026-10-22 - version 2.4.0
* Added the wp_connectr_post_types filter. A plugin can make a post type available in Power Automate without turning on show_in_rest, so the public REST API does not change
* WP Connectr now requires WordPress 6.8 or later and PHP 7.4 or later
* Fixed meta_key, meta_value and meta_query filters having no effect on post types that a plugin adds to WP Connectr after init
* Fixed an error when Power Automate reads one post type from the post types resource
* Security: the public wp/v2 posts and users routes no longer accept the meta query parameters of WP Connectr. Only WP Connectr routes filter by meta values

2026-09-15 - version 2.3.2
* Fixed ACF fields assigned to all user roles, or to the user form, not appearing in Power Automate for users and role-specific user resources in WP Connectr Pro
* Fixed ACF location rules so every rule in a location group must match. Fields scoped to one user role no longer appear on other roles
* Fixed ACF field values missing from list results for posts, taxonomies, users and comments
* Fixed ACF fields missing from single item results for taxonomies and comments
* Fixed a server error on user resources when another plugin's field, such as Elementor's, returns a value that contradicts its own schema. Power Automate now receives an empty object or array of the declared type instead
* Fixed a critical error on WP Connectr requests authenticated with an application password when no user was logged in. Invalid application passwords now return a permission error
* WP Connectr now requires WordPress 5.6 or later
* Removed the ReEnhancements admin page

2025-10-06 - version 2.3.0
* Enhanced ACF field retrieval with alternative request schema support for improved compatibility

2025-09-19 - version 2.2.0
* Added meta query support for users and posts - filter by custom fields using meta_key, meta_value, meta_compare, and complex meta_query parameters
* Enhanced REST API with advanced filtering capabilities for Power Automate workflows

2025-09-17 - version 2.1.1
* Added support for users with specific roles as resources in WP Connectr Pro - enables importing Dataverse users with role-based access

2025-09-16 - version 2.1.0
* SECURITY: Added authentication requirements for all API endpoints - users must have wp_connectr_manage, wp_connectr_use_actions, or administrator capabilities

2025-09-12 - version 2.0.3
* Improved term creation to act as lightweight upsert - returns existing term instead of error when term already exists

2025-09-08 - version 2.0.2
* Enhanced enum value normalization with optional null support for better Power Automate compatibility

2025-08-19 - version 2.0.1
* Resolves an issue with the plugin publishing process that caused issues with the plugin installation from the plugin directory.

2025-06-26 - version 2.0.0
* Support for solution import/export through the new WP Connectr Pro plugin

2025-04-22 - version 1.4.0
* Adds password generation and email notification for new user creation

2025-03-27 - version 1.3.2
* Additional updates to support the upcoming WP Connectr Pro. Make sure you have the latest version if you are using the pro version.

2025-03-06 - version 1.3.1
* Just a small fix for upcoming pro version support. Adds ability to use any action hook as trigger.

2025-02-28 - version 1.3.0
* Added dynamic schema support for trigger topics
* Added dynamic fetch endpoint for upcoming new action in connector (GetItemV2)

2025-02-24 - version 1.2.0
* User responses now contain much more data

2025-02-17 - version 1.1.1
* Resolves some incorrect naming in the plugin.


For other changes, see changelog.txt
