Book a restaurant table through a Resy connector
A PCWorld writer asked Claude to book a table for three in Midtown Manhattan via the Resy connector; it picked a restaurant but the exchange was clunky, with raw JSON and permission prompts. Task: Suggested implementation: A user adds the Resy connector to Claude via Customize > Connectors. The user prompts Claude for dining options near a specific location with party size and time constraints. Claude suggests a restaurant and displays availability, but the user must manually complete the booking on the Resy platform due to connector limitations.; tools: Claude. Human role: The original post does not say how a person stayed involved.; limitations: Prerequisites include a Claude account with connector access and a Resy account. The connector likely only supports read-only operations like availability checks, not write operations like booking. Integration uncertainty exists regarding permission prompts and raw JSON exposure. Human approval is required for the final reservation step..
Tools
Published on Agent Work Atlas:
Overview
A PCWorld writer asked Claude to book a table for three in Midtown Manhattan via the Resy connector; it picked a restaurant but the exchange was clunky, with raw JSON and permission prompts.
Workflow
Suggested implementation: A user adds the Resy connector to Claude via Customize > Connectors. The user prompts Claude for dining options near a specific location with party size and time constraints. Claude suggests a restaurant and displays availability, but the user must manually complete the booking on the Resy platform due to connector limitations.
Reported result
Outcomes are unverified as the source URL returned a 403 error and no direct evidence quotes are available. It is unknown if the recommendation quality or interaction friction met user expectations. Proposed acceptance check: Measure time saved in restaurant discovery versus manual search, and confirm if the connector successfully retrieves real-time availability data.
Human role
The original post does not say how a person stayed involved.
Limitations
Prerequisites include a Claude account with connector access and a Resy account. The connector likely only supports read-only operations like availability checks, not write operations like booking. Integration uncertainty exists regarding permission prompts and raw JSON exposure. Human approval is required for the final reservation step.
Try it
Act as a user testing the Resy connector in Claude. First, navigate to Customize > Connectors and add the Resy connector. Input the following prompt: 'Find a restaurant near [replaceable location] for [replaceable party size] people at [replaceable time]. Please check availability.' Review Claude's response for restaurant suggestions and open slots. If a raw JSON permission prompt appears, note it but do not click 'Always allow' without understanding the scope. Since the connector may not support booking, manually verify the suggested restaurant's availability on the Resy website or app. Measure the time taken to find a suitable option compared to searching Resy directly. If the connector fails to retrieve data or produces errors, document the specific error message. Do not proceed with any actual reservations or payments through the chat interface. Confirm with a human reviewer that the workflow steps are clear before attempting this with real personal data.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.