Use the iAuditor integration with MS Flow to automatically start or pre-populate an inspection with information from a SharePoint list. A SharePoint list can be a great and powerful way of collectively storing data in a central location. A SharePoint List can cater for a range of different data types across a number of different use cases such as asset management, contact lists, issue tracking and many more.

For our setup, we’ll be using the “Asset Management” example where data will already be stored/entered within a list. Each time a new asset/piece of equipment is added to your asset list, we’ll want to automatically start and pre-populate an Inspection with key pieces of information (eg, Serial Number, Model etc). Once your SharePoint Item is added, you’ll be able to open iAuditor and commence the Inspection!

Getting Started

  1. This setup assumes some knowledge about how SharePoint lists work and an understanding of the JSON data model & the iAuditor API. If you need any additional assistance at any point through this guide, please don’t hesitate to contact us.
  2. You will need to have your iAuditor Template ready to go, see the “prerequisites” section of this guide.
  3. Create and set up your SharePoint list with the relevant custom Columns/fields; these will likely be the same as your Template fields.
  4. For a simple setup, this integration should take as little as 30 minutes to implement.


  1. Start by creating and defining your Template Fields
  2. Create a new Template using our Template creation guide
  3. For our setup, we’ll be using “text” fields from the inspection template’s “information” section (title page)
  4. With our Template created, head into the Microsoft Flow website to begin building our workflow
  5. As mentioned, in this example we’ll be triggering a new Inspection whenever a new Item is added to a Sharepoint list

Setup using MS Flow

  1. To begin, start a new blank flow
  2. Add the “When an item is created” Sharepoint action
  3. With your “action” created, we’ll want to make sure we can easily identify it.
  4. Name your Action by clicking the 3 dots in the left-hand corner and select “rename”
  5. Populate the details of the SharePoint Site & List you’ll be using to automatically start your Inspections
  6. Now we’ve defined our site/list details, we now need to begin mapping our SharePoint List/Column responses to specific parts of our Inspection
  7. Add a new “Variable – Initialize Variable” action by searching and selecting the below
  8. Once added, set the Variable name “Item Data” and set the type to “Object”.
  9. We also recommend renaming the Variable itself by following the same steps we carried out for the “When an item is created” action
  10. To populate the “Value” field, we’ll first need to understand the JSON data model.
  11. Please read through the “Start Inspection”  & “Get Inspection” API documentation to gain a deeper understanding
  12. In our case, we’ll be looking to populate data on our Inspections “Title Page” (header_items). In this example, we’ll be specifically targeting the “Location”, “Prepared By”, “Asset being Inspected”, “Serial Number” and “Client” fields; you’ll find the break down of this detailed below.
  13. Note: this same process can be used for other areas/sections of the Inspection too.
  14. With the “Value” field populated with our target fields, we’ll now need to map the corresponding Sharepoint data.
  15. Click the whitespace next to the “Type of Response data” (as shown above); the “Add Dynamic Content” selector will pop-up for you to pick the relevant data from the Sharepoint List. This is pulled in from our first action – “When an item is created”:

  16. The same steps will have to be repeated for each field you’re looking to pre-populate within the Inspection.
  17. Once you’ve completed mapping your responses, we’ll now need to send this data as an HTTP request to create the Inspection.
  18. Create a new “HTTP – HTTP” Action as below:
  19. Change the HTTP Method to POST & set the URI as “” as detailed within our Start Inspection documentation.
  20. Within the Header field, we’ll need to input our API token. This will need to be entered as Bearer <Insert API Token> (NB: with whitespace between the word Bearer and the token) as shown below:
  21. We’ll now need to grab the data we’ve defined within the “Item Data” variable. Click into the “Body” field to expand the “Dynamic Field” content.
  22. Select the “Item Data” variable to populate the “Body” field.
  23. Save and activate your Flow and head over to your SharePoint List to create a new Item
  24. A new entry should appear on your SharePoint List
  25. Once we’ve entered the necessary data, the Flow will automatically start the Inspection creation process with our pre-populated fields
  26. We can see the Inspection our Flow has created below




Was this article helpful?

We love your feedback. Please tell us what you think.

Yes No
Care to share a bit more so we can continue to make improvements for you? Care to share a bit more so we can make this article even better for you? Thanks for your feedback!