Move Resource Action

introduction the move resource action by cloudfiles is used to move the file from one destination to another destination e g once the deal stage gets updated you want to update the location of the files stored in any of your cloud storage folder to another folder, here the move resource flowaction comes into play to make sure this action works with your cloud storage, you need to understand what is an 'automation user' and how does it work? docid 9ibd0tgbyrtn kgjpxhtn input parameters the "move resource" action takes in various parameters to specify the source & destination of the file library the desired library where the file must be moved (e g sharepoint, google drive etc ) path to resource the exact path to the file, including the file name and extension there may be more than one parameters required to specify this path based on library selection path to destination the exact path to destination where the file must be moved there may be more than one parameters required to specify this path based on library selection return values various values returned by this action after execution these parameters have been detailed in the section below 1 library the cloud storage from where the file is to be moved from anything between cloudfiles, onedrive, sharepoint, box or dropbox can be selected based on your choice, new parameters would become visible in the action these are discussed in the sections below 2 path to resource this specifies the source from where the files must be picked you can specify the full path using a simple '/' separated string with the file name at the end the path to the folder can be copied from the metadata on the cloudfiles dashboard and then personalized using the record tokens follow the simple steps below 1\ find the cloudfiles widget from any hubspot record, and click on cloudfiles it will redirect you to app cloudfiles io https //app cloudfiles io/ 2\ under the libraries tab, navigate to the file or folder that you are trying to add 3\ copy the parameter from the meta data on the right side of the screen these meta deta example is shown below 3 path to destination this specifies the destination where the files must be moved to thus you can specify a different file name and rename the file through this action you can specify the full path using a simple '/' separated string with the file name at the end the path to the folder can be copied from the metadata on the cloudfiles dashboard and then personalized using the record tokens to copy the full folder path from metadata, follow the steps in the path to resource section above 4 shared drive id / drive this is important for google drive & sharepoint library selection both these cloud storage have multiple drives where files can be stored e g google drive has my drive & shared drive while sharepoint can have multiple drives inside multiple sites this parameter helps cloudfiles identify which drive to pick / push the file the drive id can be copied using the meta data in cloudfiles dashboard as shown in the steps in the path to resource section above return values the move resource action returns the following values these can be used in later actions to chain together actions and create complex automations 1\ action status this is a success or failure message based on whether the action executed correctly