Lupdo guides

Turn a client request into a saved form entry

Updated 27 October 2026

A request arrives with a name, email and company, and someone has to transfer each value into a web form. Lupdo can reuse the form-entry routine you demonstrate, with the next client's data.

Record the route

Open the client list or entry page in your web application. Start Record a task, create one fictitious record and finish recording. Include the field choices and save action actually needed. Do not add unrelated browsing to an older client's record afterwards.

Paste the next request

Choose With changes in the saved task. With an AI plan, paste the request and ask Lupdo to prepare the form fields. Review the proposed name, email, company and any other data before approving.

Handle missing values deliberately

A source message may omit a phone number or leave the contact status unclear. Do not assume that an old recorded value belongs to the new client. State whether an absent field should be left blank, kept or supplied by you, and check the review. Dropdowns and legal-basis choices also need the correct intended values.

For several clients

Supply a clearly headed table and request one complete entry per client. Check the proposed batch size and destination. Each record needs its own run of the saved process; this is different from pasting a whole table into one document.

Verify in your application

Look at the actual saved record, then the final list for a batch. This example describes the workflow, not guaranteed compatibility with every CRM. A different form, ambiguous control or uncertain save result may require intervention. Use fictitious data for your first check.