# Custom integrations: connect any API-key or public REST API

> When an app isn't in the catalog, an agent turns its API docs into a private integration that works in chat, workflows, and apps.

Jun 3, 2026. Topics: Integrations, Agents. https://www.generalinput.com/changelog/2026-06-03-custom-integrations

Until now, an API outside our catalog meant filing a request and waiting. You can now add it yourself: in Integrations, choose New, then Custom Integration, and describe the API or drop in its docs. An agent drafts a private integration for your workspace, and once published it works everywhere a built-in integration does. Agents call it in chat, and workflows and apps declare it as a connection.

### How it works

- **Same structure as ours.** A custom integration has a description, an authentication definition, common docs (base URL, auth header, pagination, rate limits, errors), a setup guide, and one documented operation per endpoint, so agents call it as reliably as a catalog integration.
- **Reads any format.** Drop in an OpenAPI or Swagger spec, a Postman collection, a PDF, or plain docs, or just give a name or link and the agent researches the public reference.
- **API keys or public APIs.** Define one or more key fields and mark which are secret; secret fields are encrypted, scrubbed from output, and injected only at run time.
- **Publish when complete.** Publishing requires authentication, docs, a setup guide, and at least one operation; the agent tells you what's missing.
- **Workspace-owned.** Members connect their own credentials by following its setup guide.

Services that only support OAuth can still be requested through Integration Request.