Integration
Connect ConfigCat to Fullstory
When Feature Flag & Setting value changed fires in ConfigCat, your agent runs Add user in Fullstory. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want ConfigCat and Fullstory to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What ConfigCat can start in Fullstory
When Feature Flag & Setting value changed in ConfigCat
then Add user in Fullstory
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with ConfigCat and Fullstory
Triggers and actions 1 trigger · 35 actions
- Feature Flag & Setting value changed
Triggers when a ConfigCat Feature Flag or Setting value is changed.
- Add Config
Create a new config within a product.
- Add Flag
Create a new feature flag or setting within a config.
- Add Segment
Create a new segment within a product.
- Add Tag
Create a new tag within a product.
- Delete Config
Delete a config.
- Delete Flag
Delete a feature flag or setting.
- Delete Segment
Delete a segment.
- Delete Tag
Delete a tag.
- Get Config
Get a single config by id.
- Get Environment
Get a single environment by id.
- Get Flag
Get a single feature flag or setting by id.
- Get Flag value
Get the current served value of a feature flag or setting in an environment.
- Get Product
Get a single product by id.
- Get Segment
Get a single segment by id.
- Get Tag
Get a single tag by id.
- List Configs
List all configs (SDK config bundles) within a product.
- List Environments
List all environments within a product.
- List Flags
List all feature flags and settings within a config.
- List Organizations
List all organizations the caller has access to.
- List Products
List all products the caller has access to.
- List Segments
List all segments within a product.
- List Tags
List all tags within a product.
- Update Config
Update a config's name/description/order.
- Update Environment
Update an environment's name/color/description.
- Update Flag
Update a feature flag or setting's metadata (name, hint, tags).
- Update Flag value
Update (turn on/off, change served value or targeting) a feature flag or setting's value in an environment.
- Update Segment
Update a segment's name/rules.
- Update Tag
Update a tag's name/color.
- Add annotation
Creates an annotation in Fullstory to mark an event such as a release on your session and metric timelines.
- Add user
Creates a Fullstory user, or updates the existing user with the same User ID.
- Delete user
Deletes a single Fullstory user by their Fullstory-generated user id.
- Find users
Finds Fullstory users matching a uid, email, display name or identified status.
- Get user
Returns the details of a single Fullstory user, including their custom user properties.
- Set User Properties
Updates an existing Fullstory user's custom properties, display name, email or application user id.
- Track Event
Creates a custom server event in Fullstory, optionally attached to an existing session or user.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from ConfigCat
ConfigCat to FlokzuFlokzu is a powerful cloud BPM suite, made agile & friendly!
ConfigCat to Geocode.xyzGeocode.xyz is a worldwide geocoding service.
ConfigCat to New Relic InsightsNew Relic Insights is a real-time analytics platform that collects metrics directly from your live...
ConfigCat to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
ConfigCat to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
ConfigCat to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
More into Fullstory
Google Sheets to FullstoryGoogle Sheets
Gmail to FullstoryGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to FullstoryGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
ConfigCat and Fullstory, answered
What can start an automation from ConfigCat?
Any of ConfigCat's 1 trigger in the catalog, including Feature Flag & Setting value changed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Fullstory when something happens in ConfigCat?
Any of Fullstory's 7 actions, including Add annotation, Add user, Find users and Get user. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Fullstory to ConfigCat?
Fullstory has no triggers in the catalog today, so automations start in ConfigCat. If you need the other direction, ask: your agent reads Fullstory's API documentation and adds it.
Do I have to build a connector for ConfigCat or Fullstory?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use ConfigCat and Fullstory without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.