Old photo restorer with an upload form

Old photo restorer with an upload form

An n8n workflow. Someone sends an old or damaged photo through its form, a RunningHub AI app restores it, and the
workflow downloads the restored picture into the run.

What is inside

• workflow.json: the workflow as n8n exports it, 11 nodes and no sticky notes. It holds no credential. Your RunningHub
  key goes into one node, API Setup.
• README.md: these notes.

What we changed from the original copy

• API Setup held a line of text asking for the key. It is now YOUR_RUNNINGHUB_API_KEY.
• Nothing else. Its one Code node, getBinaryFile, needed no repair.

Before you start

• An n8n instance, on n8n Cloud or your own server.
• A RunningHub account and its API key. Each restoration is a paid task there.
• A scan or a photo of the old picture, in .jpg, .jpeg, .png or .webp.

Set it up

1. In n8n, create a workflow, open its menu and choose Import from File. Pick workflow.json.
2. Open API Setup and replace YOUR_RUNNINGHUB_API_KEY with your RunningHub key. The four RunningHub nodes read it
   from there.
3. Optional: open On form submission to change the form's title, its field label or the file types it takes.
4. Save, open the form's test address and send one photo through it.
5. Press Publish, then share the form's production address.

The form confirms at once, and the run goes on behind it. The restored picture ends up as a file in Download Image, in
the run's execution data, so open the run under Executions to get it. The person who sent the photo sees only the
confirmation. To get the result back to them, add a node after Download Image that emails it or saves it to a shared
folder.

How a run goes

1. On form submission takes the file from its one field, Upload your image.
2. getBinaryFile passes the file on, API Setup holds the key, and Merge joins the two by position into one item.
3. Upload Image sends the photo to RunningHub's /task/openapi/upload and gets back its stored fileName.
4. Image Processing starts the RunningHub AI app 1978607856536719362 at /task/openapi/ai-app/run, with the stored
   file in the app's node 3.
5. Wait pauses 30 seconds, then checkStatus asks for the task's state. If sends SUCCESS on to getOutput, and any
   other state back to Wait for another pause.
6. getOutput reads the restored picture's fileUrl, and Download Image fetches it.

Change the look

• Which app restores the photo: webappId in Image Processing. Node 3 belongs to that app, so check the node number
  if you point it at another one.
• Check timing: amount in Wait, in seconds.
• The form: its title, the field's label and the accepted file types in On form submission. If you rename the field,
  change Upload Image too: it reads the file as Upload_your_image, a name n8n makes from the label.

Good to know

• RunningHub bills each restoration task to your account.
• A task that fails never ends the run. If looks for SUCCESS only, so a failed task is checked again and again until
  you stop the run under Executions.
• Once the workflow is published, anyone with the form's address can start a run on your RunningHub account.
• The key sits as plain text in API Setup, so anyone who can open the workflow can read it. Take it out before you share
  the workflow.
• The photo goes to RunningHub. Send only photos you have the right to use, and ask the people in them, or their
  family, when you can.
• An AI restorer fills in detail that was lost: faces, text and fabric can come back looking sharper than they were.
  Keep the original scan.