Integration
Connect Request Tracker (RT) and Telegram
When Ticket Created fires in Request Tracker (RT), your agent runs Send Message in Telegram, or New Update in Telegram to Create Ticket in Request Tracker (RT). 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 Request Tracker (RT) and Telegram 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 Request Tracker (RT) and Telegram can do together
From Request Tracker (RT) to Telegram
When Ticket Created in Request Tracker (RT)
then Send Message in Telegram
When Ticket Status Changed in Request Tracker (RT)
then Update Message in Telegram
From Telegram to Request Tracker (RT)
When New Update in Telegram
then Create Ticket in Request Tracker (RT)
When New Update in Telegram
then Update ticket in Request Tracker (RT)
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 Request Tracker (RT) and Telegram
Triggers and actions 4 triggers · 33 actions
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.
Trigger
New UpdateTriggers when Telegram delivers an update to your bot. Choose which kind of update to watch — a new message, a button press, a membership change, and so on. Telegram allows one webhook per bot, so use a single New Update trigger per bot token.
Action
Ban Chat MemberBan a user from a group, supergroup or channel.
Action
Delete MessageDelete a message from a chat.
Action
Forward MessageForward an existing message from one chat to another.
Action
Get ChatGet up-to-date information about a chat (user, group, or channel).
Action
Get Chat MemberLook up one person's membership in a chat — whether they are a member, an administrator, restricted, or have left or been banned.
Action
React to MessageSets an emoji reaction on an existing message.
Action
Send Chat ActionSend a chat action (e.g. typing, upload_photo) to indicate the bot is doing something.
Action
Send DocumentSend a general file/document to a chat.
Action
Send LocationSend a point on the map to a chat.
Action
Send MessageSends a message from your bot.
Action
Send PhotoSends a photo from your bot.
Action
Send PollSends a poll from your bot.
Action
Send VideoSend a video to a chat.
Action
Update MessageEdit the text of a previously sent message.
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 Request Tracker (RT)
Request Tracker (RT) to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Request Tracker (RT) to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Request Tracker (RT) to StripeStripe is a payment processing platform for online businesses.
Request Tracker (RT) to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Request Tracker (RT) to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Request Tracker (RT) to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
More into Telegram
Stripe to TelegramStripe is a payment processing platform for online businesses.
Better Stack to TelegramBetter Stack is a tool to provide reliable monitoring with voice calls and beautiful on-call scheduling.
CRUSH to TelegramCRUSH is an AI powered second brain helping you collect a thought, organize it and take action.
Guerrilla Mail to TelegramGuerrilla Mail issues disposable temporary email addresses that receive mail without a signup.
Snitcher to TelegramSnitcher is a B2B visitor ID platform that helps you uncover your anonymous website visitors.
HubSpot to TelegramHubSpot is your all-in-one stop for all of your marketing software needs.
Questions
Request Tracker (RT) and Telegram, answered
What can start an automation from Request Tracker (RT)?
Any of Request Tracker (RT)'s 3 triggers in the catalog, including Ticket Created, Ticket Status Changed and Ticket Correspondence. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Telegram when something happens in Request Tracker (RT)?
Any of Telegram's 14 actions, including Send Chat Action, Send Document, Send Location and Send Message. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Telegram to Request Tracker (RT)?
Yes. When something happens in Telegram, your agent can act in Request Tracker (RT) too. This page covers both directions: Telegram's triggers and Request Tracker (RT)'s actions are listed here as well.
Do I have to build a connector for Request Tracker (RT) or Telegram?
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 Request Tracker (RT) and Telegram 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.