Skip to content

Commit e4d97ef

Browse files
committed
docs: update AGENTS.md to clarify schema.type requirements
- Added a note specifying that `schema.type` must be a simple string and should not use a YAML array format. - Explained the potential TypeError that may occur if an array is used, guiding users to express nullability in the `description` instead.
1 parent 5b69171 commit e4d97ef

1 file changed

Lines changed: 1 addition & 0 deletions

File tree

AGENTS.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -427,6 +427,7 @@ schema:
427427
- `assistant_ids` uses **Vapi UUIDs** (not local filenames) — these are the IDs of assistants this output applies to
428428
- `target: messages` means the LLM analyzes the full message history
429429
- `type: ai` means an LLM generates the output (vs. `type: code` for programmatic)
430+
- **`schema.type` must be a simple string** (e.g. `type: string`, `type: boolean`, `type: object`). Do NOT use a YAML array like `type: [string, "null"]` — the Vapi dashboard calls `.toLowerCase()` on this field and will crash with `TypeError: .toLowerCase is not a function` if it receives an array. For nullable values, express nullability in the `description` instead (e.g. "Return null if no follow-up is needed")
430431

431432
---
432433

0 commit comments

Comments
 (0)