onesignal-rust-api 5.12.0

A powerful way to send personalized messages at scale and build effective customer engagement strategies. Learn more at onesignal.com
Documentation
# JourneyCondition

## Properties

Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**kind** | **String** | Condition kind. Selects which other fields apply. | 
**included_segment_ids** | Option<**Vec<String>**> | segment_membership conditions: Segment UUIDs the user must belong to. | [optional]
**excluded_segment_ids** | Option<**Vec<String>**> | segment_membership conditions: Segment UUIDs the user must not belong to. | [optional]
**action** | Option<**String**> | on_notification_action conditions: the notification action to branch on. Which actions apply depends on the sending node's channel. | [optional]
**sending_node_id** | Option<**String**> | on_notification_action conditions: id of the sending node this action refers to. Returned on reads; accepted on write. | [optional]
**client_node_id** | Option<**String**> | on_notification_action conditions: write-only alternative to sending_node_id. References the sending node by its client_node_id. | [optional]
**name** | Option<**String**> | event_trigger conditions: event name, up to 255 characters. | [optional]
**attributes** | Option<[**Vec<Vec<crate::models::JourneyEventAttribute>>**]array.md> | Event attribute matchers, as a list of condition groups. Send a single group whose conditions are AND'd together. More than one group is rejected. | [optional]
**entry_event_match_attributes** | Option<[**Vec<serde_json::Value>**]serde_json::Value.md> | event_trigger conditions: match incoming event properties against the journey's entry event. Only valid on event-triggered journeys. | [optional]

[[Back to API list]](https://github.com/OneSignal/onesignal-rust-api#full-api-reference) [[Back to README]](https://github.com/OneSignal/onesignal-rust-api)