Integration
Connect ConfigCat and Request Tracker (RT)
When Feature Flag & Setting value changed fires in ConfigCat, your agent runs Create Ticket in Request Tracker (RT), or Ticket Created in Request Tracker (RT) to Add Config in ConfigCat. 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 Request Tracker (RT) to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 and Request Tracker (RT) can do together
From ConfigCat to Request Tracker (RT)
When Feature Flag & Setting value changed in ConfigCat
then Create Ticket in Request Tracker (RT)
When Feature Flag & Setting value changed in ConfigCat
then Update ticket in Request Tracker (RT)
From Request Tracker (RT) to ConfigCat
When Ticket Created in Request Tracker (RT)
then Add Config in ConfigCat
When Ticket Status Changed in Request Tracker (RT)
then Add Flag in ConfigCat
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 Request Tracker (RT)
Triggers and actions 4 triggers · 47 actions
Trigger
Feature Flag & Setting value changedTriggers when a ConfigCat Feature Flag or Setting value is changed.
Action
Add ConfigCreate a new config within a product.
Action
Add FlagCreate a new feature flag or setting within a config.
Action
Add SegmentCreate a new segment within a product.
Action
Add TagCreate a new tag within a product.
Action
Delete ConfigDelete a config.
Action
Delete FlagDelete a feature flag or setting.
Action
Delete SegmentDelete a segment.
Action
Delete TagDelete a tag.
Action
Get ConfigGet a single config by id.
Action
Get EnvironmentGet a single environment by id.
Action
Get FlagGet a single feature flag or setting by id.
Action
Get Flag valueGet the current served value of a feature flag or setting in an environment.
Action
Get ProductGet a single product by id.
Action
Get SegmentGet a single segment by id.
Action
Get TagGet a single tag by id.
Action
List ConfigsList all configs (SDK config bundles) within a product.
Action
List EnvironmentsList all environments within a product.
Action
List FlagsList all feature flags and settings within a config.
Action
List OrganizationsList all organizations the caller has access to.
Action
List ProductsList all products the caller has access to.
Action
List SegmentsList all segments within a product.
Action
List TagsList all tags within a product.
Action
Update ConfigUpdate a config's name/description/order.
Action
Update EnvironmentUpdate an environment's name/color/description.
Action
Update FlagUpdate a feature flag or setting's metadata (name, hint, tags).
Action
Update Flag valueUpdate (turn on/off, change served value or targeting) a feature flag or setting's value in an environment.
Action
Update SegmentUpdate a segment's name/rules.
Action
Update TagUpdate a tag's name/color.
Trigger
Ticket CorrespondenceTriggers when a ticket is replied to (that is, corresponded with).
Trigger
Ticket CreatedTriggers when a new Request Tracker ticket is created.
Trigger
Ticket Status ChangedTriggers when a Request Tracker ticket changes status. Can watch for any status change or only for changes to a specific status.
Action
Add assetCreate an asset.
Action
Add userCreate a user.
Action
Comment on a TicketAdd an internal comment to a ticket and send to any internal watchers.
Action
Create TicketCreate a new ticket in Request Tracker.
Action
Find AttachmentLocate an attachment by ID.
Action
Find TicketLocate a ticket by ID.
Action
Find TicketsIssue a query to find matching tickets.
Action
Find TransactionFind a transaction by ID
Action
Get assetRetrieves one asset by ID: name, description, status, catalog, owner, held by, contact, custom fields.
Action
Get queueGet a queue by id or name.
Action
Get userGet a user by id or name.
Action
List queuesList all queues visible to user.
Action
List ticket historyList transactions of a ticket.
Action
Reply to a TicketReply to the requestor and any internal or external watchers of a ticket.
Action
Update ticketGeneral ticket update (Owner, Priority, Queue, custom fields).
Action
Update Ticket Due DateUpdate the due date of a ticket.
Action
Update Ticket StatusUpdate the status of a ticket.
Action
Update Ticket SubjectUpdate the subject of a ticket.
Action
Update userUpdate a 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 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...
ConfigCat to Google SheetsGoogle Sheets
ConfigCat to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into Request Tracker (RT)
HubSpot to Request Tracker (RT)HubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to Request Tracker (RT)Google Sheets
Gmail to Request Tracker (RT)Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Request Tracker (RT)Google Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to Request Tracker (RT)Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to Request Tracker (RT)Mailchimp marketing automation and email platform.
Questions
ConfigCat and Request Tracker (RT), 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 Request Tracker (RT) when something happens in ConfigCat?
Any of Request Tracker (RT)'s 19 actions, including Create Ticket, Update ticket, Update Ticket Due Date and Update Ticket Status. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Request Tracker (RT) to ConfigCat?
Yes. When something happens in Request Tracker (RT), your agent can act in ConfigCat too. This page covers both directions: Request Tracker (RT)'s triggers and ConfigCat's actions are listed here as well.
Do I have to build a connector for ConfigCat or Request Tracker (RT)?
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.
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.