Multiple Structures for Offers and Integrations

Often you have almost identical structures for different products.

  • In 99% of cases the structure is the same, only one field is different.
  • Copying and maintaining two entire structures (including all modifications) is inefficient and error-prone.
  • You still want to use them inside the same integration without duplicating effort.

Solution

PalDock supports linking an Offer or an Integration to multiple structures.

  • When listing fields in integrations, fields are deduplicated by name.
  • This means:
    • An Offer can contain multiple structures.
    • An Integration can also work with multiple structures.
  • When a lead arrives from Structure A, which is almost identical to Structure B, PalDock does not rely on the structure ID. It uses the field names instead.
  • As long as field names are consistent across structures (with the system name matching, ensured by the admin), the integration processes the lead correctly.
  • Since a lead always comes from exactly one structure, field mapping is needed only on the field name, not on a per-structure basis.
  • As a result, leads from any linked structure are processed seamlessly as long as field names match.

We recommend using global fields whenever possible. If a required field is missing, use local or custom fields as needed.

Related articles

HTTP Element > Timeout
HTTP Element > Field format
Element types > HTTP Element
Element types > Flow Control
Tool Elements > Mirror
Tool Elements > Set Event
Tool Elements > Set Variable
Tool Elements > Modify Request
Tool Elements > Modify field in Connection Creator
Element types > Tool Elements

Insights that
helps you grow