Integrations
Connected serverless providers.
Where: Code → Integrations · /projects/<project>/code/integrations
The Code Integrations list shows the serverless providers connected to this project — the engines your custom functions run on. Connect one before creating custom functions.
Screenshot TODO — capture comes from testing-plan area 01-integrations.
What you can do here
The table has the columns Integration Name, Provider, Enabled, and Default. The default badge is per environment ("Default for {ENV}"); when more than one integration is active but none is the default, a warning appears: "No Default Set For Active Integrations". Click a name to open the integration's edit screen, where you can also Set as default, Test (the test runs automatically end to end — the backend invokes a test function, no manual confirmation), Enable/Disable, and Delete.
Add New Integration opens the provider picker (…/code/integrations/pick) with three providers — see Providers for each configuration form:
AWS Lambda — connect your AWS account with a Cross-Account Role (recommended) or an IAM user; on the Norbix AWS deployment you can also run on the built-in engine.
Azure Functions — function app name plus a connection string or function key.
Google Cloud Functions — a service account JSON key, GCP project, and region.
Use it from code
API reference
Endpoints: Get Code Integrations, Save Code Integration, Set Code Integration As Default, Test Code Integration.
Last updated