Bring ConfigCat into
the flow of work.
A little less busywork with ConfigCat.
Feature-flags1 capabilities+
- Create feature flag
Creates a new feature flag in ConfigCat.
Configs3 capabilities+
- Create config
Creates a new config in ConfigCat.
- Get values
This endpoint returns all Feature Flag and Setting values of a Config identified by the configId parameter in a specified Environment identified by the environmentId parameter.
- Post values
This endpoint batch updates the Feature Flags and Settings of a Config identified by the configId parameter in a specified Environment identified by the environmentId parameter.
Environments1 capabilities+
- Create environment
Creates a new environment in ConfigCat.
Products1 capabilities+
- Create product
Creates a new product in ConfigCat.
Members1 capabilities+
- List members
Retrieves a list of all members in ConfigCat.
Settings3 capabilities+
- Get setting value
This endpoint returns the value of a Feature Flag or Setting in a specified Environment identified by the `environmentId` parameter.
- Get multiple setting values
This endpoint retrieves the values of multiple Feature Flags or Settings in a specified Environment.
- Get value
This endpoint returns the value of a Feature Flag or Setting in a specified Environment identified by the SDK key.
Frequently asked
questions.
What could an Ambacti integration do with ConfigCat?
The documented operations include Feature-flags: Create feature flag; Configs: Create config; Configs: Get values; Configs: Post values.
Could I keep a workflow read-only?
For a read-only workflow, limit account permissions to reading data and exclude actions that create, update, or delete records.
Will every action run automatically?
Choose which steps could run on their own and which should pause for review. Changes should follow the permissions and approval rules you set.
Do I need to review actions in ConfigCat?
Decide which work could run on its own and which steps need your review.