Documentation
Start typing to search…

Find Item


Definition

The Find Item action allows a user to locate and retrieve a specific item from a SharePoint list by using its unique identifier. This action is fundamental for workflows that need to access, update, or process individual records stored within a SharePoint environment.

Key capabilities:

  • Locate a specific item using its unique Site ID, List ID, and Item ID.
  • Specify which columns of data to return, optimizing data retrieval for subsequent actions.

This action provides a direct way to fetch precise data from SharePoint, enabling targeted automation and integration with other business processes.

Inputs

  1. Connection Establishes the authenticated connection to your SharePoint environment, allowing the action to access your sites and lists securely.
  2. Site ID The Site ID is a unique identifier for a SharePoint site (or a Microsoft 365 Group site) within an organization's SharePoint environment. Every SharePoint site, including team sites, communication sites, and OneDrive for Business sites, has a unique Site ID that must be provided to locate the correct list.
  3. List ID Each site can contain multiple lists. You must provide the unique ID for the specific list where the item resides. You can either enter a List ID directly or select a list from the drop-down menu that appears after the connection is established.
  4. Item ID The Item ID is a unique identifier for a specific item within a SharePoint list. Each item in a list is assigned a distinct ID by SharePoint, which is required to find and retrieve the exact record.
  5. Columns to Return Select the specific columns from the SharePoint list that you want the action to retrieve in its output. This allows you to limit the data returned to only what is necessary for your workflow, improving efficiency.

Outputs

  1. Site ID The unique identifier of the SharePoint site where the item was found.
  2. List ID The unique identifier of the list containing the retrieved item.
  3. ID The unique identifier of the item that was found.
  4. GUID The Globally Unique Identifier (GUID) of the item.
  5. Created Date/Time The date and time when the item was originally created in the SharePoint list.
  6. Last Modified Date/Time The date and time the item was last modified.
  7. Hyperlink An object containing the details of a hyperlink field, if present on the item.
  • Description: The descriptive text for the hyperlink.
  • Url: The full URL of the hyperlink.
  1. Date The value from a date-specific column in the list item.
  2. Currency The numerical value from a currency-specific column in the list item.

Example Use Cases

  1. Update Specific Records Find a specific item by its ID to update its status, details, or assignments as part of an automated business process.
  2. Retrieve Details for Approval Workflows Fetch the complete details of a submitted request from a SharePoint list to provide approvers with all the necessary information.
  3. Sync Data with External Systems Locate a SharePoint item to retrieve its latest data and update a corresponding record in a separate application like a CRM or ERP system.
  4. Archive Specific Items Find an item based on an external trigger, such as a project closing, in order to move its data to a separate archive list for record-keeping.

Example

Scenario: An HR department uses a SharePoint list called "Leave Requests" to manage employee time-off applications. When a manager approves a request via an external system (like a simple form), the workflow receives the unique Item ID of that request. The automation must then find the specific request in the SharePoint list to retrieve the employee's name and the requested dates before proceeding to update the payroll system.

Steps to Implement:

  1. Initiate the workflow with a trigger, such as a "Webhook" or "Form Submission" trigger, which provides the ItemID of the approved leave request.
  2. Add the Find Item action to your flow.
  3. Configure the action with the following settings:
  • Connection: Select your established SharePoint connection.
  • Site ID: Choose the HR department's SharePoint site from the dropdown list.
  • List ID: Select the "Leave Requests" list.
  • Item ID: Use the token picker to insert the ItemID received from the workflow's trigger.
  • Columns to Return: Select only the columns needed for the next step, such as "EmployeeName", "StartDate", and "EndDate", to optimize performance.
  1. Use the outputs from the Find Item action in subsequent steps, such as a "Send Email" action to notify the employee or an action that connects to the payroll system to log the approved leave.

Outcome: By using the Find Item action, the workflow can precisely target and retrieve the correct leave request without needing to search through the entire list. This ensures that the correct employee's data is used for subsequent actions, eliminating manual lookup errors and significantly speeding up the process from approval to final system update.

Best Practices

  1. Use Dynamic Item IDs For flexible and reusable workflows, always provide the Item ID dynamically using a token from a trigger or a previous action. Hardcoding the ID limits the workflow to a single, static item.
  2. Limit Columns to Return To improve workflow performance and reduce unnecessary data processing, only select the specific columns you need for subsequent steps in the "Columns to Return" field. Avoid retrieving all columns if you only need one or two pieces of information.
  3. Implement Error Handling Add an error handling branch to the action to manage cases where the specified Item ID is not found. This prevents the workflow from failing and allows you to define a fallback process, such as sending a notification that the record could not be located.
  4. Verify Site and List Selection Always double-check that you have selected the correct Site ID and List ID. Using the dropdown menus is recommended, as it ensures the IDs are valid and reduces the risk of configuration errors that could lead to the workflow failing to find the item.

Updated about 2 hours ago