In Pimcore, open Datahub and create or locate a GraphQL configuration. Note its name — you will enter it in iPaaS.com later as the Datahub Config.

2. On the Schema Definition tab, add the query schema for the top-level classes you will integrate — your product and product category classes (for example, Car as the product and Category as the product category). Only top-level entities need to be added here.

3. For each class, open its field settings and add every field the integration will use. Ensure the system fields ID and classname are included for each class — the integration requires them to build the external ids that link records together.

4. On the Security Definition tab, create or note an API key, and add the object paths for the data objects you will use under Workspaces / Objects. If you will use the image URL or image id functions, also grant read permission to the asset paths in use.

5. Keep introspection enabled during setup. Introspection is used to discover field names and paths while you configure the integration; it is not required by the integration once configuration is complete, and it is not recommended to check Disable Introspection during implementation.

Copy your iPaaS.com subscription webhook key from the subscription settings page in iPaaS.com. (Create the subscription first — see Part 3 — if you have not already.)

2. In Pimcore, create or identify a Datahub webhook configuration. Refer to the Pimcore documentation for how to create a webhook configuration if needed.

3. On the Events tab, add the events pimcore.dataobject.postAdd and pimcore.dataobject.postUpdate. 4. Under Schema Definition → Data Objects, include the classes you will receive notifications for.

5. On the Subscribers tab, build the subscriber URL by combining the iPaaS.com webhook endpoint with your webhook key in a key query-string parameter. Use the endpoint for your iPaaS.com environment: - Staging: https://stagingapi.ipaas.com/hookapi/v2/dynamic/Pimcore.v2?key=YOUR_WEBHOOK_KEY - Production: https://api.ipaas.com/hookapi/v2/dynamic/Pimcore.v2?key=YOUR_WEBHOOK_KEY 6. Enter the resulting URL in the Subscribers list and press enter.

Check the Active checkbox to enable the webhook, then save the configuration.

In iPaaS.com, go to Subscriptions and click Search Certified Integration Marketplace and Subscribe.

Click the Pimcore integration tile.

Click Subscribe.

Enter a Name for the subscription and select a Version. Use a name that is unique and meaningful within your company.

Leave Create Default Mappings checked (recommended) to install the example mapping collections that demonstrate the integration. Uncheck it only if you intend to build every mapping yourself.

6. Enter the subscription settings. The connection fields (API URL, API Key, Datahub Config) and the class-name settings are described in detail, with examples, in the Pimcore Connections and Settings article. Enter the values from the Datahub configuration you set up in Part 1.

7. Review the throttling settings, which come pre-populated with recommended defaults: - API Throttle Limit — the number of requests allowed within the throttle window. Recommended values: 5 for initial setup, 500 for ongoing operations. - API Throttle Seconds — the throttle window, in seconds. Default: 60. - Concurrent Connections and Concurrent Batch Executions — control how many requests run at once; leave the pre-populated defaults unless you have a reason to change them. See the Subscription Configuration – Edit article for details. 8. Click Apply to save the settings.

Data Sync Test: From the iPaaS.com Manual Sync page, transfer a sample product by entering its Pimcore record id, and confirm the product is created in iPaaS.com with its expected fields, variants, and category assignments.

Webhook Test: Update a product in Pimcore and confirm the change transfers to iPaaS.com automatically.

Review logs: Open Dashboard → Integration Monitoring → Error Logs in iPaaS.com to confirm there are no errors from the test transfers.