Where integrations live
Foundry uses two settings pages:- Settings → Integrations. Create and manage custom API integrations. They appear in the Custom category alongside Ravenna’s built-in integrations.
- Settings → OAuth Providers. Register OAuth providers that end users connect their own accounts to.
Custom API integrations
Use these for any tool with an API that uses a static credential (API key, bearer token, basic auth) or no auth at all.Create one
Basics
Fill in the API name, an optional description and logo, a category, and a link to the tool’s documentation.
The best documentation link is one that goes straight to the API reference, not the marketing homepage. If the tool has an OpenAPI or Swagger link, use that.
Research
Foundry reads the documentation to learn how the tool works, including pagination, auth methods, rate limits, error handling, and versioning. You’ll see live progress for each of those steps. This usually takes under a minute.
Auth
Pick the sign-in type and fill in the credentials. The wizard supports API key, Bearer token, Basic auth, and No auth. You can also add default headers that should be sent with every request from this integration. These are useful for things like a tenant or account header.
Edit or delete later
From Settings → Integrations, click any custom integration to open its details. You can edit the basics and authentication, re-run docs research, or delete the integration. You’ll need to remove or unpublish any functions using it before you can delete it.Credentials are stored in Ravenna’s secure vault. They’re only used when a function runs and they’re never shown to the AI that writes your function code.
For a step-by-step walkthrough of the custom integration wizard, see Set up a custom API integration in the Foundry guide.
OAuth providers
Use these for tools where end users sign in with their own account, for example Google, Microsoft, or Salesforce. Each user who runs a function connects their account once, and the function executes as that account.Register a provider
General
Give the provider a name, a slug (used internally), an optional description and logo, and the base URL and docs URL for the API.
OAuth
Enter the provider’s authorization URL, token URL, scopes, client ID, and client secret. You can also pass extra parameters to the authorization or token-exchange requests for providers with non-standard flows.
Connect an account
Once a provider is registered, each user connects their own account by going to Settings → Integrations, finding the provider in the Custom category, and clicking through the standard OAuth sign-in flow. Tokens refresh automatically.Need help registering a provider? The Foundry guide has end-to-end walkthroughs for Google Cloud, GitHub, and DocuSign, plus a shared overview you can adapt to any provider.
Managing integrations
- Edit to update sign-in details, the base URL, or the docs URL.
- Re-research to make Foundry re-read the documentation if the API has changed.
- Delete to remove the integration. Remove or unpublish any functions using it first.
Ready to build? Learn how to create a function.