Build solutions, not workarounds.
What do you want Telegram and Queue 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 Telegram can start in Queue
When New Update in Telegram
then Add client in Queue
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 Telegram and Queue
Triggers and actions 1 trigger · 38 actions
- New Update
Triggers 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.
- Ban Chat Member
Ban a user from a group, supergroup or channel.
- Delete Message
Delete a message from a chat.
- Forward Message
Forward an existing message from one chat to another.
- Get Chat
Get up-to-date information about a chat (user, group, or channel).
- Get Chat Member
Look up one person's membership in a chat — whether they are a member, an administrator, restricted, or have left or been banned.
- React to Message
Sets an emoji reaction on an existing message.
- Send Chat Action
Send a chat action (e.g. typing, upload_photo) to indicate the bot is doing something.
- Send Document
Send a general file/document to a chat.
- Send Location
Send a point on the map to a chat.
- Send Message
Sends a message from your bot.
- Send Photo
Sends a photo from your bot.
- Send Poll
Sends a poll from your bot.
- Send Video
Send a video to a chat.
- Update Message
Edit the text of a previously sent message.
- Add client
Create a new client.
- Add column
Create a new column on a project board.
- Add invoice
Creates a new invoice in a Queue project with the given line items and billing details.
- Add project
Create a new project.
- Create Task
Creates a task in a project in a column.
- Create Task Comment
Creates a Task Comment for a Task.
- Delete client
Delete a client.
- Delete column
Deletes a column from a Queue project.
- Delete project
Deletes a project in Queue.
- Delete task
Deletes a task in Queue by its ID.
- Delete task comment
Deletes a comment from a task in Queue.
- Get invoice
Retrieves a specific invoice by its ID.
- Get project
Retrieve a single project by id.
- Get task
Retrieve a single task by its ID, including its custom field values and sections.
- Get task comment
Retrieves a single task comment by its ID.
- List clients
Lists the clients attached to a Queue project.
- List columns
Lists the columns on a Queue project's board.
- List invoices
Returns all invoices for a project.
- List projects
Lists the projects in your Queue workspace.
- List tasks
Lists the tasks in a column of a Queue project.
- Update column
Updates a column's title, position, stage, or task behavior in a Queue project.
- Update project
Update an existing project.
- Update task
Updates an existing task by ID
- Update task comment
Update an existing task comment.
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 Telegram
Telegram to GalileoGalileo is a tool that turns text into beautiful UI designs instantly with Galileo AI—fast, smart, and ready...
Telegram to NewtonNewton is a symbolic and arithmetic mathematics engine exposed over HTTP.
Telegram to NextdnsCloud-based DNS filtering service for blocking malware, ads, and trackers, with an API to manage profiles...
Telegram to Umeå Open DataUmeå Open Data is the municipal open data portal for the city of Umeå in northern Sweden.
Telegram to Google SheetsGoogle Sheets
Telegram to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into Queue
HubSpot to QueueHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to QueueSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to QueueSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Calendar to QueueGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Telegram and Queue, answered
What can start an automation from Telegram?
Any of Telegram's 1 trigger in the catalog, including New Update. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Queue when something happens in Telegram?
Any of Queue's 24 actions, including Create Task, Create Task Comment, Update column and Update project. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Queue to Telegram?
Queue has no triggers in the catalog today, so automations start in Telegram. If you need the other direction, ask: your agent reads Queue's API documentation and adds it.
Do I have to build a connector for Telegram or Queue?
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.