Skip to content

Build or run

Should you build integrations yourself with AI?

Build them with AI. Yes. Your coding agent writes a working integration fast.

Run them yourself. Usually no. That work starts with the first API call and never ends.

Who does what

AI writes the code. Someone still has to run it.

Above the line is the part your agent writes fast. Below it is what keeps working for every customer, for one integration or a hundred.

Your AI agent writes this

integration.jsonmappings.jsonataSettings.tsx
  1. "auth": { "type": "oauth2" }// integration logic
  2. name: first_name & " " & last_name// field mappings
  3. <ConnectButton integration="salesforce" />// your product
AI writes everything above this line. Truto runs everything below it.

Truto runs this

All systems running

InfrastructureNo servers to deploy, scale or patchrunning
OAuth appsApproved by vendors, such as Google CASA Tier 2approved
Customer loginsEncrypted, and refreshed for every customerrefreshed 3s ago
2 a.m. failuresHandled without paging your teamhandled
Security reviewsSOC 2 Type II and ISO 27001reports ready

85integrations shipped in one sprint

50 integrations, in-housea year
On Trutoa couple of weeks

“We could maybe build 50 integrations a year… or we can do it in a couple of weeks with Truto.”

Annie GregoryPrincipal Product Manager
Read the Thoropass case study →

Compare

What you own after your agent is done.

The same AI writes the integration in both columns. The difference is who runs it in production.

Vendor OAuth apps

You run itRegister an app with every vendor. Pass each review.

Truto runs itFor catalog apps, Truto’s approved apps work from day one.

Google review

You run itA CASA security assessment, again every 12 months.

Truto runs itTruto’s Google app is CASA Tier 2 verified.

Customer logins

You run itEncrypt every token. Refresh without two workers racing.

Truto runs itAES-256 at rest. One refresh per account, under a lock.

Rate limits

You run itLearn how each vendor says “slow down”.

Truto runs itA standard 429, with Retry-After when the vendor gives one.

Webhooks

You run itKeep an endpoint up. Check each vendor’s signature.

Truto runs itVerified per vendor, then sent to your URL.

Vendor changes

You run itFind out from errors. Fix. Redeploy your app.

Truto runs itThe fix is live on apply. No deploy.

Custom fields

You run itFork the mapping for each customer.

Truto runs itOverride the mapping per account.

Security reviews

You run itTokens and logs join your audit scope.

Truto runs itSOC 2 Type II and ISO 27001. Not stored by default.

The next integration

You run itAdds to every row above.

Truto runs itRuns on the same runtime as the first.

FAQ

Common questions.

When should I build integrations myself instead of using Truto?

Build them yourself with your coding agent, and run them on Truto from the first API call. Even one integration needs an OAuth app, token refresh, rate-limit handling and webhook checks. Run that yourself only when your team wants to own the runtime and has time to keep it up.

Can my coding agent build integrations on Truto?

Yes. Install the Truto skills in Claude Code or Cursor, then ask for the integration. Your agent runs truto integrations build with the vendor’s API docs, then lints, verifies and applies the file. See Build.

Does Truto store my customers’ data?

Not by default. Data is fetched in real time from the vendor’s API and passed through to you. Features that store data, such as SuperQuery, are off until you turn them on. Credentials are encrypted at rest with AES-256.

Let your agent build it. Let Truto run it.

Get a sandbox, install the Truto skills, and ask for the integration your customers need.