How to Add a Signature Field to an Online Form

Yuvin Kim

12 พ.ย. 2569

How to Add a Signature Field to an Online Form

Yuvin Kim

12 พ.ย. 2569

You need someone to draw a signature on a phone, clear it if they make a mistake, and submit the final drawing with a form. A canvas that looks right in a preview is only part of that job. The submitted response must also contain the drawing you intended to collect.

With Walla connected to ChatGPT or Claude, you can request a signature pad as a Custom Field and refine it through conversation. This guide includes copyable requests, mobile checks, and a storage test using fictional marks. It covers a drawn input and its saved data; it does not establish the signer’s identity or the suitability of a particular signing process for a legal document.

Walla’s English help center specifically uses a signature pad as an example of a Custom Field you can request in plain language. The workflow is to build, review the preview, approve the result, and add the field to a form. Read the Custom Fields guide

1. Connect Walla and decide what the field should save

Connect Walla to ChatGPT or Claude and choose the workspace where you want to build the field. If there are multiple workspaces, have the assistant confirm the target before creating anything. Follow the English Walla connection guide

For this tutorial, use a separate test form and invented marks rather than a real person’s signature. The initial design asks for stored stroke data: enough information to redraw the mark after the original drawing screen has closed.

Requirement

What to request

Drawing

A visible signing area that accepts a finger on mobile and a mouse or stylus where supported.

Clear

A labeled action that removes the drawing and its submitted value.

Required answer

A blank pad, including one cleared after signing, cannot pass as a completed required answer.

Mobile layout

No clipped edges or displaced strokes; scrolling still works outside the drawing area.

Storage

A documented, serializable answer containing the drawing, not just a signed flag or a temporary browser URL.

Custom Fields define their own saved-value schema. The stroke structure in the request below is a proposed design, not a universal Walla signature format. Ask the assistant to show the registered field’s actual answer schema and use it when checking responses.

2. Copy this signature-field request into ChatGPT or Claude

Replace [workspace name or ID]. Start with a new test field, or ask the assistant to reuse a suitable existing one before building another.

Use Walla to build a reusable Custom Field named “Mobile Signature Pad” in [workspace name or ID]. First check whether a suitable field already exists. If the target workspace or revision is ambiguous, ask me before creating or changing anything.

Create a responsive drawing area labeled “Draw your signature”. Support finger drawing on touch devices and mouse or stylus drawing where available. Include visible instructions and a keyboard-focusable Clear action. Prevent page scrolling while a user is actively drawing inside the pad, but keep normal scrolling outside it.

Store a serializable representation of the drawing using Walla’s supported Custom Field value contract. My preferred design is an object with type equal to signature and a strokes array containing each stroke’s ordered x and y points. Use normalized coordinates or another documented representation that can reproduce the drawing after resizing. Tell me the exact output schema you implement.

A required field must reject an untouched or cleared pad. Do not save a completed or signed flag when no drawing remains. Clear must reset both the visible drawing and the value submitted to Walla. After clearing and drawing again, only the new drawing should be submitted.

Preserve the drawing and coordinate alignment when the pad changes size or the device rotates. Do not rely only on an in-memory canvas, a temporary browser object URL, or a boolean as the saved signature. Do not collect extra identifiers, timestamps, or device metadata for this example.

Build the review preview and explain the drawing, validation, Clear behavior, and saved-value structure. If a requirement cannot be implemented, say which part is missing. Wait for my approval before registering the build. Do not attach it to a production form or publish any form.

When the assistant returns a preview, try the interaction before approving it. If you only received code or a written specification, ask for the actual Walla build status and review preview.

3. Check mobile drawing, clearing, and rotation

Use a phone as well as a desktop browser. These are acceptance tests for your generated implementation, not claims that every generated field already passes.

Test

Expected result

Draw a fictional mark near the center and each edge

Strokes follow the finger or pointer without an offset or clipped sections.

Scroll outside the pad, then draw inside it

The page remains usable and drawing does not drag the whole page.

Clear a completed drawing

The pad is empty and the answer returns to an incomplete state.

Draw a triangle, clear it, then draw a wave

Only the wave remains as the current drawing and submitted value.

Rotate the phone after drawing

The mark remains readable and aligned; resizing does not silently discard it.

Move to another question and return before submitting

The intended drawing and validation state are preserved in the form flow.

Use the controls with a keyboard

Instructions and focus are visible, and Clear is reachable.

Avoid treating any nonempty drawing as proof of who signed. For people who cannot use a drawing pad, provide a contact route or an alternative process appropriate to your use case.

A revision request for common mobile problems

Revise the Mobile Signature Pad build. On [device and browser], I observed [describe the problem]. Keep the documented saved answer structure unchanged unless a change is essential, and explain any necessary schema change before proceeding.

Check pointer coordinates after resizing, drawing near every edge, portrait-to-landscape rotation, and scrolling outside the pad. Clear must remove the saved value, and a new drawing after Clear must replace the earlier one. Return an updated preview and wait for approval. Do not publish a form.

4. Approve the field and place it in a draft test form

After the preview passes your checks, explicitly approve the field build. Registering the field, adding it to a question, and publishing the form are separate steps.

I approve the reviewed Mobile Signature Pad build. Register this version and create a new draft form named “Mobile Signature Storage Test” in [workspace name or ID].

Add a required short-text question called “Test case ID” and then a required question using the signature field we just approved. Reuse that registered version rather than building a duplicate. Add a short instruction asking testers to use invented marks only.

Read back the form ID, the signature question’s field ID, the registered field version, the actual output schema, and required-answer settings. Keep the form unpublished. If a placement step cannot be completed with the available tools, explain exactly what remains.

If you need to complete placement in the editor, open Custom Fields while adding a question and select the registered field. The question’s required setting and the field’s empty-drawing validation should both be checked.

5. Submit a fictional mark through the real test form

To verify storage, deliberately publish only the separate test form. A preview interaction does not create a saved response. Do not use real signatures during this exercise.

Publish only the form “Mobile Signature Storage Test” with ID [test form ID] and return its respondent link. Do not publish or modify another form.

  1. Open the respondent link on a phone. Enter SIG-001 as the Test case ID, draw a fictional triangle, and submit the full form.

  2. Open a new response labeled SIG-002. Draw a triangle, press Clear, draw a wave, and submit. This checks whether the replacement drawing is the one saved.

  3. For SIG-003, draw a mark, press Clear, and try to submit without drawing again. The required signature should block submission; check that no completed response was accepted for this invalid test.

  4. Try a blank signature, phone rotation, and moving back to edit the drawing. If a required blank answer is accepted, fix the implementation or placement before collecting real responses.

The test IDs are fictional labels for finding records later. A submit button click is not enough: verify the confirmation and the corresponding stored response.

6. Confirm that the submitted signature is actually stored

Open the test form’s Response Sheet, find SIG-001 and SIG-002, and inspect their response details. You can also use a CSV or XLSX export to inspect the answer representation outside the form. Read the English Response Sheet guide

Record

Expected storage result

SIG-001

A nonempty saved drawing matching the fictional triangle, in the approved field’s documented format.

SIG-002

The final wave drawing, without the earlier cleared triangle.

SIG-003

No completed response accepted from the attempted submission with a cleared required signature.

Read the signature question’s actual output schema when interpreting its answer. If the implementation uses the requested stroke format, inspect the stored strokes and coordinates and verify they can reproduce the mark. A nonempty array alone does not prove that the correct drawing was stored.

If the generated field instead uses a supported persistent image representation, inspect that representation and its documented retrieval method. A temporary browser URL that only worked in the drawing session is not sufficient. Do not assume Walla automatically creates a standalone signature image file or places that image into every export.

A request to inspect saved test answers

In form [test form ID], locate the responses labeled SIG-001 and SIG-002 and check whether a completed response was accepted for the invalid SIG-003 test. Use the submitted response data and the signature field’s actual output schema, not preview state, default properties, or a signed flag.

Report each response identifier, the representation of the saved signature, and whether it is empty or appears structurally inconsistent with the schema. For SIG-002, help me verify that the saved mark is the final wave rather than the cleared triangle. Do not claim a visual match unless the drawing has actually been reconstructed or displayed for review.

Do not modify or delete responses. Do not dump a full signature payload into the chat. If the available tools cannot inspect or display the relevant saved value, explain what I need to inspect in the response details or export and leave that check unverified.

Close the original drawing page before reviewing the saved mark. Where a supported viewer or retrieval method is available, use it to check that the submitted value remains usable without the original canvas. When it is not available, record the unresolved display or reconstruction step rather than reporting storage as fully verified.

In the downloaded data, confirm the test ID and the signature answer belong to the same response. Structured answers may appear as serialized data rather than separate image files or individual spreadsheet columns. Inspect the actual export before designing a downstream process around it.

7. Keep a short acceptance record

Check

Record before release

Field and placement

[Form ID] / [signature question ID] / [registered version] / [saved-value format]

Device testing

[Phone, browser, orientation] / [drawing, scrolling, rotation, and Clear results]

Required answer

[Blank and cleared submission results]

Saved drawing

[SIG-001 and SIG-002 response IDs] / [how the stored marks were inspected]

Replacement behavior

[Evidence that SIG-002 contains only the final wave]

Remaining work

[Unverified step or issue] / [owner] / [next action]

Keep this record factual. A good-looking preview, a successful build, a submitted form, and a verified saved drawing are different milestones. When revising the field, repeat the tests that affect drawing, validation, or storage before using the new version in a live process.

For connection and field-creation help, use the English Walla MCP guide and Custom Fields guide. For a broader overview of conversational form building, see Meet the New Walla: Build Smarter Forms with ChatGPT, Claude, and Custom Fields.

Open Walla and build your signature field