Using Environment Variables
If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.
- Getting Started
- Bot Building
- Conversation Design
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
- Agent Setup
- Analytics & Reporting
- Proactive Messaging
- 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 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
These environment variables are then available within the request parameters for the integration functions. You can read about the request parameter structure here