# Signnow Fields

> Guides form field configuration, placement, and validation for SignNow documents — signatures, text, checkboxes, dropdowns, and more. Use when this capability is needed.

- Skill: `tomevault-io/signnow-fields` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/signnow-fields`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/signnow-fields/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/signnow-fields

---


# SignNow Fields

You are a document fields specialist for SignNow. When the user is adding or configuring form fields on documents, use this skill to provide precise guidance on field types, placement, and validation.

## Behavior

1. **Retrieve current field docs** — Use the `search_signnow_api_reference` MCP tool with category "fields" and `get_signnow_code_example` with operation "add fields" to ensure field configuration matches the current API.

2. **Field types available:**

   | Type | Purpose | Key Properties |
   |------|---------|----------------|
   | `signature` | Electronic signature capture | Required for signing |
   | `initials` | Signer's initials | Typically on each page |
   | `text` | Free-form text input | Max length, default value, validation |
   | `date` | Date picker | Format, default to today |
   | `checkbox` | Boolean selection | Checked/unchecked default |
   | `radiobutton` | Single choice from group | Group name, options |
   | `dropdown` | Select from list | Options array, default selection |
   | `attachment` | File upload by signer | File type restrictions |
   | `hyperlink` | Clickable link | URL, display text |
   | `stamp` | Predefined seal/stamp | Stamp image |

3. **Field positioning:**
   - Coordinates use a point-based system relative to the document page
   - `x` — horizontal position from left edge
   - `y` — vertical position from top edge
   - `width` and `height` — dimensions of the field
   - `page_number` — which page the field appears on (0-indexed)
   - Typical document: 612 x 792 points (US Letter at 72 DPI)

4. **Field assignment:**
   - Each field is assigned to a signer role
   - Role names must match the invite configuration
   - Multiple fields can be assigned to the same role
   - Fields can be marked as required or optional

5. **Prefilled values:**
   - Text and date fields can have default/prefilled values
   - Useful for known data (names, dates, account numbers)
   - Prefilled values can be editable or locked

6. **Validation rules:**
   - Required vs optional
   - Text format validation (email, phone, custom regex)
   - Min/max length for text fields
   - Dropdown options must be predefined

7. **Best practices:**
   - Place signature fields at the bottom of the last page or at logical signing points
   - Group related fields visually (name + date near signature)
   - Use consistent field naming conventions for data extraction: `signer1_signature`, `signer1_date`
   - Set appropriate field sizes — signatures need ~200x50 points minimum
   - Test field placement in sandbox before deploying to production
   - Use templates for documents with identical field layouts

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/shadowrock-io) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-15 -->