Integrations

Payments, email delivery and AI models are services you rent rather than build. Each needs a secret key that must never reach the browser, plus backend work around it: a checkout endpoint, a receiver that verifies Stripe’s webhook signature, a record of sent emails, a quota so a loop cannot drain your OpenAI credit. Integrations stores the key encrypted for the project and gives your agent a known starting point for that work.

1. 1

   Paste your key

   Pick a provider and paste the API key from its dashboard. It is stored encrypted for this project, and Backenly asks the provider whether the key works where the provider allows that.

2. 2

   Describe what you want

   Pick a starting point, such as subscription billing or a welcome email, and Backenly turns it into a request for your coding agent.

3. 3

   Your agent builds it

   Over MCP it creates the tables, functions and webhook receivers the feature needs, through the same governed path as every other change.

4. 4

   Functions use the key on the server

   Your functions call the provider through ctx.integrations, which uses the stored key, so the key never ships to the browser.

Once your coding agent is connected, ask it:

Add subscription billing with Stripe: monthly and annual plans, a checkout endpoint, and a payments table updated from Stripe’s webhook.

Send a welcome email through Resend when a user signs up.

• You use your own accounts with these providers and pay them directly.
• Stripe also needs its webhook signing secret, so Backenly can check that payment events really came from Stripe.
• Functions that use a key stop working if the key is removed.
• Integrations is for services your backend calls. To tell your own services that something changed, use Webhooks.