Executing Requestador Actions in Pimcore: Overview and Methods

Once Requestador has been configured in Pimcore, actions can be executed directly from Pimcore in different ways depending on the use case.

Requestador actions can typically be started from:

• a Pimcore data object

• the grid view of a Pimcore class

• the Datahub Importer, when Requestador is used as part of an import workflow

The available execution method depends on how the Requestador configuration has been set up and how the workflow should be applied.

Use object-level execution when working on a single item, grid-based execution when processing selected records, and importer-based execution when Requestador should be part of a structured import process.

Before executing a Requestador action in Pimcore, make sure the following conditions are met:

• the Pimcore extension is installed

• the Requestador subscription is active

• the AI endpoint has been configured in Requestador

• the Requestador action has been created and tested

• the Pimcore Requestador configuration exists

• input and output mappings are configured correctly

If any of these prerequisites are missing, the action may not be available or may fail during execution.

Use the following approach as a guideline:

Use Data Object execution when:

• you want to work on one item

• you want to test a configuration manually

• immediate review on a single object is important

Use Grid View execution when:

• you want to process multiple selected objects

• you need controlled bulk execution

• the same action should be applied to a defined set of rows

Use Datahub Importer execution when:

• Requestador should be part of an import workflow

• enrichment should happen automatically during import

• you want to integrate AI processing into a repeatable ingestion process

• always test the AI endpoint and Requestador action before executing from Pimcore

• verify Pimcore mappings before running bulk actions

• start with a single object before executing on multiple rows

• confirm that required source fields are populated

• review generated output after execution, especially for new configurations

• use importer-based execution only after the configuration has been validated in standard Pimcore usage

Action is not available

Possible causes:

• no Pimcore Requestador configuration exists

• the Requestador action was not created

• the configuration is linked to a different Pimcore class

Action starts but no fields are updated

Possible causes:

• response field mapping is incorrect

• the action returns different field names than expected

• localized target language is not configured correctly

Action fails for some objects in grid view

Possible causes:

• some selected objects do not contain required input fields

• source data quality differs across records

• one or more objects are missing mandatory values

Importer execution does not return expected enrichment

Possible causes:

• importer data does not match the expected Requestador inputs

• wrong Requestador configuration was selected

• the Requestador configuration was not tested before using it in the importer

Requestador actions can be executed in Pimcore from three main entry points:

• directly from a data object

• from the grid view for selected rows

• from the Datahub Importer as part of an import workflow

Each method supports a different operational scenario, but all depend on the same foundation: a working Requestador action and a correctly configured Pimcore Requestador mapping.

The recommended approach is to first test on a single object, then move to grid-based or importer-based execution once the configuration has been verified.