Integration
Connect Telegram to Spike.sh
When something happens in Telegram, your agent does the next thing in Spike.sh. Describe it 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 Telegram and Spike.sh 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 Spike.sh
When New Update in Telegram
then Add alert rule in Spike.sh
When New Update in Telegram
then Add escalation in Spike.sh
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 Spike.sh
Triggers and actions 1 trigger · 39 actions
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.
Action
Acknowledge incidentAcknowledge one or more Spike.sh incidents by counter id or incident id.
Action
Add alert ruleCreate a new alert routing/automation rule with conditions and actions.
Action
Add escalationCreates a new escalation policy for a Spike.sh team, defining who is notified, through which channel, and how long to wait between steps.
Action
Add integrationCreate a new integration for a team (source system that sends alerts into Spike).
Action
Add on-callCreate a new on-call schedule for a team.
Action
Add serviceCreate a new service in a team, with name and description.
Action
Create IncidentCreates a Spike incident through one of your integrations and sends alerts. The integration decides which service and escalation policy the incident is routed to.
Action
Delete alert ruleArchives (soft-deletes) a Spike alert rule so it no longer applies to incoming incidents.
Action
Delete escalationArchives (soft-deletes) a Spike escalation policy by its ID.
Action
Escalate incidentEscalates one or more Spike incidents to the next step of their escalation policy.
Action
Get escalationGet escalation policy details by id.
Action
Get incidentFetch a single incident by counter id.
Action
Get integrationFetches an integration by its token, including its name, type, service, escalation settings and webhook URL. An error occurs if the integration is not found.
Action
Get serviceGet a Spike service's details, along with its incidents and open-incident count.
Action
List alert rulesLists all alert rules (enabled and disabled) configured for a Spike team.
Action
List escalationsLists the escalation policies that belong to a Spike team.
Action
List incidentsLists the incidents for a Spike.sh team.
Action
List on-callsLists the on-call schedules for a team.
Action
List servicesLists the services in a Spike team.
Action
List teamsLists every team in your Spike organisation. Use a team's ID from here wherever other Spike actions ask for a team.
Action
Resolve incidentResolve one or more incidents by counter id array.
Action
Update alert ruleReplace an existing Spike alert rule's name, conditions and actions.
Action
Update escalationReplaces an existing escalation policy's name, steps and start delay. The whole policy is replaced, so send every step you want to keep.
Action
Update on-callUpdates an on-call schedule's name and/or moves it to another team. Rotations and layers are not changed by this action.
Action
Update serviceUpdates the name and/or description of an existing Spike.sh service.
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 Spike.sh
HubSpot to Spike.shHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Spike.shSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Spike.shSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Spike.shGoogle Sheets
Gmail to Spike.shGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Spike.shGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Telegram and Spike.sh, 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 Spike.sh when something happens in Telegram?
Any of Spike.sh's 25 actions, including Create Incident, Update alert rule, Update escalation and Update on-call. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Spike.sh to Telegram?
Spike.sh has no triggers in the catalog today, so automations start in Telegram. If you need the other direction, ask: your agent reads Spike.sh's API documentation and adds it.
Do I have to build a connector for Telegram or Spike.sh?
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.