Working with files

In Keragon, you have the ability to handle files directly within your automations. Whether you’re working with documents, images, or other file types, understanding how to properly access, download, and upload files is crucial for successful workflow execution.

Downloading files

Handling files often starts with retrieving them from a source. The process differs depending on whether the file URL is public or gated.

Case 1: Public URLs

• If the file URL is public, you can directly map the URL to any action that accepts a file input—there’s no need to download the file first.

• How to Check if a URL is Public:

  • Open the URL in an incognito/private browser window.

  • If it loads without requiring authentication, the URL is public.

• Example:

  • https://www.wikipedia.org/portal/wikipedia.org/assets/img/Wikipedia-logo-v2@2x.png is a public URL.

Case 2: Gated URLs

• If the file URL is gated, you must download it before uploading or processing it.

• How to Check if a URL is Gated:

  • Open the URL in an incognito/private browser window.

  • If it prompts for authentication or fails to load, it’s gated.

• Common Example:

  • Jotform file URLs are gated and require authentication.

How to Download Gated Files

1. Locate and add the Download File action from the app hosting the file.
   
   

2. Provide the gated URL in the configuration.
   
   

3. Run a test to ensure the file is successfully downloaded.

4. The output will be a Keragon-hosted URL, which can now be safely used for further uploads.

Uploading Files

Uploading files is typically required when sending files to apps or cloud storage platforms. You can handle this:

• Directly within a Create/Update action (e.g., Create Patient).

• Using a dedicated Upload File action (e.g., Upload File to Patient Record).

How to Upload Files

1. Locate the Upload File action for the target app.
   
   

2. In the file URL field:

   • If the file is public, use the URL directly.

   • If the file was downloaded, use the Keragon-hosted URL generated from the Download File action.
     
     

3. Complete the remaining configurations for the upload action.

4. Test the step to confirm the upload is successful.

Key Reminders

• Public URLs require no additional steps—use them directly.

• Gated URLs must be processed through a Download File action.

• Always test both downloading and uploading steps to ensure file availability.