Add credentials
By the end of this page you will have saved a connection’s credentials for preview, and know how to add the production ones.
Prerequisites
- Developer Developer role or above. Other roles see the form read-only.
- The keys from the service itself. For Razorpay, see Get your Razorpay keys.
Steps
Open the connection
Open Connections (see Open Connections) and click the service’s card.
The page header shows the service’s name, its Verified badge and its version. Beneath them is the mention to use in a prompt, for example Mention it in a prompt as @razorpay.
Check what your app can do (optional)
Expand What your app can do with Razorpay to see the operations this connection gives your app. For Razorpay these are:
| Operation | What it does |
|---|---|
| Create order | Creates an order to hand to Razorpay’s checkout. The amount is in paise. |
| Verify payment signature | Checks the signature checkout returns to the browser after a payment. |
| Fetch payment | Looks up a payment’s current status. |
| Fetch order payments | Lists every payment attempt against one order. |
| Refund | Refunds a captured payment, in full or in part. |
You don’t call these yourself. Describe what you want in your prompt, such as “let shelter admins refund a donation”, and the generated code uses them.
Fill in the Preview side
The Credentials section has two columns: Preview on the left and Production on the right. Enter your test keys on the Preview side.
Fields marked with a red * are required. Each field also carries a label saying where its value ends up:
| Label | Meaning |
|---|---|
| Reaches the browser | Sent to the browser while the app runs, so anyone using the app can read it. Correct for a publishable key, such as Razorpay’s Key ID. |
| Server only | Stays on the server. Never sent to the browser and never written into the app’s build. |
| Encrypted | A secret. It’s encrypted when stored and never shown again after you save it. |
Under each field, Reaches your app as shows the environment variable name your app receives, such as RAZORPAY_KEY_ID.
Never paste a secret into a field marked Reaches the browser. Anyone using your app can read that value.
Save the Preview side
Click Save preview. The button is only enabled when that side has changes to save.
Once it saves, a green panel confirms it: Saved. Running previews will pick this up automatically. Your secrets now show as masked dots.
If a required field is empty, nothing is saved. A message names the missing field instead, for example Preview is missing Key Secret.
Add the Production side when you’re ready
The Production side saves on its own, so it can wait until you’re ready to publish. When you are, enter your live keys there and click Save production.
Copy from preview fills in the non-secret values from the Preview side, which saves retyping them. It never copies secrets: type those in yourself.
Changing a saved secret
A saved secret shows as masked dots. To replace it, click into the field and type the new value. Clicking in selects the stored value, so whatever you type replaces it.
Emptying a saved secret does not remove it. If you clear the field and save, the old value is kept, and a message says the field was left unchanged. To remove credentials completely, delete them. See Update or remove credentials.
Common issues
- Save preview or Save production is greyed out. That side has no unsaved changes. Edit a field first.
- ”… left unchanged” after saving. You emptied a saved secret. Emptying a secret never clears it; type a new value to replace it, or delete the credentials.
- “Another configuration exists for this integration.” This connection’s type also has credentials saved under another name, usually created from the Configuration page. Apps only read the credentials on this page; anything else is ignored. Move the values you need into this form, then delete the other entry using the bin icon in the warning.
- “This configuration applies to all environments.” One set of values is currently serving both preview and production, so a live key would also be used by your previews. Save each side to split it into separate preview and production values.