feat: Expand push_data guidance in Reservation Automations guide#1197
Merged
Conversation
Add to section 3 (Push reservation data): - Update examples for changing reservation time and assigned space - Guidance to use a stable reservation_key not derived from underlying resources, plus the delete-before-update pattern when the key must change - Recommendation to push only confirmed reservations to reduce unneeded hardware operations and avoidable errors Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add a "Bookings that span multiple rooms" subsection: push one reservation per sub-reservation, keyed by <reservation_id>_<sub_reservation_id> with each sub-reservation's own space, so each room's access stays independently addressable for updates and delete_data. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Restructure section 2 around the Console's Automation Rules model: - Organize the access-method settings under a "When a reservation is created" rule and document the drag-to-reorder access-method preference order - Add a "When a staff member is created" rule that provisions access for staff to their associated properties Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Linear: DOC-237
Summary
Expands section 3 (Push reservation data) of the Reservation Automations capability guide with practical guidance requested for the
push_dataworkflow:starts_at/ends_at) and changing its assigned space (space_keys), both keyed by the samereservation_key.reservation_keyguidance — explains the key should be your system's own booking ID and must not be derived from underlying resources (space, room, device, guest). Spells out the failure mode (a changed key reads as a new reservation → duplicate credentials on hardware) and documents the safe delete-before-update pattern when the key itself must change.push_datacan translate into a physical hardware operation; speculative pushes multiply commands and avoidable errors.Notes
#3-push-reservation-datasection and follow the section's curl-based example style.🤖 Generated with Claude Code