Philia: Update User Attributes
AI-generatedSummary
Posts a user-attribute event to Philia for each incoming item. The implementation reads a payload parameter to build each request, although the operation’s declared properties expose only Segment ID, Name, and Text; those fields are not used directly in the request builder.
Inputs
- Segment ID (required) — Declared required string. The implementation does not read this field directly.
- Name (required) — Declared required string. The implementation does not read this field directly.
- Text (required) — Declared required string. The implementation does not read this field directly.
- payload — The implementation reads this node parameter for each item and sends it as the POST body. It is not included in the supplied operation properties.
- Philia API credentials (required) — Requires the
philiaApicredential, including its base URL and API key.
Output shape
A list of items, one per input item, each containing json.request and json.response.
Sends each payload to
/v1/api/integration/flow-state/event/add/using POST. The API key is exchanged for a bearer token before requests are made. The response value is the Philia API response.