Integrations
Integration terms explained (Part 2)
Welcome to your integration glossary. This page covers every essential term you’ll encounter when using or building integrations in Base44, no coding knowledge required. Whether you’re adding a catalog integration or creating your own from scratch, this guide will give you the clarity and confidence to move fast.
API (Application Programming Interface)
What it is:A structured way for apps and services to communicate. Why it matters:
All integrations in Base44 work by sending API requests behind the scenes.
Think of it like a waiter at a restaurant: your app places an order → the API takes it to the service → the service responds with the result.
API Key
What it is:A unique string (like a password) that authenticates your app with another service. Where to find it:
Log in to the external service → Developer/API settings → Click “Generate Key”
Store securely in Dashboard → Secrets
Authentication
What it is:The process of verifying your app’s identity with another service (usually using an API key or OAuth).
Backend Functions (BF)
What it is:Server-side logic that securely powers most integrations, letting your app call external APIs, handle data, or run workflows.
Think of it like the kitchen in a restaurant: it prepares the actual result when your user clicks a button or submits a form.
- You must have a Builder Plan to use or create integrations
- Ready-Made integrations automatically enable BF
- Instant integrations require you to manually enable BF in App Settings
Check out our guide to backend functions here.
Environment variables (also known as “required setup variables”)
What it is:Named values (like API keys or workspace IDs) that your integration uses to connect and run properly. Where it’s used:
Stored as Secrets in your Dashboard, or prefilled in a catalog integration. Why it matters:
They help Base44 connect your app to external tools and services behind the scenes.
Example Prompt
What it is:A natural-language request you give to the AI to trigger an integration. Example:
“Send a confirmation email when someone signs up.”
Integration Prompt (aka catalog integration instructions)
What it is:A full block of instructions that tell the Base44 AI how your integration works.
Think of it like a recipe that the AI follows to build the integration properly.
Only in Ready-Made Integrations from the catalog. What it includes:
- Overview
- Required environment variables
- Backend function code
- (Optional) frontend logic
- Example usage
- Documentation links
This is what Base44 injects when you build an app that uses a catalog integration.
Integration Credits
What it is:Credits are used whenever your app performs an integration action — like sending an email, making an API call, or transcribing a file. How it works:
- 1 API request = 1 credit (on average)
- AI model calls may use more
You need to be logged in to your Base44 account to access the billing dashboard
Integration Types
Base44 supports two ways to connect your app to external services:| Type | When it’s added | Setup | Best for |
|---|---|---|---|
| Ready-made | Before you type your first prompt / right before the app is created | Pick from the Integrations Catalog | Apps that need the integration built-in |
| Instant | Anytime | Just describe it in the AI chat | Adding services on the fly or mid-build |
You will need to be logged in to your Base44 account to access the integrations catalog.
A few more details regarding the integrations:
Ready-made integrations (through the catalog)
Some integrations in Base44 are what we call “ready-made”. They’re packaged and ready for use but only if you install them before you start building your app.Set it up before your first prompt:**Want to add an integration later? **You can still add a ready-made integration after your app is in progress, but the flow’s a bit more manual. Here’s what to expect:
- Go to the Integrations Catalog.
- Select the integration that you want to set up
- Click “Use this integration” on the one you want.
- Add your API keys/secrets.
- Then start building your app with your first prompt.
Why does the order matter?
The integration actually shapes how your app is structured from the very beginning—so it needs to be in place before you type your first instruction.
The integration actually shapes how your app is structured from the very beginning—so it needs to be in place before you type your first instruction.
- You’ll need to install it through the AI chat.
- The setup won’t be as seamless, and the app won’t automatically adapt to the integration.
- That said, the chat can walk you through the steps if you need help. The chat builder can give you step-by-step instructions, even if it’s not as smooth as doing it upfront.
Instant integrations (on-the-fly)
Instant integrations are much more flexible. You can install them anytime, before or after building your app. There are no catalog restrictions to this.
How to use them:
- Just ask the AI chat to add the integration.
- It’ll guide you through the setup process step-by-step.
Example: Type out “Set up an email integration using Resend for new user signups.” in the AI chat.
OAuth
What it is:A secure way to connect accounts using a login (e.g., “Sign in with Google”). Why it matters:
Used in integrations where user-specific access is needed.
Secrets
What it is:A secure space in your Base44 Dashboard where API keys and tokens are stored. Where to find it:
Go to Dashboard → Secrets
Test-mode (also called Sandbox)
What is is:A safe environment to test your integration without triggering real charges, messages, or actions. Why it matters:
Great for validating your flows using test API keys before going live.
Example: Stripe has test cards, and OpenAI has a usage cap in free mode.
Webhook
What it is:A live listener that receives data from another service when an event occurs.
Example: Stripe sends a webhook when a payment is successful.