MaleusMaleus

Connect a third-party integration

Add credentials for the external services your project depends on. Each integration holds its own secrets per environment.

In the appIntegrations
On this page

Integrations hold the credentials your project needs to talk to external services: a payment provider, an LLM API, a CRM, an issue tracker. Each integration belongs to one project and stores its secrets per environment, so development, staging and production each keep their own keys.

Where integrations live

Open the project, then Integrations. The list is one card per connected service, with the count above it and Add in the top right.

One card per connected service. Click a card to manage its secrets.

Under the list, Add another integration puts the popular services one click away, next to Browse all and a shortcut to describe one with AI. Use those when you already know the next service to wire up.

Three ways to add one

Click Add, or Add integration from the empty state. The screen opens on one question, How would you like to add an integration?, with three answers.

PathWhen to use it
Browse catalogThe service is one of the 80-odd already described. Fastest path.
Describe with AIThe service is not in the catalog. Describe what you need in plain English and the agent writes the definition.
Create from scratchYou know exactly what you want: a name, a short description, the secrets listed by hand.
  • Browse catalog: search the grid, pick a tile. Each tile says how many secrets it needs.
  • Describe with AI: describe what you need, refine the proposal, start over if the result is not right.
  • Create from scratch: fill in a name, an optional description, the documentation, and the secret key definitions.

All three land on the same last step.

Configure secrets

Each environment holds its own keys, and is switched on separately.

Under Secrets by environment, the three environments are colour-coded: blue for Development, amber for Staging, emerald for Production. Each has its own toggle, and one that is switched off says so instead of showing fields. You can enable production without enabling staging.

Each secret carries its own description and a How to obtain disclosure telling you where to get the value. Add custom secret appends a key the catalog did not list, and Additional documentation takes any notes the agent should read, in Markdown.

Create Integration saves the lot.

Secret fields can be shown or hidden with the eye icon. Hidden by default.

Manage an existing integration

Back on the list, click any card to open it. From there:

  • Per-environment activation toggles.
  • A separate secrets form per environment, with its own Save.
  • A Documentation view, editable if you have permission.
  • A delete action, with confirmation.

A configured-but-inactive integration is a useful pattern for incident response. Keep the secrets ready in production and leave activation off until you are ready to switch traffic.