Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.alumio.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

The Customer Attribute Subscriber is a configuration-based subscriber that listens for customer attribute data from a Magento 2 source system. It replaces the deprecated prototype-based magento-2-customer-attribute-subscriber previously used in the Legacy Magento 2 Connector.
This component has been migrated from a prototype-based implementation to a configuration-based setup as part of the Legacy Magento 2 Connector replacement project.

​
Prototype vs Configuration-based

This is an important behavioral difference to understand before setting up this component.
Prototype-basedConfiguration-based
ReusabilityCan be reused across different flows by changing a few fieldsNot reusable across different purposes or payloads
FlexibilityOne prototype can serve multiple use cases(Not always) Each use case requires its own dedicated configuration
How to reuseModify fields directlyDuplicate the configuration and adjust as needed
If you need to handle a different payload structure or use case, you must duplicate this Subscriber and adjust the configuration accordingly. Do not modify an existing configuration as another Route already uses it.

​
Type

Subscriber

​
Purpose

This Subscriber listens to incoming customer attribute data from Magento 2 and triggers the appropriate Route for further processing. It is used in flows where customer data or custom attributes need to be synced or mapped to a target system.

​
Configuration

ParameterDescriptionRequired
store_codeThe Magento 2 Store CodeYes
http-clientThe HTTP Client Authentication method used to connect to Magento 2Yes
entity-schemaThe specific schema for the entityNo

​
Usage

  1. Navigate to Subscribers in your Alumio environment.
  2. Search for Magento 2 Customer Attribute Subscriber.
  3. Configure the required parameters as described above.
  4. Attach this Subscriber to the relevant route as the Incoming configuration.

​
Deprecated VS New

An example of the deprecated configuration:
Image
An example of the new configuration:
Image

​
Notes

  • Replaces the prototype: magento-2-customer-attribute-subscriber
  • Unlike the prototype-based implementation, this configuration-based subscriber is not reusable across different purposes or payloads. If you need to handle a different payload structure or use case, you must duplicate this Subscriber and adjust the configuration accordingly.
  • Commonly used in customer attribute data sync flows between Magento 2 and ERP or CRM systems.