Opentable Booking

OpenTable Booking (Browser Tool)

Use the OpenClaw browser tool to book restaurants via OpenTable.

> Why this skill exists: OpenTable's widget hides critical UI elements > (time-slot links, terms checkboxes) from the accessibility/aria tree. > This skill encodes the JS evaluation patterns that reliably find them. > See browser-snippets.md for the full snippet reference.

When to Use

Do not use for SevenRooms, Resy, Tock, TheFork, or other booking platforms.

Prerequisites

1. OpenClaw browser is running with profile="openclaw" (headed, not headless — Cloudflare blocks headless on OpenTable). 2. User is already logged into OpenTable (session cookie present). 3. A payment card is on file in the OpenTable account (auto-loaded at checkout).

First-time setup: If not yet logged in, navigate to the OpenTable sign-in page manually, authenticate via email + verification code, and ensure a card is saved. This only needs to be done once — the session persists.

Core Loop (MANDATORY)

1. browser.navigate to target URL. 2. browser.snapshot (interactive). 3. Decide action using refs from snapshot. 4. browser.act (click/fill). 5. Re-snapshot after every significant action.

Never guess selectors. Never reuse old refs after navigation.

Booking Flow

1) Parse request

Extract from the user's message:

2) Navigate to restaurant page

Use slug URL:

https://www.{domain}/r/{restaurant-slug}-{location}?covers={partySize}&dateTime={YYYY-MM-DD}T{HH:MM}

If you don't know the slug, use search:

https://www.{domain}/s?covers={party_size}&dateTime={date}T{time}&term={restaurant}+{location}

Where {domain} is the appropriate OpenTable domain (e.g. opentable.co.uk, opentable.com).

3) Dismiss cookie banner

If a cookie banner appears, click the Accept/Close button by ref. Re-snapshot.

browser.act(click ref for "Accept" / "Accept All" / close button)
browser.snapshot(interactive=true)

4) Confirm/Set date, time, party size

Check the widget bar at the top of the restaurant page. If the pre-filled values don't match the request, click the relevant widget and update:

Re-snapshot after each change. Then click "Find a Table" / "Search" if needed.

5) Select time slot (⚠️ JS required)

The time-slot buttons are NOT reliably in the aria tree. Run this JS evaluation to find them:

(() => {
  const links = [...document.querySelectorAll('a')];
  const timeSlots = links.filter(a => {
    const text = a.textContent.trim();
    return /^\d{1,2}:\d{2}$/.test(text) && a.offsetParent !== null;
  });
  return timeSlots.map(a => ({
    time: a.textContent.trim(),
    id: a.id || '',
    href: a.href || '',
    rect: a.getBoundingClientRect().toJSON()
  }));
})()

This returns visible elements whose text matches HH:MM.

To click the desired slot:

(() => {
  const links = [...document.querySelectorAll('a')];
  const target = links.find(a =>
    a.textContent.trim() === '{TARGET_TIME}' && a.offsetParent !== null
  );
  if (target) { target.click(); return 'clicked ' + target.textContent.trim(); }
  return 'not found';
})()

Replace {TARGET_TIME} with the exact HH:MM string (e.g. "20:30").

If the exact time isn't available, pick the nearest available slot. Re-snapshot after clicking.

6) Choose booking type

If options like Standard reservation vs tasting menus appear, select Standard unless user specified otherwise. Click its Select button by ref. Re-snapshot.

7) Verify pre-filled details

Because we're logged in, OpenTable should pre-fill:

(() => {
  const checkboxes = [...document.querySelectorAll('input[type="checkbox"]')];
  const terms = checkboxes.find(cb => {
    const label = cb.closest('label') || document.querySelector('label[for="' + cb.id + '"]');
    return label && /terms|conditions|policy|agree/i.test(label.textContent);
  });
  if (terms && !terms.checked) {
    terms.click();
    return 'checked terms';
  }
  if (terms && terms.checked) return 'already checked';
  return 'not found';
})()

browser.act(click ref={confirm_button_ref})

1. OpenClaw browser is running with profile="openclaw" (headed, not headless — Cloudflare blocks headless on OpenTable). 2. User is already logged into OpenTable (session cookie present). 3. A payment card is on file in the OpenTable account (auto-loaded at checkout).

First-time setup: If not yet logged in, navigate to the OpenTable sign-in page manually, authenticate via email + verification code, and ensure a card is saved. This only needs to be done once — the session persists.