Skip to content
RTI

Integrations

Integrations that keep the inspection record in one place

Ready To Inspect keeps the inspection record and shares it with the tools around it: reviewed inspections into Smartsheet, signed webhooks to your own endpoint, and a read-only API for your own reports.

Start freeSee them in the demo
  • One way, out of RTI
  • Set up by workspace admins
  • Secrets shown once

Ready To Inspect

The record: inspections, photos, approvals and the activity log

  • Smartsheet integration

    Writes to Smartsheet

  • Webhooks

    Sends to your endpoint

  • Read API

    Read by your system

Inspection data runs one way, out of RTI. Nothing that comes back changes the record.
What it connects to

Pick the connection that fits how you work

  1. ConnectorWrites to Smartsheet

    Smartsheet integration

    Ready To Inspect pushes approved and rejected inspections into your Smartsheet tracker, matched on the tag column, queued and retried. One way.

    • One way, RTI to Smartsheet
    • Matched on the tag column
    • Queued and retried
    See the details: Smartsheet integrationWalk through it: Smartsheet integration
  2. For developersSends to your endpoint

    Webhooks

    Ready To Inspect webhooks post signed JSON to your HTTPS endpoint when an inspection is submitted, approved or sent back, or signed off. Queued and retried.

    • Signed with HMAC-SHA256
    • Four events, plus a test
    • Queued, retried, replayable
    See the details: WebhooksWalk through it: Webhooks
  3. For developersRead by your system

    Read API

    Ready To Inspect's read-only API returns your projects, tags and inspections as JSON, up to 200 rows a page, behind a token scoped to your workspace.

    • Read-only JSON
    • Scoped to one workspace
    • 120 requests a minute
    See the details: Read APIWalk through it: Read API

Don't see the tool you run? Tell the founder what it is.

The rules

Every integration keeps the same rules

One way, out of RTI
Nothing an integration does can change an inspection, an approval or the activity log. Smartsheet sync writes out, webhooks send out, and the API only reads.
Admins hold the keys
Only a workspace admin can connect Smartsheet, add a webhook endpoint or create an API token.
Secrets shown once
The Smartsheet token and webhook signing secrets are stored encrypted, API tokens only as a hash, and none is shown again once it is saved.
Queued and retried
Smartsheet pushes and webhook deliveries are queued before they are sent, tried up to five times, and flagged to admins when one runs out of retries.
One workspace each
Every token, endpoint and sheet connection belongs to one workspace and sees nothing outside it.
The proof stays in RTI
Photos, signatures and the tamper-evident activity log stay in RTI. Integrations carry an inspection's status, names, dates and reviewer notes.

Records that leave RTI without an integration

Questions about RTI integrations

6 answers

What does Ready To Inspect integrate with?
Smartsheet, webhooks and a read-only API. RTI writes reviewed inspections into a Smartsheet tracker, sends signed webhooks to any public HTTPS endpoint you run, and lets your own systems read projects, tags and inspections through the API.
Which RTI integration should I use?
Smartsheet if your team already tracks inspections in a sheet. Webhooks if your own system should act when an inspection is submitted, approved, sent back or signed off. The read API if your reports should pull inspection data on their own schedule. A workspace can use all three at once.
Can an integration change the inspection record?
No. Smartsheet sync writes out of RTI, webhooks only send, and the API only reads. Approvals, photos and the tamper-evident activity log change only inside RTI, by the people your workspace allows.
Can RTI connect to a tool that is not listed here?
Yes, if the tool can take a webhook or call an API, directly or through code or an automation service you run. RTI's webhooks post signed JSON to any public HTTPS address, and the read API answers any system that holds a token. RTI does not build a dedicated connector for it.
Who can set up an integration?
Only a workspace admin. Connecting Smartsheet, adding a webhook endpoint and creating an API token each need the admin role, and each belongs to that admin's workspace.
Do photos leave RTI through an integration?
No. Integrations carry an inspection's status, names, dates and reviewer notes. Smartsheet can also carry the checklist name, the compliance result, the location, the photo count and a link back to RTI. Photos and signatures stay in RTI and go out in the turnover package, which anyone can check on the verify page.

See it on a real job.

Tag one area, run one walk, and see the record it leaves behind.

Start freeSee how it works

30-day trial · No card required