Overview
This node integrates with ConfigCat, a feature flag management service. It allows users to evaluate the value of a specified feature flag dynamically during workflow execution. This is useful for enabling or disabling features in applications without redeploying code, performing gradual rollouts, or targeting specific user segments.
Common scenarios include:
- Conditionally executing parts of a workflow based on feature flags.
- Testing new features with selected users by passing user attributes.
- Managing feature toggles centrally and reflecting their state in automation workflows.
For example, you can check if a "newCheckoutFlow" feature flag is enabled for a particular user and route the workflow accordingly.
Properties
| Name | Meaning |
|---|---|
| Feature Flag | The name of the feature flag to evaluate (e.g., "myFeatureName"). |
| SDK Key | The ConfigCat SDK key used to authenticate API requests (e.g., "configcat-sdk-3/..."). |
| Default | The default value to return if the feature flag cannot be evaluated. Must match the flag's type. |
| User ID | Unique identifier for the user to target in the feature flag evaluation. |
| User Email | Email address of the user, used for targeting rules. |
| User Country | Country of the user, used for targeting rules. |
There are also informational notices about default value requirements and targeting rules URL.
Output
The node outputs an array with one item per input item. Each output item contains a json object with a single property named after the feature flag. The property's value is the evaluated feature flag value (boolean, number, string, array, etc.) as returned by ConfigCat.
Example output JSON structure:
{
"myFeatureName": true
}
No binary data is produced.
Dependencies
- Requires the
configcat-nodenpm package for interacting with ConfigCat. - Needs a valid ConfigCat SDK key provided via the "SDK Key" property.
- Optionally uses user attributes (ID, email, country) for targeted flag evaluation.
No additional environment variables or n8n credential types are required beyond these inputs.
Troubleshooting
- Invalid SDK Key: If the SDK key is incorrect or missing, the node will fail to retrieve flag values. Ensure the SDK key is correct and active.
- Malformed Default Value: The default value must be valid JSON matching the expected type of the feature flag; otherwise, parsing errors may occur.
- User Attributes Missing: If targeting rules depend on user attributes but none are provided, the flag evaluation may not behave as expected.
- Network Issues: Connectivity problems to ConfigCat servers can cause timeouts or failures.
To resolve errors, verify all inputs, especially the SDK key and default value format, and ensure network access to ConfigCat.