HubSpot administrators can use the WoodsPortal CopyResource workflow action to copy a file or folder to another File Manager location and associate the copied resource with the record enrolled in the workflow.
Before you begin
- Confirm that the WoodsPortal app and required file-manager extension are installed and authorized.
- Use a HubSpot workflow for a supported record type and a safe test record.
- Identify the exact source file or folder path and the intended destination path.
- Identify the WoodsPortal portal ID that should own the copied resource association.
Configure the workflow action
- Open the intended HubSpot workflow and define its enrollment criteria.
- Add the WoodsPortal Copy Resource action, then set Target record to Enrolled contact or the record appropriate for the workflow.
- Enter the Portal ID for the intended WoodsPortal implementation.
- Enter Path to File/Folder for the file or folder to copy.
- Enter Destination. Use / for the root or specify the destination folder path.
- Use HubSpot personalization tokens only when the resolved path and destination values will be valid and predictable.
- Review the action and test it with the safe record.
Expected behavior
- The source resource remains in its original location. CopyResource does not move or delete it.
- The supported action can copy a file or a folder to the configured destination.
- The copied resource is associated with the record that triggered the workflow.
- Nested destination paths should be tested to confirm that the intended folder structure exists or is created by the current action version.
Troubleshooting
- If the action is missing, confirm the installed app version and workflow actions available in the connected HubSpot account.
- If the source is not found, compare the complete source path, including capitalization and folder hierarchy.
- If the copy lands in the wrong location, review the destination root slash, nested path, and resolved personalization values.
- If the copied resource is not associated with the record, confirm that the workflow object type is supported and review the action result.
- If the action fails, check File Manager access, WoodsPortal authorization, invalid path characters, and empty personalization values.
Figure: Configure Copy Resource with Target record, Portal Id, Path to File/Folder, and Destination. A resulting copied-resource screenshot is still needed.