Skip to main content
Environment variables let you store sensitive values (API keys, tokens, configuration settings) that your API tools and integrations can reference at runtime. Values are encrypted and never exposed in the dashboard or to customers.

​
Built-in variables

Lookfor provides some built-in environment variables that are automatically available:
VariableDescription
SHOP_DOMAINYour Shopify .myshopify.com domain.
SHOP_URLYour store’s public URL.
Built-in variables cannot be edited or deleted.

​
Custom variables

​
Creating a variable

  1. Go to Settings > Environment Variables.
  2. Click Add Variable.
  3. Set the Key (e.g., SHIPPING_API_KEY) and Value.
  4. Save.

​
Using variables in API tools

Reference environment variables in your API tool configurations using double curly braces:
FieldExample
HeaderAuthorization: Bearer {{SHIPPING_API_KEY}}
URLhttps://api.provider.com/v1/endpoint?key={{API_KEY}}
Body{"token": "{{SERVICE_TOKEN}}"}
At runtime, {{VARIABLE_NAME}} is replaced with the stored value. The actual value is never visible to the agent or the customer.

​
Using variables in MCP servers

Environment variables can also be used in MCP server configurations for authentication headers and connection strings.

​
Best practices

  • Never hardcode secrets in API tool configurations. Always use environment variables.
  • Use descriptive names: SHIPPING_PROVIDER_API_KEY is better than KEY1.
  • Rotate regularly: When you update an API key with your provider, update the environment variable in Lookfor too.
  • Keep it organized: Use a consistent naming convention (e.g., SERVICE_NAME_KEY_TYPE) so your team can easily find and manage variables.