Posthog Create Feature Flag

• keystring

  Required
  Unique identifier key for the feature flag (e.g., 'dark-mode', 'new-checkout-flow'). Used in your code to check if the flag is enabled. Must be unique within the project.
• namestring
  Human-readable name for the feature flag displayed in the PostHog UI (e.g., 'Test Feature Flag from Composio'). If not provided, defaults to the key value.
• tagsarray
  List of tags to organize and categorize the feature flag (e.g., ['frontend', 'experiment']). Helps with filtering in PostHog UI.
• activeboolean
  Whether the feature flag is active/enabled. Set to false to disable without deleting. Defaults to true.
• deletedboolean
  Whether the feature flag is soft-deleted. Soft-deleted flags are hidden but can be restored. Generally not needed when creating a new flag.
• filtersobject
  Filtering and rollout configuration. Structure: {'groups': [{'properties': [], 'rollout_percentage': 50}]}. Use 'rollout_percentage' (0-100) for gradual rollout. Use 'properties' to target specific users. If omitted, flag is enabled for all users.
• project_idstring

  Required
  Project ID where the feature flag will be created. Find this via the List All Projects action or from your PostHog project settings.
• is_simple_flagboolean
  If true, creates a simple boolean flag (on/off). If false, enables advanced targeting and multivariate options. Defaults to true.
• ensure_experience_continuityboolean
  If true, ensures users see consistent experience even if flag settings change. Useful for A/B tests where users shouldn't switch between variants.

• data

  Required
  Data from the action execution
• errorstring
  Error if any occurred during the execution of the action
• successfulboolean

  Required
  Whether or not the action execution was successful or not

No verified related use cases are linked yet.

No published Skills explicitly reference this Action yet.