Skip to content

A picture: Truto in the middle, with lines out to apps such as Salesforce, HubSpot, QuickBooks, Slack, Gmail, Jira, Xero, Zendesk. Small dots move along the lines. When one connection breaks, Truto fixes it.

Used by teams at

  • 15Five
  • Sprinto
  • Thoropass
  • Spendflo
  • Springworks
  • Smart Tribune
  • BalkanID
  • Workweek
  • Cloudficient
  • Regodit
  • Naq
  • Komplai
  • Evergrowth
  • Mesha
  • DocsBot
  • SiteGPT
  • Spark2
  • Senja
  • Claira
  • ZenAdmin
  • Omnitrain
  • Equs

Why the build is not the hard part

AI can write an integration.

Keeping it working is the hard part.

Truto does that work for every connection and every customer. At any scale.

Customers

Months of work, done in weeks. Sometimes in hours.

85+ integrations in one sprint

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

Annie GregoryPrincipal Product ManagerRead the Thoropass case study →

2 to 17 integrations in a few hours

“We went from 2 integrations to 17 integrations in a few hours. Without Truto, that would have taken us at least 4 months.”

PrabodhVP of EngineeringRead the Sprinto case study →

01 Ship

Every customer connects their own account.

Your customer clicks Connect inside your product and signs in to their own app. That is all they do.

  1. 1 Your Connect screen

    It looks like your product

    Your customer picks an app on a Connect screen with your name and your logo.

  2. 2 The app’s own sign-in

    They sign in to their own app

    They sign in on the app’s own screen, or paste a key from the app. Truto keeps the login, so your team never handles it.

  3. 3 Back in your product

    Then your product uses the data

    With your customer’s permission, your product can read and update their data in that app. Your AI features can work with that data too.

    For developers: see what your code calls →

“…we had our first early adopter customer connect to both ms teams and outlook calendar today - the connection process was smooth.”

Nathan Baldwin15FiveRead the story →

02 Maintain

Every connection has to keep working.

After launch, things break with no warning. Here is one connection over its first year, without Truto and with Truto.

  1. Launch day

    Your customer connects

    Without TrutoConnectedEverything works.

    With TrutoConnectedEverything works.

  2. Month 2

    The login runs out

    Without TrutoSigned outYour customer finds it before your team does.

    With TrutoStill signed inTruto renewed the login before it ran out.

  3. Month 5

    The app changes how it works

    Without TrutoSync stopsAn engineer stops product work to find the cause.

    With TrutoWorking againTruto fixed it once, for every customer. For apps in the catalog.

  4. Month 9

    Your customer removes access

    Without Truto“Something went wrong”Your customer writes to support.

    With Truto“Reconnect”Truto tells your product. Your customer signs in again.

“Overall, the net impact is that a small engineering team can support a broad integration catalog without getting buried in per-provider maintenance.”

Karan SinghFounding Engineer, Regodit. From a G2 review.
For developers: the rule behind each event, and nine more

Login renewal

An OAuth token expires.

Truto renews it shortly before it expires. Each account renews under its own lock, so two requests at the same moment cause one renewal. A 30-second watchdog clears a stuck one.

Vendor changes

A field moves or an endpoint is retired.

An integration is a file, not code in your app. truto integrations apply puts one fix on every connected account, with no deploy on your side.

Rate limits

A vendor sends its limit as a 429, a 200 or a 403.

Your app gets a standard 429 with Retry-After when the vendor gives one (is_rate_limited). A sync run waits, then continues.

Lost access

The vendor refuses the renewal.

Truto sets the account to needs_reauth and sends the webhook integrated_account:authentication_error.

Hidden errors

A vendor puts an error inside a 200.

Where an integration sets error_expression, Truto reads the response body and returns a real HTTP error to your app.

Webhooks

Each vendor signs and shapes its webhooks differently.

In: HMAC, basic, bearer or JWT checks, where the vendor signs. Out: one format, signed with HMAC-SHA256, 5 attempts in 5 minutes.

Pagination

Every API pages its results differently.

Six pagination styles: page, cursor, link header, offset, range and dynamic. Your app always gets next_cursor.

Retry-After

The header can be an HTTP date or a number of seconds.

Truto reads both, or a vendor’s own header through an expression.

Query arrays

One API wants ids=1,2. The next wants ids[]=1 or ids=1&ids=2.

Four array formats (comma, brackets, indices and repeat), set for each integration or method.

Request bodies

Not every API takes JSON.

JSON, form-encoded, multipart, XML and raw bodies. XML responses come back as JSON.

Redirects

A download can redirect to another host, such as a file store.

A method can follow the redirect without sending your customer’s credentials to the new host.

Auth

OAuth 2.0 is only one of many schemes.

Seven auth types, from API keys and OAuth 2.0 to OAuth 1.0a, JWT bearer and AWS STS.

03 Scale

One system, for one integration or a hundred.

Every new integration and every new customer adds more connections to look after. Truto runs them all on one system, so your team does not run any of it.

“Integration with many ATSs in a short amount of time with little maintenance requirements.”

Sean KennyCEO, Spark2. From a G2 review.Read the story →

Is the app you need already here?

1050+ integrations in 50+ categories.

Already in the catalog

Truto builds these and keeps them up to date. When an app changes, Truto fixes the integration for all your customers.

Not here yet

Your team’s AI coding tool can build it from the app’s public documentation, and it runs on Truto like the rest. Or ask us, and Truto’s engineers build it for you.

For each team

One system. A different win for each team.

Pick your team to see what changes for you.

Engineering

Your AI coding tool builds it. Truto runs it.

Tell your AI coding tool what you need. It builds the integration from the app’s public documentation, and Truto runs it for every customer. Each customer’s login, the app’s limits and its changes stay out of your code.

Set-up steps for developers →

8 minutesTruto pointed Workweek’s engineer to its CLI. 8 minutes later, he was making calls to Salesforce in his sandbox.“I made a change on our sandbox using the CLI. I listed and deleted an Event.”Matt Kindy, WorkweekRead the story →

Product

Say yes to the apps your customers ask for.

1050+ integrations in 50+ categories. When an app is missing, your team’s AI coding tool builds it, or Truto’s engineers do.

Search the catalog →

6 CRMsEvergrowth had 6 CRMs live within a month of signing.Read the story →

Customer Success

Fewer tickets about broken connections.

When a login runs out, Truto renews it. When a customer removes access, Truto tells your product, so it can ask them to sign in again. Your team talks to Truto’s engineers in a shared Slack channel.

See all customer stories →

5 minutesSprinto’s average wait for a reply from Truto’s engineers in Slack. One feature Sprinto asked for shipped in 15 minutes.“They are available round the clock, and they’re quick to jump in and assist us with any questions or issues, ensuring that we never get stuck.”Prabodh, VP of Engineering, SprintoRead the story →

Start

Start with one sentence.

If your team builds with an AI coding tool, such as Claude Code or Cursor, tell it what you need in plain words. Truto teaches the tool the rest.

An example. Acme Payroll is a made-up app that is not in the catalog. The build step uses your own AI key.

Support and security

Engineers on your side. Your data stays yours.

“They’ve been hands-on in Slack, shipped features fast, and helped us solve the real-world sync edge cases that show up only in production.”

Aaron EdwardsCEO, DocsBotRead the DocsBot case study →
  • A shared Slack channel You talk to Truto’s engineers.
  • A new integration by Thursday If the app you need is not in the catalog.
  • Help to move from another vendor DocsBot moved to Truto in under 30 days.

Truto passes your customers’ data through. It is not a second copy of their app.

Your product reads and writes the data in your customer’s own app, in real time, through Truto.

What Truto does keep, and why

  • Each customer’s loginEncrypted (AES-256), so your customer stays connected. Kept while connected.
  • A log of each requestIts address and result, so your team can see what happened. 30 days, or 90 on Enterprise.
  • Notices that data changedSo a missed notice can be sent again. Up to 30 days.
  • The reply to a writeSo a retry does not make the same change twice. About 1 day.

Need your own deployment? On the Enterprise plan, Truto runs one only for you.

Trust Centre →

Customers

What teams got done with Truto.

The result first, then their own words, from case studies, G2 reviews and our shared Slack channels.

  • SpendfloMoved from Merge

    Spendflo moved from Merge to Truto.

    “After carefully evaluating multiple unified APIs, we’re confident that partnering with Truto was the optimal choice for our organization. The caliber of Truto’s product and the quality of their support have validated our decision.”

    Ajay VardhanCTO, SpendfloCase study →

  • 15Five21 integrations live

    15Five’s Slack and calendar data landed in its own storage.

    “Just letting you know we were successful getting slack and calendar data landing in S3 today - great work, and thank you for your help! Huge progress.”

    Nathan Baldwin15FiveCase study →

  • BalkanIDAvalara ready in 1 day

    Truto added Avalara for BalkanID the day before a customer demo.

    “The demo went quite well. Thank you so much, Truto team, for the quick turnaround on this.”

    Gokul RamBalkanIDCase study →

  • ThoropassWon a deal on new integrations

    Thoropass builds its access review integrations on Truto.

    “We’re having a great closing week at Thoropass! Won a deal because of some of the integrations we’re working on this morning specifically because of the work this team is doing.”

    Annie GregoryPrincipal Product Manager, ThoropassCase study →

  • Senja3 integrations in one day

    Senja set up its integrations with Truto.

    “With Truto, we were able to get fully set up with 3 integrations in just one day when previously, it would have taken up to a week.”

    Wilson WilsonCTO, Senja

  • Thoropass85+ integrations in 2 weeks

    Thoropass added 85+ access review integrations in one sprint.

    “I think you guys are doing something really cool, both from the tech and the pricing side. It all just makes sense, and it works so well. So very happy to use your system.”

    James FletcherProduct Manager, Integrations, ThoropassCase study →

  • WorkweekNo auth flows to build

    Workweek offers its customers CRM and Google Analytics connections through Truto. From its G2 review:

    “Truto lets us offer our customers CRM and Google Analytics connections from one integration layer, so we don’t have to build and maintain the auth flow for each vendor ourselves.”

    Jordan HarrellSoftware Engineer, WorkweekCase study →

  • NaqIntune live in 5 days

    Truto added Microsoft Intune for Naq, a compliance platform, in 5 days.

    “we currently have MS Intune live for our customers”

    Martin DoneganNaqCase study →

  • KomplaiOne API for ERPNext and QuickBooks

    Komplai’s engineers work on their integration through Truto’s MCP server.

    “The MCP is super useful! Makes it so easy to work with the integration.”

    Anirudh VarmaKomplaiCase study →

FAQs

Common questions, straight answers.

What is Truto, in plain words?

Your customers use apps such as Salesforce, Slack and QuickBooks. An integration lets your product work with one of those apps. Truto is the service that connects each customer’s account to your product, and does the work to keep that connection working.

AI can build integrations. Why do we need Truto?

AI builds the integration. That job is done once. Then every customer has to connect their own account, and every connection has to keep working. Truto does that part. It runs the Connect screen and keeps each customer signed in. One fix reaches every customer, with no release on your side. See the full comparison.

Do we need developers to use Truto?

Someone has to add the Connect button to your product and use the data. A developer can do that, and so can an AI coding tool such as Claude Code or Cursor. After that, Truto runs the connections. On a paid plan, Truto’s engineers can also build an integration for you.

Does each app have to approve us before our customers can connect?

Not to start. Many apps make you register with them first, and some review you. Truto has done this already for many apps in the catalog, so accounts can connect on day one. For the other apps, and when you want your own name on the app’s sign-in screen, you register your own.

Will my customers see Truto’s brand?

Your customers see your name and your logo on the Connect screen. By default, the screen also says that it uses Truto. On the Enterprise plan, Truto removes that. The app’s own sign-in screen names the company that registered with the app. It says Truto until you register your own.

How fast can we start?

Request a free 30-day sandbox at truto.one/sandbox. You need a work email and no credit card. Most sandboxes are ready within one business day.

How much does Truto cost?

The plans and the prices are on the pricing page. The sandbox is free for 30 days, with no credit card.

Do you store my customers’ data?

When your product asks for a customer’s data, Truto fetches it from the app at that moment and passes it on. Truto does not keep a copy. Truto does store four things: each customer’s login, encrypted; a log of requests; the notices that it sends you when data changes, for up to 30 days; and the reply to a change that you sent with a retry key, for about one day. Features that store more data are off until you turn them on.

When a customer asks

“Do you support Jira?” Yes. And 1000+ more.

Your Connect screen is live on day one, and Truto’s integration infrastructure keeps every connection working.

Free for 30 days. No credit card. Most sandboxes are ready within one business day.