Using Environment Variables
Written by Medha Anand
Updated on April 19th, 2023
- Getting Started
- Bot Building
- Smart Agent Chat
- Conversation Design
-
Developer Guides
Code Step Integration Static Step Integration Shopify Integration SETU Integration Exotel Integration CIBIL integration Freshdesk KMS Integration PayU Integration Zendesk Guide Integration Twilio Integration Razorpay Integration LeadSquared Integration USU(Unymira) Integration Helo(VivaConnect) Integration Salesforce KMS Integration Stripe Integration PayPal Integration CleverTap Integration Fynd Integration HubSpot Integration Magento Integration WooCommerce Integration Microsoft Dynamics 365 Integration
- Deployment
- External Agent Tool Setup
- Analytics & Reporting
- Notifications
- Commerce Plus
- Troubleshooting Guides
- Release Notes
You can set environment variables for the code executor to store values like database username and passwords that you don't want to expose inside the code.
The environment variables are stored at a bot level. This means that variables stored in one step are automatically available to all steps inside the bot.
You can set these variables by opening the code editor, clicking on the More button in the top right corner
and selecting the Variables option.
In the variables the menu that opens, you can set the variable name and values for the variable on the staging and production environments. For example, you can create a variable called MONGO_URI and set its staging value as mongodb://mongodb0.example.com:27017/admin and its production value as mongodb://mongodb1.example.com:27017/admin.
These environment variables are then available within the request parameters for the integration functions. You can read about the request parameter structure here
There is a character limit of 50 to store the environment variables. If this limit exceeds, the IVA will break.
