Flow Actions
Doc Management Flow Actions
Get Resource Details
introduction the get resource details flow action allows you to retrieve comprehensive metadata details of an external storage resource by inputting known metadata information, even if only a few parameters are available the diagram below offers an overview of the input parameters and includes a visual representation of the flow action detailed explanations of each input parameter and the corresponding outputs will be provided in the following sections what this action does the get resource details flow action accepts certain combinations of input paramaters i e metadata details of a resource and returns the complete metadata information as output for instance, consider the following use case when a new account record is created, an account folder is generated, along with a subfolder named "opportunities" to store folders for all related opportunity records to create an opportunity folder within the "opportunities" subfolder (located under the corresponding account folder), you need the folder id of the "opportunities" subfolder while you can use the get connected folder docid iq8rljf2ne8sx0 iuu action to find the account folder by setting the parent id to the opportunity's account id, you can't directly retrieve the folder id of the "opportunities" subfolder in this case, you know that there is a subfolder named "opportunities" within the account folder therefore, the subfolder's path can be formulated as the account folder's path followed by "/opportunities" this is where the get resource details flow action is useful by inputting the known metadata details such as library , drive id , resource path , and resource type , you can retrieve the resource id (the subfolder’s id) this resource id can then be used to create an opportunity folder within the opportunities subfolder similarly, if you know the library , drive id , resource path and resource type but do not have the resource id , you can retrieve the same using this action since google drive google drive does not have a resource path , retrieving resource id using library , drive id , resource path and resource type is not possible however you can use this for sharepoint sharepoint and dropbox dropbox libraries input parameters let us discuss each of the input parameters in detail in the individual sections given below drive id this is important for google drive & sharepoint libraries only the drive id is a unique identifier for a storage location in both sharepoint and google drive in sharepoint, it represents a document library within a site, while in google drive, it identifies a user's drive or shared drive this is a mandatory input parameter you can get this parameter by viewing metadata details for a folder in the “content library” tab of cloudfiles app in salesforce or can be fetched through other flow actions like get connected folder library the library parameter is the external storage type you are using possible values are sharepoint , google (for google drive), onedrive , azure , dropbox , box , cloudfiles (for aws s3) this is a mandatory input parameter resource id this is the folder id of the target folder whose resource we want to be fetch it is mandatory to fill either resource id or resource path resource path this is the path to the target folder whose resource we want to be fetch it is mandatory to fill either resource id or resource path in order to retrieve file resource details using resource path , the input resource path parameter must include file name along with extension resource type specify file or folder based on the type of resource you are querying it is not mandatory and can be excluded output parameters the action returns complete metadata information of the queried resource docid\ mr7u7qdhigoasucpf nlr drive id the drive id of the queried resource library the library of the queried resource resource id the resource id of the queried file or folder resource resource name the name of the queried resource in case, queried resource type = file , the resource name is output along with extension resource path the complete path for the queried resource in the external storage google drive google drive does not have a resource path you can use this for sharepoint sharepoint and dropbox dropbox type the resource type of the queried resource i e file or folder see it in action the gif below illustrates the use case discussed in the previous section creating an opportunity folder for each opportunity record within the opportunities subfolder of the corresponding account’s folder