Skip to main content

Pimcore to iPaaS.com Webhook Message Mapping Documentation

The required Pimcore webhook message collection that receives and routes every incoming Pimcore webhook, underpinning automatic transfers to iPaaS.com.

Summary

This document describes the Pimcore Required Webhook Message collection — a required system collection that underpins webhook (automatic) transfers for the whole integration. Every webhook Pimcore sends to iPaaS.com arrives first as a message handled by this collection, and is then translated into the appropriate data type (Product, Product Category, Product Variant, and so on). Because all webhooks pass through it, this collection is a shared prerequisite for automatic transfers on every other Pimcore collection.

How the Integration Works

When a record changes in Pimcore and a Datahub webhook fires, iPaaS.com does not receive a finished Product or Category directly. Instead:

  1. The webhook arrives at iPaaS.com and is recorded as a message by this collection.

  2. The integration reads the message, identifies which Pimcore record changed, and retrieves the full record from the Datahub GraphQL API.

  3. The record is routed to the appropriate mapping collection (for example, the Product or Product Category collection) and transferred.

This collection is therefore part of the plumbing that makes automatic transfers work — not a collection subscribers configure or map data through.

Requirement

  • Do not delete this collection. If it is removed, incoming Pimcore webhooks can no longer be received and translated, and automatic transfers stop working for every other collection. This is why the collection ships with a name that flags it as required.

  • No subscriber configuration is needed. Its mappings carry shipped system defaults and do not need to be edited for a normal implementation.

  • Manual Sync on the individual data collections (Product, Product Category, and so on) does not depend on this collection; only the automatic, webhook-driven path does.

Mapping Collection Status

Enabled, with no mapping filter. It processes the webhook messages it receives.

Mappings

Pimcore Required Webhook Message

The collection sets four message fields to shipped system defaults. These are not subscriber-configured.

Mapping Type

Source (Pimcore)

Destination Field (iPaaS.com)

Description

Dynamic Formula

current time plus an offset

ExpirationTime

System default. Sets when the message expires (the example uses the current time plus 30 minutes).

Static

"Info"

Severity

System default. The message severity level.

Dynamic Formula

composed message text

Text

System default. A human-readable message such as "Hook arrived for <class> with id <id>".

Static

"Transfer"

Type

System default. Identifies the message as a transfer message.

Related Documents

Did this answer your question?