Installation of the Workflow Automation Integration Bundle

The bundle requires Pimcore 2026.1 or newer and PHP 8.4 or 8.5. It builds automation blueprints from existing Datahub configurations, so Pimcore Datahub has to be installed and enabled as well.

caution

Composer pulls pimcore/data-hub in as a dependency, but a Composer dependency is not an installed bundle, and bin/console pimcore:bundle:install does not cascade to dependencies. Datahub ships its own installer, and that installer creates the plugin_datahub_config permission and the Datahub permission model this bundle reads. If Datahub is not installed in your project yet, install it before or alongside this bundle.

Bundle Installation

1. Install the package:

composer require pimcore/workflow-automation-integration-bundle

2. Enable the bundle in config/bundles.php. Add Datahub in the same step if it is not enabled yet:

use Pimcore\Bundle\DataHubBundle\PimcoreDataHubBundle;
use Pimcore\Bundle\WorkflowAutomationIntegrationBundle\PimcoreWorkflowAutomationIntegrationBundle;
// ...
return [
    // ...
    PimcoreDataHubBundle::class => ['all' => true],
    PimcoreWorkflowAutomationIntegrationBundle::class => ['all' => true],
    // ...
];

3. Run the installers:

bin/console pimcore:bundle:install PimcoreDataHubBundle
bin/console pimcore:bundle:install PimcoreWorkflowAutomationIntegrationBundle

Permissions

The installer registers a single user permission under the category Pimcore Workflow Automation Integration Bundle. Assign it in Pimcore Studio under user and role management.

Permission key	Label in user management	Effect
wai_configuration_permission	Automation Blueprints Configuration	Grants access to the Workflow Automation Blueprints view and to every endpoint of this bundle

The permission is enforced on the server: every controller of the bundle carries an IsGranted check, so a user without it is rejected even when calling the endpoints directly. The Pimcore Studio frontend uses the same permission to decide whether the main menu entry is rendered, and the entry additionally respects the perspective permission automationIntegration.workflowAutomationBlueprints.

Which Datahub configurations a user sees inside the view is governed by Datahub's own permission model (plugin_datahub_admin, the per-adapter permissions and the per-configuration permission sets), not by this permission. Inactive configurations are never listed.