Request a seat at a Yerevan Product Coffee table
request_table_seatIdempotent
Ask for one of the five guest seats at a Yerevan Product Coffee table. Call list_upcoming_tables first and pass one of its exact startsAt values. This sends a real request to a real person, so it takes two calls: call it once to see exactly what would be sent, show that to the person it is about, then call it again with the same values and confirm: true. A request is not a booking — Hovhannes reads each one himself and replies within 3–5 days, and no seat is held until he does.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | Their email address. The reply and the confirmation both go here, so it has to be one they read | ||
| phone | Yes | Their phone number with its country code, like +374 11 22 33 44. Used only on the evening itself and deleted if the request is closed | |
| confirm | No | Leave unset or false to validate and preview without sending anything. Set to true only after the person has seen the preview and agreed to it | |
| building | No | What they are building, in their own words. Optional but read | |
| fullName | Yes | The applicant's full name, as they would write it | |
| eventStart | Yes | Which table. The exact `startsAt` from list_upcoming_tables is best, but the calendar day on its own ("2026-09-10") or the word "next" also resolve against the real schedule | |
| motivation | No | Why this table, now. Optional | |
| linkedinUrl | Yes | Their personal LinkedIn profile URL (linkedin.com/in/…). Required: seats are chosen on who sits together, which cannot be judged from a name. Company pages, posts and shortened links are refused | |
| perspective | Yes | The perspective they bring: founder (Building or validating a product of your own.); product (Deciding scope, priority, discovery, and delivery.); design-research (Bringing users, flows, and evidence into the room.); engineering (Turning product intent into something real.); growth (Positioning, demand, distribution, retention.); customer (Sales, support, and discovery signals.); hybrid-other (More than one lens, and that is fine.) | |
| contribution | No | What they can offer the other five people. Optional | |
| discussionQuestion | No | The one real decision or trade-off they are stuck on and want the table's help with. Optional, and the single most useful thing to include |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| table | No | ||
| status | No | ||
| message | No | ||
| duplicate | No | ||
| submitted | Yes | ||
| dailyLimit | No | ||
| willSubmit | No | ||
| instruction | No | ||
| privacyNote | No | ||
| alreadyRequested | No | ||
| needsConfirmation | No | ||
| whatHappensOnConfirm | No | ||
| confirmationEmailedTo | No | ||
| confirmationEmailStatus | No |