Skip to main content
Connect your qrtub Links to SafetyCulture inspections, enabling staff to scan equipment and immediately open the right inspection template.

​
Overview

SafetyCulture (formerly iAuditor) is a mobile inspection platform. By integrating with qrtub, you can:
  • Open specific inspection templates by scanning equipment
  • Pre-fill inspection data using URL Templates
  • Route different users to different inspection types
  • Maintain inspection access even if you switch platforms later

​
Integration Method

qrtub integrates with SafetyCulture using deep links - special URLs that open SafetyCulture directly to a specific inspection, template, or report. SafetyCulture supports two deep link formats:
  • Mobile app (iauditor://) - Opens the SafetyCulture mobile app
  • Web app (https://app.safetyculture.com/) - Opens in web browser

​
Getting Your Template ID

Before setting up deep links, you’ll need your SafetyCulture Template ID:
  1. Open SafetyCulture web app
  2. Navigate to your inspection template
  3. Copy the Template ID from the URL
  4. Example: template_fcbc86fd41a74180921347e4be53bdf2
See SafetyCulture’s guide on getting entity IDs for detailed instructions.

​
Basic Setup: Start Inspection

In your Item’s Profile Page, add a new Destination: Destination Name: Start Inspection Destination URL: iauditor://template/new_audit/<template_id> Example: 
iauditor://template/new_audit/template_fcbc86fd41a74180921347e4be53bdf2
Alternatively, use a web app deep link for users who prefer desktop/browser access: Destination Name: Start Inspection (Web) Destination URL: https://app.safetyculture.com/inspection/new?templateId=<template_id> Example: 
https://app.safetyculture.com/inspection/new?templateId=template_fcbc86fd41a74180921347e4be53bdf2

​
Using qrtub URL Templates

Use qrtub’s URL Template feature to automatically insert template IDs from your Item data: Destination URL: iauditor://template/new_audit/{templateID} Why this matters for bulk deployment: Configure the Destination once with a template placeholder. Each Item in your Tub can have a different templateID field value—some use the forklift inspection template, others use the excavator template. One Destination configuration serves all equipment types, with each QR code routing to its specific inspection template automatically. This allows different Items to use different SafetyCulture templates based on their Item data—no manual configuration per Item.

​
Advanced: Pre-Fill Inspection Questions

SafetyCulture allows you to pre-fill specific inspection questions using question item IDs.

​
Mobile App Pre-Fill Format

iauditor://template/new_audit/<template_id>?<item_id>=<response>
Example with qrtub URL Templates: 
iauditor://template/new_audit/template_fcbc86fd41a74180921347e4be53bdf2?8f2f287e-be6e-470c-a2e2-a0fd8ab966ae={assetID}
Where:
  • template_fcbc86fd41a74180921347e4be53bdf2 is your SafetyCulture template ID
  • 8f2f287e-be6e-470c-a2e2-a0fd8ab966ae is the question item ID in your template
  • {assetID} is the qrtub Item field placeholder—automatically filled with each Item’s actual asset ID
Bulk deployment benefit: Configure this URL template once. Deploy to 500 pieces of equipment. Each QR code scan automatically pre-fills the inspection with that specific equipment’s asset ID. No manual setup per Item.

​
Pre-Fill Multiple Questions

Use & to pre-fill multiple questions: 
iauditor://template/new_audit/<template_id>?<item_id_1>=<response_1>&<item_id_2>=<response_2>
Example: 
iauditor://template/new_audit/template_fcbc86fd41a74180921347e4be53bdf2?8f2f287e={assetID}&a2e2a0fd={location}
Important notes:
  • You need the specific question item ID from your SafetyCulture template (not arbitrary parameter names)
  • To get question item IDs, see SafetyCulture’s entity ID guide
  • Responses may need URL encoding depending on content
  • Very long deep links may not work consistently
Beyond starting new inspections, you can create Destinations for other SafetyCulture actions:

​
View Inspection Report

Mobile: iauditor://audit/<inspection_id> Web: https://app.safetyculture.com/report/audit/<inspection_id> With qrtub URL Template: 
https://app.safetyculture.com/report/audit/{inspectionID}
Store the latest inspection ID in each Item’s inspectionID field. When someone scans, they’re automatically routed to that Item’s most recent inspection report.

​
Edit Existing Inspection

Mobile: iauditor://audit/<inspection_id> Web: https://app.safetyculture.com/inspection/<inspection_id>

​
Open Asset Profile

Mobile: iauditor://asset/profile/<asset_id> Web: https://app.safetyculture.com/assets/<asset_id> Example use case: Link qrtub Items directly to their SafetyCulture asset profiles.

​
View Document/File

Web: https://app.safetyculture.com/documents/<document_id>

​
Use Cases

Equipment Inspections
  • Excavators, forklifts, vehicles
  • Pre-start checklists
  • Daily safety inspections
Facility Inspections
  • Fire extinguishers
  • Emergency equipment
  • Building systems
Multi-Audience Routing Create a Profile Page with multiple Destinations:
  • Operators see “Start Inspection” → Start new inspection
  • Managers see “View Report” → View latest report
  • Maintenance see “Asset History” → SafetyCulture asset profile

​
Troubleshooting

Mobile app doesn’t open:
  • Ensure SafetyCulture mobile app is installed on the device
  • Verify Template ID format is correct
  • Check that the user has access to the template in SafetyCulture
Web link doesn’t work:
  • Verify user is logged into SafetyCulture web app
  • Check that the user has permission to access the entity (template, inspection, asset)
  • Confirm the entity ID is correct
Data not pre-filling:
  • You need the specific question item ID from your SafetyCulture template (not arbitrary field names)
  • Ensure Item fields in qrtub contain data
  • Test that URL encoding is correct for special characters
  • Verify deep link isn’t too long (keep it under ~2000 characters)
Users need access: Deep links only work if users have permission to access the relevant entities in SafetyCulture. Ensure your team has appropriate access before deploying.

​
Resources