Meta’s current Muse Connector Platform guidelines ask services to support the full task, including changes, cancellations and refunds where available. For a booking connector, producing a checkout link is insufficient. The documented workflow extends from search and pricing to approval and a confirmed result, with progress preserved when sign-in or verification needs the user.
The guidelines also address ambiguous failures: check an operation’s status before retrying, prevent duplicate transactions and distinguish pending outcomes from confirmed ones. Meta says its review includes end-to-end testing of workflows, permissions and failure handling. These are platform requirements, not evidence that every approved connector performs reliably. The page is undated, and we have not tested these workflows.
Editorial take: The useful connector test comes after the happy path. Can the assistant establish whether an interrupted booking succeeded, show its reference and help change or cancel it? That is a more demanding measure of completion than successfully starting a transaction. For a low-risk evaluation, ask the provider to demonstrate recovery with test data before trusting an integration with a purchase that would be difficult to reverse.