Skip to content

Build

Name the app. Your agent builds the integration.

Install the Truto skills once. Your agent reads the app’s API docs, builds the integration, checks it and puts it live on Truto. No deploy.

Agent skills

Install once. Then ask in plain words.

Works in Claude Code, Cursor, Codex, Windsurf and any agent that reads skills.

1Install the skills once

/plugin marketplace add trutohq/truto-skills/plugin install truto@truto-skills

Adds the skills as a Claude Code plugin.

2Ask for the integration in plain words

Say what you need, as you would to a teammate. Your agent does the rest.

your coding agent
>

Add Expensify to our app. Map its expense reports to our accounting model, and put a Connect button in Settings.

✓

Built the Expensify integration from its API docstruto integrations build expensify-docs.md

✓

Checked it: 0 problemstruto integrations lint

✓

Put it live on Trutotruto integrations apply

✓

Mapped expense reports to your accounting modeltruto unified-mappings apply

✓

Added a Connect button to Settingssrc/settings/integrations.tsx

✓

Done. Your customers can connect Expensify from Settings.

All eight skills on GitHub →

What your agent runs

From the app’s docs to your customers, in five steps.

Your agent runs them for you. Each step checks the one before it.

  1. 1

    Read the docs

    Reads the app’s API docs and writes one integration file.

    truto integrations build✓ file written
  2. 2

    Check the file

    Finds mistakes before anything goes live. No AI, no changes.

    truto integrations lint✓ 0 problems
  3. 3

    Check it against the docs

    Compares the file with the app’s OpenAPI spec, when it has one.

    truto integrations verify✓ verified
  4. 4

    Publish it to your team

    Live on Truto when it finishes. No deploy.

    truto integrations apply✓ on your team
  5. 5

    Turn it on for customers

    Your customers can now connect their accounts.

    truto environment-integrations create✓ live

Need one API for a whole category, such as CRM? truto unified-mappings build maps the integration to a unified model. Every command is on the CLI page, and the full reference is in the build docs.

17integrations, up from 2

Without Truto4 months
With Trutoa 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 Engineering
Read the Sprinto case study →

After apply

Built by your agent. Run by Truto.

Your agent’s work ends at apply. Everything under the line runs on Truto, for every customer who connects.

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

Why run it on Truto →    What Truto runs, step by step →

Ask your agent for your first integration.

Get a sandbox, install the skills, and name the app your customers ask for.