Adobe App builder ingtegrate with Adobe commerce "addresses": "\Magento\Customer\Api\Data\AddressInterface[]", empty address problem

Hi,

Please check the Official Slack community of Magento. Many developers are active to answer your queries.

Refer the article for better understand: Want to Join Magento Open-Source Community?

Thank you.

Hi ​@KrishnaMa11 ,
addresses is empty by design in the customer events you’re subscribing to – it’s not a bug in App Builder or the starter kit.
In Adobe Commerce:

• The customer events (like observer.customer_save_commit_after) only contain:
  • Core fields (email, firstname, lastname, dob, etc.)
  • Pointers: default_billing, default_shipping (address IDs) They do not embed the full address objects.
• The actual address data is emitted in separate events:
  • observer.customer_address_save_commit_after
  • observer.customer_address_delete_commit_after …with fields like entity_id (address id), parent_id (customer id), etc.

Because of this, adding "addresses" to scripts/commerce-event-subscribe.json for a customer event will always give you addresses: [].

Pick one of these patterns:

• Stay event‑driven
  • Keep your current customer event subscription (with middlename, dob, etc.).
  • Add separate subscriptions for address events:
    • observer.customer_address_save_commit_after
    • observer.customer_address_delete_commit_after
  • In your App Builder action:
    • Use parent_id (customer_id) from address events to attach/update addresses for that customer in your own storage.
    • Use default_billing / default_shipping from the customer event (IDs) to know which address is default.
• Fetch addresses via API when you get a customer event
  • Remove addresses from commerce-event-subscribe.json for customer events.
  • When your App Builder action receives a customer event:
    • Read customer_id (or entity_id) from the payload.
    • Call Commerce REST/GraphQL from App Builder to fetch the customer’s addresses on demand.

Either way: you cannot get populated addresses directly on the customer event; you must use address events or an extra API call.

Thanks,
Amit