Add a configuration

Outcome

A named configuration your agents and tools can reference by name, with its credentials encrypted at rest.

Before you start

Developer Developer role or above. Viewers can see configurations but not create them.
The credentials themselves — an API key, a connection string, a service account file. qRaptor doesn’t fetch these for you.

Steps

Choose a category

From Configuration → Configurations, click Add Configuration. Five categories are offered: AI Models, Embeddings, Databases, Voice and Integrations.

The Add Configuration screen showing the five category choices

Choose a template

Each category lists the services it supports. A template already knows what that service needs, so you fill in a form rather than composing a connection by hand.

Each card shows how many fields the template has, how many are required, and how many are secrets — a quick way to see what you’re signing up for before you open it.

The template list for the Databases category

Name it

The name is how you’ll reference this configuration everywhere else, so it’s worth a moment. Lowercase letters, numbers, hyphens and underscores, starting with a letter.

The form shows the exact reference prefix underneath the field as you type — for a PostgreSQL template it reads {{config.postgresql.<name>}} — so you can see what you’re creating.

⚠️

The name can’t be changed later. Everything referencing a configuration does so by name, so renaming would break those references. Pick something that will still make sense in six months — orders_db rather than test2.

Fill in the fields

Required fields come first, optional ones below. Some fields appear only once you’ve answered another — choose an authentication method on a REST API template and only the fields that method needs are shown.

The configuration form showing required and optional field groups

Check what’s marked secret

Every text field has an Encrypted / Plain toggle beside it. Fields the template knows are sensitive — API keys, passwords — start as Encrypted. A summary at the bottom of the form lists everything that will be encrypted before you save.

See Secrets & encryption for what that means in practice.

Save

Click Create Configuration. You’ll land back on the list with the new configuration in place.

Notes on particular categories

Voice covers three kinds of service, and which you need depends on the agent:

Speech-to-text — Deepgram, OpenAI Whisper, Azure Speech
Text-to-speech — OpenAI, ElevenLabs, Deepgram Aura, Azure Speech
Realtime — OpenAI Realtime API, Google Gemini Live, for voice agents that stream both directions

Integrations is the broadest category — CRM, ticketing, messaging, storage, source control, email and generic HTTP. If a service isn’t listed by name, REST API and Generic Webhook cover most of the rest, and Custom Integration is there for anything else.

ℹ️

Some configurations are created for you elsewhere and simply appear in this list. Connecting an MCP server or completing a Google OAuth flow writes its credentials into the project as a configuration — you don’t create those here, but you can see them.

Common issues

“A configuration with this name already exists” — names are unique per template within a project. Either pick another name, or edit the existing one.
The name field won’t accept what you typed — it must start with a letter and contain only lowercase letters, numbers, hyphens and underscores. No spaces or capitals.
A field you expected isn’t there — several templates show fields conditionally. Set the field it depends on (usually an authentication method or SSL mode) and it will appear.
You can’t see the Add Configuration button — that action needs Developer or above.

Secrets & encryption — what happens to the credentials you just entered.