{"id":"msg.automations","app":"msg","title":"Triggers, conditions, actions and timing","summary":"Build a matching rule with explicit scope and predictable execution timing.","url":"https://www.simultem-apps.com/wiki/msg#automations","apiUrl":"https://www.simultem-apps.com/api/wiki/v1/articles/msg.automations","resourceUri":"wiki://msg/automations","revision":"2026-11-02.1","lastReviewedAt":"2026-11-02","keywords":["webhooks","reservation created","arrival","departure","recurring","delay","conditions","filters"],"sections":[{"title":"Create a reservation or event automation","steps":["Choose the reservation/event source supported by the editor.","Select the included properties and configure the conditions and exclusions offered for that source.","Check field paths, operators and values, including how grouped conditions combine.","Choose when to send: the offered event delay, reference-date offset or scheduled execution time.","Preview the audience/conditions, name the rule and save it in the intended enabled state."],"notes":[]},{"title":"Use a recurring property schedule","steps":["Choose a recurring trigger, included properties, recurrence and time zone. A weekly recurrence offers a weekday selector, such as Friday.","Understand the scope: each occurrence creates one event per eligible property and supplies property context. It does not enumerate the hotel’s in-house reservations or guests.","Configure a recipient supported by that property context and test the actual channel and rendered recipient.","Use a supported reservation-specific rule when the message requires a guest’s address or reservation tokens. Confirm a suitable guest-audience workflow with support before planning a weekly broadcast to all staying guests."],"notes":["Recurring rules do not expose the normal reservation condition controls. A weekly schedule alone is not an in-house guest broadcast.","A missing rendered recipient can prevent sending. A property-level run is not proof that any particular guest received a message."]},{"title":"Validate the behavior","steps":["For a reservation/event rule, use one reservation that should match and one that should not. For recurrence, test the property event and its explicitly configured recipient.","Wait for the relevant event or schedule and inspect Logs.","If a message is skipped, check scope, conditions, timing, channel and recipient data before duplicating the rule."],"notes":["Saving a rule does not guarantee that historical events are replayed. Check the preview and trace for the actual trigger."]}],"text":"# MSG: Triggers, conditions, actions and timing\n\nBuild a matching rule with explicit scope and predictable execution timing.\n\n## Create a reservation or event automation\n\n1. Choose the reservation/event source supported by the editor.\n\n2. Select the included properties and configure the conditions and exclusions offered for that source.\n\n3. Check field paths, operators and values, including how grouped conditions combine.\n\n4. Choose when to send: the offered event delay, reference-date offset or scheduled execution time.\n\n5. Preview the audience/conditions, name the rule and save it in the intended enabled state.\n\n## Use a recurring property schedule\n\n1. Choose a recurring trigger, included properties, recurrence and time zone. A weekly recurrence offers a weekday selector, such as Friday.\n\n2. Understand the scope: each occurrence creates one event per eligible property and supplies property context. It does not enumerate the hotel’s in-house reservations or guests.\n\n3. Configure a recipient supported by that property context and test the actual channel and rendered recipient.\n\n4. Use a supported reservation-specific rule when the message requires a guest’s address or reservation tokens. Confirm a suitable guest-audience workflow with support before planning a weekly broadcast to all staying guests.\n\nNote: Recurring rules do not expose the normal reservation condition controls. A weekly schedule alone is not an in-house guest broadcast.\n\nNote: A missing rendered recipient can prevent sending. A property-level run is not proof that any particular guest received a message.\n\n## Validate the behavior\n\n1. For a reservation/event rule, use one reservation that should match and one that should not. For recurrence, test the property event and its explicitly configured recipient.\n\n2. Wait for the relevant event or schedule and inspect Logs.\n\n3. If a message is skipped, check scope, conditions, timing, channel and recipient data before duplicating the rule.\n\nNote: Saving a rule does not guarantee that historical events are replayed. Check the preview and trace for the actual trigger.","related":[{"id":"msg.customer-journeys","app":"msg","title":"Customer journeys and stages","summary":"Organize communication around the guest’s stay.","url":"https://www.simultem-apps.com/wiki/msg#customer-journeys","apiUrl":"https://www.simultem-apps.com/api/wiki/v1/articles/msg.customer-journeys","resourceUri":"wiki://msg/customer-journeys","revision":"2026-11-02.1","lastReviewedAt":"2026-11-02"},{"id":"msg.logs","app":"msg","title":"Delivery logs, automation traces and troubleshooting","summary":"Find where a rule stopped: trigger, match, timing, rendering or delivery.","url":"https://www.simultem-apps.com/wiki/msg#logs","apiUrl":"https://www.simultem-apps.com/api/wiki/v1/articles/msg.logs","resourceUri":"wiki://msg/logs","revision":"2026-11-02.1","lastReviewedAt":"2026-11-02"},{"id":"bulk.automations","app":"bulk","title":"Build event-driven and recurring Bulk automations","summary":"Combine a trigger, conditions, an action and execution timing.","url":"https://www.simultem-apps.com/wiki/bulk#automations","apiUrl":"https://www.simultem-apps.com/api/wiki/v1/articles/bulk.automations","resourceUri":"wiki://bulk/automations","revision":"2026-11-02.1","lastReviewedAt":"2026-11-02"},{"id":"platform.reservation-changes","app":"platform","title":"Coordinate arrival changes and room moves","summary":"Check reservation, messages, preparation tasks and door access after a date or unit changes.","url":"https://www.simultem-apps.com/wiki/platform#reservation-changes","apiUrl":"https://www.simultem-apps.com/api/wiki/v1/articles/platform.reservation-changes","resourceUri":"wiki://platform/reservation-changes","revision":"2026-11-02.1","lastReviewedAt":"2026-11-02"}]}