Skip to main content
Version: 2026.2

Work with Workflow Automation Integration

Open Automation & Integration > Workflow Automation Blueprints from the main menu in Pimcore Studio. The entry requires the wai_configuration_permission permission, see Installation.

Automation Blueprints AccessAutomation Blueprints AccessAutomation Blueprints Access

Download Automation Blueprints​

The Workflow Automation Blueprints view lists the active GraphQL and webhook endpoints configured in Pimcore Datahub that the user is allowed to read. A configuration only appears if at least one blueprint can be built from it:

  • For GraphQL endpoints, the Query Schema must contain at least one Entity, or the Mutation Schema must have Update enabled for an entity or for assets.
  • For webhook endpoints, the configuration must have a Schema defined for Data Object and listen to at least one of the pimcore.dataobject.postAdd and pimcore.dataobject.postUpdate events.

Datahub Configs available for WAIDatahub Configs available for WAIDatahub Configs available for WAI

For each item in the list, you can download automation blueprints in a JSON file - that you can further import and execute in n8n - from the right dropdown menu. The options available in this menu depend on your endpoint's type and Schema Definition.

GraphQL Blueprints​

For a GraphQL endpoint you can download blueprints to:

  • n8n Export *Object*: Export the attributes of Data Objects corresponding to an Entity defined in your Query Schema Gear IconGear IconGear Icon in a spreadsheet. A workspace with Read permission must be defined for Data Objects in Security Definition.
caution

The export only picks up Query Schema columns whose data type is one of the following. Localized fields are included when their underlying data type is in the list. Operator columns and columns addressing nested structures (object bricks, field collections, classification store) are skipped, and every other attribute of the Query Schema is left out of the resulting spreadsheet.

  • System fields, for example ID and Key/Path
  • Input
  • Textarea
  • WYSIWYG
  • Select
  • Number
  • Checkbox
  • Date
  • Date & Time
  • Time
  • n8n Update *Object*: Update the first text field of Data Objects corresponding to an Entity listed in your Mutation Schema with the Update option enabled. The blueprint appends _edited_by_N8N to the current value. A workspace with Update permission must be defined for Data Objects in Security Definition.
  • n8n Update Asset: Update the first text (input) metadata field of Assets. This option appears when Update is enabled for Asset in the Generic Types section of the Schema Definition. The blueprint appends _updated_by_N8N to the current value. A workspace with Update permission must be defined for Assets in Security Definition.

Available options for GraphQL endpointAvailable options for GraphQL endpointAvailable options for GraphQL endpoint

Webhook Blueprints​

For a Data Objects-focused webhook endpoint, you can download a Process Item blueprint to listen to your webhook, update your Objects' first text attribute and write the corresponding data in a spreadsheet.

Your webhook Datahub configuration needs:

  • to have an Entity defined in Schema Definition Data Objects;
  • to listen to pimcore.dataobject.postUpdate or pimcore.dataobject.postAdd.

When downloading your automation blueprint, add a valid webhook URL of your n8n instance in the related field. The URL is validated against ^(https?:\/\/)([a-zA-Z0-9.:\/-]+)(\/webhook|\/webhook-test)$ and therefore consists of:

  • the http:// or https:// protocol;
  • the host name of your n8n instance, optionally with a port and a path;
  • a trailing /webhook or /webhook-test segment, with no slash after it. n8n uses /webhook-test for testing.

For example, a webhook URL could be: https://pimcore.com/non-example/webhook-test.