plugin-tables
Beta@fayz-ai/plugin-tables
Restaurants don't run on records — they run on the room. plugin-tables gives the food vertical a real floor plan: zones, tables, and live status (available, occupied, reserved, cleaning), with seat and close flows wired to your own backend. It's the difference between a generic CRM and software a host can actually work a Friday night on.
Full documentation is coming. For now, this page summarizes what the SDK catalog knows about the plugin.
Specs
| Package | @fayz-ai/plugin-tables |
|---|---|
| Version | 0.3.0 |
| Status | beta |
| Capability | Partial capability |
| Stable channel | ^0.3.0 |
| Migrations | none |
| Factory | createTablesPlugin() |
Data model
No tables of its own — this plugin uses the core / archetype library (same rule: tenant_id + RLS). See Data model.
AI tools
| id | mode | description |
|---|---|---|
tables.availability | read | Returns which tables are available, occupied, reserved, or being cleaned. |
tables.seat-guests | persist | Seats guests at a specific table. |
Tools an agent can call against your app. Your app as a data layer.
Integrations
No hosted connector — external providers come in via the connector spine. integrations catalog.
Use this page as a skill.
.md of this page is the agent-consumable contract — data model, tools and integrations in a single file an AI reads directly. Preview fayz skill add plugin-tables is coming soon to install this as a skill. See Skills.Integrate
Add the plugin to surfaces.admin.plugins in your app's app.manifest.json and run the doctor to validate:
{
"surfaces": {
"admin": {
"plugins": [
{ "id": "tables", "enabled": true }
]
}
}
}npx fayz doctorfayz doctor checks the manifest against the SDK catalog. See Configuration.
