Home/HighLevel/Features/Workflows/HighLevel client portal file upload workflow trigger setup

Workflows and Automation

HighLevel client portal file upload workflow trigger setup

In short

The Client Portal File Uploaded trigger starts a workflow whenever a contact adds a document through the portal. It links the file to the contact record, allowing automatic notifications, task creation, or stage changes, so teams can act without manually checking for uploads.

AreaWorkflows · Workflow Triggers
Used forMortgage brokerage, Digital marketing agency, Property management firm
Setup steps9 steps in 1 task
Last updatedNovember 17, 2026

01Who this is for

  • Founders who run onboarding processes and need immediate acknowledgment of client documents.
  • Agents handling loan applications who must alert reviewers as soon as paperwork arrives.
  • Support teams that require a task to be generated when clients submit required files.

02Client Portal file uploaded workflow triggers, explained

The trigger fires when a contact uploads a supported file via the Shared Documents area of the Client Portal. The uploaded file is attached to the contact's record and stored under Contacts > Documents > Received > Client Portal. Once the event occurs, any actions placed after the trigger run in sequence.

This trigger is managed inside the Automation > Workflows builder. After adding the trigger, you attach actions such as email, SMS, internal notification, task creation, tag addition, contact field update, opportunity movement, or webhook calls. You can also include waits, conditions, or additional actions to match your process.

A workflow must be published for the trigger to react to live uploads. Testing with a real client portal upload confirms that the file is stored correctly and that each action executes as designed.

03How businesses use Client Portal file uploaded workflow trigger

  • Mortgage brokerage. The broker adds a trigger that sends an internal notification and creates a review task each time a borrower uploads income statements. The workflow runs automatically, keeping the underwriting team informed.
  • Digital marketing agency. The agency sets up an action to email a client a confirmation receipt after they upload brand assets. The email includes next step instructions, ensuring the client knows the process continues.
  • Property management firm. When a tenant uploads a lease renewal form, the workflow updates a custom field on the contact record and moves the related opportunity to the “Renewal in Review” stage.

04The numbers and rules that matter

  • Supported document formats:.PDF,.doc,.docx,.xls,.xlsx,.ppt,.pptx,.txt,.rtf.
  • Supported image formats:.jpg,.jpeg,.png,.gif.
  • Video formats such as MP4, MOV, AVI, MKV, and WMV are not supported.
  • A client can select up to 10 files in one upload.

05Before you start

  • The contact used for testing must have active Client Portal access and be able to open the Documents or Shared Documents area.

06How to set up and use Client Portal file uploaded workflow trigger in HighLevel

Set up the Client Portal File Uploaded workflow trigger

  1. Make sure the test contact can log into the Client Portal and view the Documents section.
  2. Go to Automation > Workflows and either create a new workflow or edit an existing one.
  3. Click Add New Trigger, type “Client Portal File Uploaded”, and select it from the list.
  4. Configure any trigger filters or settings that are needed for your scenario.
  5. Click the plus button beneath the trigger to add the first action that should run after the upload.
  6. Choose the appropriate action, such as sending an email, internal SMS, creating a task, adding a tag, updating a field, moving an opportunity, or firing a webhook.
  7. Insert any additional actions, wait steps, or conditional branches required by your process.
  8. Save the workflow to make it active.
  9. Run a live upload with the test contact to verify that the trigger fires and the actions execute.

07What it looks like in HighLevel

08Settings that matter

  • Client Portal File Uploaded. Triggers a workflow when a contact uploads a supported document through the portal’s Shared Documents feature.

09Things to know before you rely on it

  • Supported document formats are PDF, DOC, DOCX, XLS, XLSX, PPT, PPTX, TXT, RTF, JPG, JPEG, PNG, and GIF.
  • Video file types such as MP4, MOV, AVI, MKV, and WMV cannot be uploaded via the Client Portal.
  • A client can select up to 10 files in a single upload operation.

10If something goes wrong

  • Workflow did not run after a client uploaded a file.. Open the workflow and check Execution Logs and Enrollment History. Confirm the workflow is published, the contact has Client Portal access, the file type is supported, and the upload completed without error.

11How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

This trigger is worth the effort for any business that relies on client submitted documents. It removes the constant need to watch records and helps keep onboarding or approval steps moving forward.

Avoid the mistake of testing with a file type that isn’t supported; the workflow will not fire if the upload fails.

Get More InformationOpens on HighLevelPublished November 3, 2026 · Updated November 17, 2026

Common questions

Common questions about Client Portal file uploaded workflow trigger.

How does the Client Portal File Uploaded trigger differ from the Documents & Contracts trigger?

The File Uploaded trigger activates only when a contact uploads a file through the portal’s Shared Documents area. The Documents & Contracts trigger reacts to actions like sending, viewing, signing, completing, or declining a HighLevel document or contract.

Will sharing a file from HighLevel start this trigger?

No. Sharing a file makes it available for the client to download, but the trigger only responds to files that the client actively uploads through the portal.

Should I test the workflow with a test contact or a live upload?

A live upload from a test contact is recommended because it confirms that the portal event, file storage, and all workflow actions work together.

Where can I investigate why a workflow didn’t fire?

Open the workflow and review the Execution Logs and Enrollment History. Also verify that the workflow is published, the contact has portal access, the file type is allowed, and the upload completed successfully.

What file types can clients upload to trigger this workflow?

Clients can upload PDFs, Word, Excel, PowerPoint, text, RTF, and image files (JPG, JPEG, PNG, GIF). Video formats are not supported.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.