How to use a Righthand with Jotform

Quick answer

Use approved Jotform submission records to prepare an attachment readiness register for administrative intake. Separate an answer, an uploaded-file reference, and a file that the authorized reviewer can actually inspect.

Start with a submission-and-attachment readiness register that the intake administrator can check against the original records. Righthand prepares the review artifact; the source application remains the operational record.

Establish the input route

Jotform’s API documentation describes access to forms and submissions and documents different API base URLs for account environments. Official Jotform reference, checked October 6, 2026.

The form administrator should identify the correct account environment and approve the minimal submission fields. Verify the available read operation before using a connected route. An explicit permitted extract can pair submission references with approved attachment-access notes without sharing credentials.

Check the current integration directory and Righthand setup documentation. A listed app does not establish every read or write action. For a connected route, verify the assigned account, available operation, object scope, and one permitted sample read. This guide also works from an explicitly supplied, approved extract; it does not require an unverified native operation. Keep credentials out of the article brief.

Worked input and output

These three records are synthetic illustrations, not customer results or a hands-on integration test.

The register should state whether a file is referenced, accessible, and relevant to the accepted checklist. JF32 shows why those categories matter: asking the respondent to upload again may be unnecessary when the problem is reviewer access. JF33 requires the correct form revision before completeness can be assessed.

A complete first-run brief

Use an approved Jotform submission extract and attachment index for October 12–16, 2026. Fields: environment reference, form ID, submission ID, question ID, answer, attachment reference, received time, access check. At Monday 9 AM America/Los_Angeles, prepare a submission-and-attachment readiness register as source-linked Markdown in my private review thread. Preserve record identities and the extract timestamp. Group unresolved items by next action and responsible owner. Reviewer: intake administrator. Do not change submissions, distribute attachments, make eligibility decisions, send requests, or expand access. Result check: Compare submission/question identities, approved document requirements, and the reviewer’s attachment access observations.

A permitted preparation step does not authorize a consequential write or an external send. Resolve proposed changes through the app's supported process after the responsible owner approves their exact scope.

Reconcile before widening the task

A URL copied into a report can expose a file more widely than intended. Keep the review destination restricted and include only permitted references. Do not use one account environment’s base URL or permissions as evidence that another environment’s submissions are available.

Use a small approved intake batch for the first review. Ask the administrator to resolve JF32’s access route and verify JF33’s revision. Keep any request for further documents as a separate draft for the intake owner rather than sending it automatically.

For the first acceptance review, keep the original input slice beside the result and mark which items were checked. If access or evidence is incomplete, return that gap with its record identity rather than a confident completion statement. Review Pricing using the actual preparation workload and correction effort.