Microsoft Flow allows you to build workflows that interconnect many different software services (up to 120 and growing). iAuditor’s integration with Flow allows you to tap into this capability and connect your auditing data with their ecosystem.

A flow from iAuditor to SharePoint looks like this.

The iAuditor Microsoft Flow Connector supports the following capabilities:

  1. Retrieve a list of inspections modified in a given date range
  2. Transfer PDF and MS Word inspection reports from iAuditor to another service like Outlook, SharePoint, MS Teams or other
  3. Get easily shareable inspection web report links
  4. Generate links that will take a user directly to an inspection within iAuditor
  5. Retrieve raw inspection metadata like the title, location etc. of a given inspection (but not the raw inspection responses)

Set it up in minutes with this guide.


1. Microsoft imposes limits on

  • how many calls a connector can perform per minute. This is a hard limit, 100 calls at the time of writing
  • how many times the connector can run in a month. More runs can be purchased on demand as needed
  • various limits for interacting with SharePoint – see here

2. SafetyCulture known limitations

  • If the “search modified inspections” step failed for any reason (e.g. iAuditor API is down for maintenance), inspections may be missed.
  • Some media (images) may not have completed uploading to the iAuditor backend if an inspection report export is requested immediately after conducting the inspection.

3. Limits are also likely to apply to the connector of the service MS Flow is connecting to at the other end. Check the relevant documentation of that service for details


MS Flow supports a comprehensive list of certifications and more.

Inspection data is transferred in plaintext over a secure TLS connection. No iAuditor data is stored by Microsoft, the connector is only used to transfer data from one service to another.


1. If no call to the iAuditor API is made within 30 days the iAuditor credentials will expire and need to be renewed. To configure iAuditor authentication in Flow see this article.
2. If the connector fails at any particular step continuously it may get disabled. To find details of any error see the Flow run history – depending on the source of the error contact Microsoft (for Flow), SafetyCulture (for iAuditor) or any 3rd party connector support.


For information on how to automatically export inspections using Microsoft Flow, visit this article.

Helpful links