Overview
This node integrates with GrowthBook, a feature flagging and experimentation platform. It evaluates a selected feature flag based on user or context attributes and outputs the feature's value and status. This is useful for dynamically controlling feature rollouts, A/B testing, and personalized user experiences in workflows. For example, it can enable or disable features for specific user segments or return feature values for conditional logic in automation.
Use Case Examples
- Evaluate a feature flag to determine if a new UI should be shown to a user based on their country attribute.
- Fetch a feature value to customize content or functionality dynamically in a workflow.
- Reload the feature list from GrowthBook to ensure the latest flags are used in evaluations.
Properties
| Name | Meaning |
|---|---|
| Feature | The feature flag to evaluate, selected from the list of available features loaded from GrowthBook. |
| Reload Features | Button to reload the feature list from GrowthBook, refreshing the cache of available features. |
| Attributes | User or context attributes used for targeting and evaluating the feature flag. These are key-value pairs such as user ID, country, or plan. |
Output
JSON
value- The evaluated value of the feature flag, which can be boolean or any other type depending on the feature.isOn- Boolean indicating if the feature flag is considered 'on' or active.featureKey- The key/name of the feature flag evaluated.attributes- The user/context attributes used in the evaluation.detectedType- The detected type of the feature value, e.g., 'boolean' or 'value'.error- Error message if the feature was not found or evaluation failed (present only in error cases).
Dependencies
- Requires an API key credential for GrowthBook with client key and API host URL.
Troubleshooting
- If the feature key is not found, the node outputs an error message indicating the feature was not found. Verify the feature key spelling and that the feature exists in GrowthBook.
- Connection errors such as ENOTFOUND or ECONNREFUSED indicate issues with the API host URL or network connectivity. Check the API host configuration and network access.
- HTTP errors like 401 or 403 indicate permission issues with the client key. Ensure the API key has proper access rights.
- Timeouts or empty responses may indicate server issues or misconfiguration. Adjust request timeout settings or verify the GrowthBook service status.
Links
- GrowthBook Documentation - Official documentation for GrowthBook feature flags and experimentation platform.