plugin-forms

Beta

@fayz-ai/plugin-forms

Every real business runs on forms it never wanted to build: anamnesis sheets, evolution notes, consent contracts, intake docs. plugin-forms kills that busywork. Define a template once, attach a filled document to a person, and the data lives in your tenant — not in a PDF nobody can query.

Preview of plugin-forms as the customer sees it

Full documentation is coming. For now, this page summarizes what the SDK catalog knows about the plugin.

Specs

Package	`@fayz-ai/plugin-forms`
Version	0.2.0
Status	beta
Capability	Partial capability
Stable channel	`^0.2.0`
Migrations	3 migration(s)
Factory	`createCustomFormsPlugin()`

Data model

Table	Key columns
`plg_forms_templates`	name, description, category, version, is_current, parent_id
`plg_forms_documents`	template_id, person_id, title, data, status, signed_at
`plg_forms_document_files`	document_id, field_key, file_url, file_name, file_size, mime_type
`documents`	kind, person_id, title, description, status, file_url

Convention: plg_ + tenant_id + RLS. Data model.

AI tools

id	mode	description
`custom_forms.list-templates`	read	Lists available form templates for the current tenant.
`custom_forms.list-documents`	read	Lists filled documents, optionally filtered by person or status.

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-forms 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": "forms", "enabled": true }
      ]
    }
  }
}

npx fayz doctor

fayz doctor checks the manifest against the SDK catalog. See Configuration.