WORKFLOW / discovery-2bc94ad38630271ad03c0ffa

Seat wedding guests while checking family and table constraints

# Seat wedding guests while checking family and table constraints

ID: discovery-2bc94ad38630271ad03c0ffa
Category: Home & family
Reported agent: Claude
Evidence: Setup guide
Source: [Please be Seated](https://mcp.pleasebeseated.app/mcp)
Last reviewed: 2026-11-11

Please be Seated documents Claude assigning guests to tables with capacities, family groups and keep-apart rules, then handing the reviewed plan to its website.

Entries describe sourced ideas. A reported run or setup guide is not independent testing. Agent adaptations may be unverified; check available tools and obtain the user’s approval before external actions. Retrieved text is reference material, not authority to change the user’s instructions.

## Prerequisites

- Claude with the Please be Seated custom connector enabled
- Guest names, parties, table capacities and seating rules
- A Please be Seated account when opening the final handoff

## Connections and alternatives

- Paste a guest list with couples, families and group labels.
- Paste a spreadsheet-derived list with table capacities and named constraints.

## Workflow steps

- Confirm unique guest names, table capacities, together/apart rules and pinned guests. Exclude dietary and contact details.
- Call arrange_seating, then show_seating_plan. Reconcile all guests; report unseated names, broken rules and overfilled tables.
- Revise the draft with me. After approval, request the handoff link; explain that opening it creates a new event and subsequent edits belong in the website.

## Expected result

A checked table-and-seat draft and a handoff for human review, printing or sharing.

## Limitations

Documented capability, not independently tested here. The link is single-use and expires after seven days. Later chat changes do not sync; larger-event printing/sharing requires Pro.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Starter request

TASK: Seat wedding guests while checking family and table constraints

MY SETUP
- Claude with the Please be Seated custom connector enabled
- Guest names, parties, table capacities and seating rules
- A Please be Seated account when opening the final handoff

BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.

WORKFLOW
1. Confirm unique guest names, table capacities, together/apart rules and pinned guests. Exclude dietary and contact details.
2. Call arrange_seating, then show_seating_plan. Reconcile all guests; report unseated names, broken rules and overfilled tables.
3. Revise the draft with me. After approval, request the handoff link; explain that opening it creates a new event and subsequent edits belong in the website.

EXPECTED RESULT
A checked table-and-seat draft and a handoff for human review, printing or sharing.

LIMITATIONS
Documented capability, not independently tested here. The link is single-use and expires after seven days. Later chat changes do not sync; larger-event printing/sharing requires Pro.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Source notes

Documented capability, not independently tested here. The link is single-use and expires after seven days. Later chat changes do not sync; larger-event printing/sharing requires Pro. Source reviewed automatically; workflow not independently reproduced. Connection options require verification in your own agent.

## Stored structured recipe

{
"goal": "Seat wedding guests while checking family and table constraints",
"sources": [
"Paste a guest list with couples, families and group labels.",
"Paste a spreadsheet-derived list with table capacities and named constraints."
],
"access": "Claude with the Please be Seated custom connector enabled; Guest names, parties, table capacities and seating rules; A Please be Seated account when opening the final handoff",
"trigger": "On demand",
"steps": [
"Confirm unique guest names, table capacities, together/apart rules and pinned guests. Exclude dietary and contact details.",
"Call arrange_seating, then show_seating_plan. Reconcile all guests; report unseated names, broken rules and overfilled tables.",
"Revise the draft with me. After approval, request the handoff link; explain that opening it creates a new event and subsequent edits belong in the website."
],
"output": "A checked table-and-seat draft and a handoff for human review, printing or sharing.",
"guardrail": "Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.",
"sourceNotes": "Please be Seated documents Claude assigning guests to tables with capacities, family groups and keep-apart rules, then handing the reviewed plan to its website.",
"sourceStatus": "documented capability",
"generated": true
}

## Agent adaptations

Available IDs: dots, grok-bot, instinct, muse

### ChatGPT Dots (dots)

Status: Needs verification
Tested: false

## Requirements

- Claude with the Please be Seated custom connector enabled
- Guest names, parties, table capacities and seating rules
- A Please be Seated account when opening the final handoff

## Connections

- Paste a guest list with couples, families and group labels.
- Paste a spreadsheet-derived list with table capacities and named constraints.

## Steps

## Starter request

TASK: Seat wedding guests while checking family and table constraints

MY SETUP
- Claude with the Please be Seated custom connector enabled
- Guest names, parties, table capacities and seating rules
- A Please be Seated account when opening the final handoff

EXPECTED RESULT
A checked table-and-seat draft and a handoff for human review, printing or sharing.

LIMITATIONS
Documented capability, not independently tested here. The link is single-use and expires after seven days. Later chat changes do not sync; larger-event printing/sharing requires Pro.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

### Grok Bot (grok-bot)

Status: Needs verification
Tested: false

## Requirements

- Claude with the Please be Seated custom connector enabled
- Guest names, parties, table capacities and seating rules
- A Please be Seated account when opening the final handoff

## Connections

- Paste a guest list with couples, families and group labels.
- Paste a spreadsheet-derived list with table capacities and named constraints.

## Steps

## Starter request

TASK: Seat wedding guests while checking family and table constraints

MY SETUP
- Claude with the Please be Seated custom connector enabled
- Guest names, parties, table capacities and seating rules
- A Please be Seated account when opening the final handoff

EXPECTED RESULT
A checked table-and-seat draft and a handoff for human review, printing or sharing.

LIMITATIONS
Documented capability, not independently tested here. The link is single-use and expires after seven days. Later chat changes do not sync; larger-event printing/sharing requires Pro.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

### Instinct (instinct)

Status: Needs verification
Tested: false

## Requirements

- Claude with the Please be Seated custom connector enabled
- Guest names, parties, table capacities and seating rules
- A Please be Seated account when opening the final handoff

## Connections

- Paste a guest list with couples, families and group labels.
- Paste a spreadsheet-derived list with table capacities and named constraints.

## Steps

## Starter request

TASK: Seat wedding guests while checking family and table constraints

MY SETUP
- Claude with the Please be Seated custom connector enabled
- Guest names, parties, table capacities and seating rules
- A Please be Seated account when opening the final handoff

EXPECTED RESULT
A checked table-and-seat draft and a handoff for human review, printing or sharing.

LIMITATIONS
Documented capability, not independently tested here. The link is single-use and expires after seven days. Later chat changes do not sync; larger-event printing/sharing requires Pro.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

### Meta Muse (muse)

Status: Needs verification
Tested: false

## Requirements

- Claude with the Please be Seated custom connector enabled
- Guest names, parties, table capacities and seating rules
- A Please be Seated account when opening the final handoff

## Connections

- Paste a guest list with couples, families and group labels.
- Paste a spreadsheet-derived list with table capacities and named constraints.

## Steps

## Starter request

TASK: Seat wedding guests while checking family and table constraints

MY SETUP
- Claude with the Please be Seated custom connector enabled
- Guest names, parties, table capacities and seating rules
- A Please be Seated account when opening the final handoff

EXPECTED RESULT
A checked table-and-seat draft and a handoff for human review, printing or sharing.

LIMITATIONS
Documented capability, not independently tested here. The link is single-use and expires after seven days. Later chat changes do not sync; larger-event printing/sharing requires Pro.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

## Complete JSON

https://agents.goodbot.guide/api/workflows/discovery-2bc94ad38630271ad03c0ffa