This article explains how Zoho CRM’s Kiosk feature handles file uploads, what the recent kiosk updates enable, and how attachments relate to CRM storage and WorkDrive integration so you can plan forms and scripts accordingly. [8][5]
Why this matters
Use kiosk screens when you need public-facing or in-person data capture that creates CRM records in real time, and decide how files should be stored or referenced because CRM’s file handling and the WorkDrive integration affect where attachments live and what fields are available. [8][5][3]
Beam Help — independent expert support for Zoho; not official Zoho support. [8]
Step-by-step
Step 1. Confirm the kiosk is created and has an integration API name set so you can launch it from client scripts anywhere inside Zoho CRM; kiosks now support a unique integration API name at creation for easier management and for calling from client-side commands. [8]
Step 2. If you want to open the kiosk from other CRM pages, configure a client script command under Settings > Developer Space > Client Scripts > Commands and use the kiosk’s integration API name when creating the command so users can launch the kiosk via command palette or shortcuts. [8]
Step 3. Decide how the kiosk should create records during execution: use the preserved “standard” data-creation setup for automatic creation with fixed or prior-screen values, or enable the new “use user input” option so administrators can present a lightweight popup that creates records from values entered while the kiosk runs. [8]
Step 4. Plan file capture fields in your kiosk flow with the platform limits and field types in mind: Zoho CRM Quote/subform limitations mean some record-level controls around image uploads and file placeholders in Writer templates are restricted, so test whether you need a file upload field or a link to WorkDrive instead. [3][5]
Step 5. If you expect many or large uploads, consider the CRM–WorkDrive integration so files can be stored in structured Team Folders with two-way sync and granular permissions rather than relying solely on CRM storage; the integration lets CRM records link to WorkDrive folders and is being rolled out across accounts. [5]
Step 6. For integrations that submit files to Zoho CRM (for example, from external forms or middleware), convert file data into the multipart format the attachment APIs expect or send an attachment link where supported; troubleshooting becomes easier once the payload format and record ID are verified. [2]
Step 7. Be aware of operational incidents and recovery steps: if you encounter failed uploads that appear system-wide, check Zoho status and follow guidance such as performing a hard browser refresh after the issue is resolved, then open a ticket via your Enterprise Support contact if problems persist. [1]
Step 8. When you require multiple files per field in related products (for example in Zoho Creator or custom forms), set multimode upload and configure the Upload Limit in the field properties so users can add the allowed count of files; consult the form field documentation for image and file upload behaviour. [6][7]
Common pitfalls
- Kiosk launch mismatch: client script commands must reference the kiosk’s integration API name exactly; using a different name prevents the kiosk from opening via the command palette. [8]
- Assuming image placeholders work in Writer merges: file upload fields and links do not always translate into Writer template placeholders, so expected images may not appear in merged PDFs. [3]
- Upload format errors from external forms: sending only a URL or non-multipart payload can cause attachments not to attach unless the receiving workflow converts the file into the multipart format the CRM attachment endpoints expect. [2]
What to check
- The kiosk has an integration API name set and your client script command uses that exact API name before testing kiosk launch. [8]
- File capture fields in the kiosk map to the storage method you want (CRM attachment vs WorkDrive folder/link) and you have tested a full upload flow. [3][5]
- If uploads fail unexpectedly, verify platform status and perform a hard browser refresh; if the issue persists open a ticket with your Enterprise Support contact. [1]