Telegram

the telegram connector enables interaction with telegram bots, allowing for message automation and update retrieval within security workflows telegram is a widely used messaging platform known for its security and speed the telegram turbine connector allows users to integrate telegram's messaging capabilities directly into swimlane turbine's security workflows with this connector, security teams can automate the sending and deletion of messages, manage chat interactions, and retrieve bot updates, enhancing communication and response times during security incidents the connector's low code integration streamlines the process, making it accessible for users to leverage telegram's api without the need for coding expertise supported version the telegram connector supports bot api 9 2 version additional documents https //core telegram org/bots/api prerequisites to utilize the telegram connector within swimlane turbine, ensure you have the following custom authentication with the telegram bot using these parameters url the endpoint url for the telegram api api token the unique token provided by telegram for bot authentication authentication methods setup instructions to create a new telegram bot and obtain an authentication token, follow these steps open telegram and find botfather open the telegram app (mobile or desktop) search for @botfather in the search bar start a conversation with botfather create a new bot send the /newbot command to botfather botfather will prompt you for a bot name (this is the display name shown in contact details) provide a name for your bot (e g , "my security bot") set the bot username botfather will ask for a username for your bot the username must be 5 32 characters long not case sensitive only include latin characters, numbers, and underscores end with 'bot' (e g , tetris bot or tetrisbot ) enter a unique username (e g , my security bot ) receive your authentication token after successfully creating the bot, botfather will generate and display an authentication token the token will look like 110201543\ aahdqtcvch1vgwjxfseofsas0k5paldsaw important copy and securely store this token immediately security considerations keep your token secure and private anyone with access to your token can control your bot do not share the token publicly or commit it to version control store the token securely (e g , in a password manager or secure vault) configure the connector use the token as the api token in the telegram connector authentication settings the url should be set to https //api telegram org/bot capabilities this telegram connector provides the following capabilities delete mesage delete messages get me get updates send message delete mesage this action usesto delete a message, including service messages https //core telegram org/bots/api#deletemessage delete messages this action uses to delete multiple messages simultaneously https //core telegram org/bots/api#deletemessages get me this action returns basic information about the bot in form of a user object https //core telegram org/bots/api#getme get updates this action uses to receive incoming updates using long polling returns an array of update objects https //core telegram org/bots/api#getupdates send message this action uses to send text messages https //core telegram org/bots/api#sendmessage configurations telegram bot authentication this asset is used to authenticate with the telegram bot configuration parameters parameter description type required url a url to the target host string required api token api token for the telegram bot string required verify ssl verify ssl certificate boolean optional http proxy a proxy to route requests through string optional actions delete mesage this action usesto delete a message, including service messages endpoint url deletemessage method post input argument name type required description chat id number optional unique identifier for the target chat message id number optional unique identifier of the message to delete input example {"json body" {"chat id" 7416146050,"message id" 3}} output parameter type description status code number http status code of the response reason string response reason phrase ok boolean output field ok result boolean result of the operation output example {"status code" 200,"response headers" {"server" "nginx/1 18 0","date" "thu, 04 dec 2025 06 59 36 gmt","content type" "application/json","content length" "25","connection" "keep alive","strict transport security" "max age=31536000; includesubdomains; preload","access control allow origin" " ","access control allow methods" "get, post, options","access control expose headers" "content length,content type,date,server,connection"},"reason" "ok","json body" {"ok"\ true,"result"\ true}} delete messages this action uses to delete multiple messages simultaneously endpoint url /deletemessages method post input argument name type required description chat id number optional unique identifier for the target chat message ids array optional unique identifiers of the messages to delete input example {"json body" {"chat id" 7416146050,"message ids" \[3,4,5]}} output parameter type description status code number http status code of the response reason string response reason phrase ok boolean output field ok result boolean result of the operation output example {"status code" 200,"response headers" {"server" "nginx/1 18 0","date" "thu, 04 dec 2025 07 07 51 gmt","content type" "application/json","content length" "25","connection" "keep alive","strict transport security" "max age=31536000; includesubdomains; preload","access control allow origin" " ","access control allow methods" "get, post, options","access control expose headers" "content length,content type,date,server,connection"},"reason" "ok","json body" {"ok"\ true,"result"\ true}} get me returns basic information about the bot in form of a user object endpoint url /getme method get output parameter type description status code number http status code of the response reason string response reason phrase ok boolean output field ok result object result of the operation result id number unique identifier result is bot boolean result of the operation result first name string name of the resource result username string name of the resource result can join groups boolean result of the operation result can read all group messages boolean result of the operation result supports inline queries boolean result of the operation result can connect to business boolean result of the operation result has main web app boolean result of the operation output example {"status code" 200,"response headers" {"server" "nginx/1 18 0","date" "thu, 04 dec 2025 05 45 16 gmt","content type" "application/json","content length" "249","connection" "keep alive","strict transport security" "max age=31536000; includesubdomains; preload","access control allow origin" " ","access control allow methods" "get, post, options","access control expose headers" "content length,content type,date,server,connection"},"reason" "ok","json body" {"ok"\ true,"result" {"id" 8328642250,"is b get updates retrieve incoming updates via long polling, returning an array of update objects in telegram endpoint url getupdates method post input argument name type required description limit number optional limits the number of updates to be retrieved values between 1 100 are accepted defaults to 100 offset number optional identifier of the first update to be returned must be greater by one than the highest among the identifiers of previously received updates by default, updates starting with the earliest unconfirmed update are returned timeout number optional timeout in seconds for long polling defaults to 0, i e usual short polling should be positive, short polling should be used for testing purposes only allowed updates array optional a json serialized list of the update types you want your bot to receive for example, specify \["message", "edited channel post", "callback query"] to only receive updates of these types input example {"json body" {"limit" 1,"offset" 0,"timeout" 10,"allowed updates" \["message","edited channel post","callback query"]}} output parameter type description status code number http status code of the response reason string response reason phrase ok boolean output field ok result array result of the operation result update id number unique identifier result message object result of the operation result message message id number unique identifier result message from object result of the operation result message from id number unique identifier result message from is bot boolean result of the operation result message from first name string name of the resource result message from language code string result of the operation result message chat object result of the operation result message chat id number unique identifier result message chat first name string name of the resource result message chat type string type of the resource result message date number result of the operation result message text string result of the operation output example {"status code" 200,"response headers" {"server" "nginx/1 18 0","date" "thu, 04 dec 2025 06 26 36 gmt","content type" "application/json","content length" "260","connection" "keep alive","strict transport security" "max age=31536000; includesubdomains; preload","access control allow origin" " ","access control allow methods" "get, post, options","access control expose headers" "content length,content type,date,server,connection"},"reason" "ok","json body" {"ok"\ true,"result" \[{}]}} send message this action uses to send text messages endpoint url sendmessage method post input argument name type required description business connection id string optional unique identifier of the business connection on behalf of which the message will be sent chat id number optional unique identifier for the target chat message thread id number optional unique identifier for the target message thread (topic) of the forum direct messages topic id number optional identifier of the direct messages topic to which the message will be sent; required if the message is sent to a direct messages chat text string optional text of the message to be sent, 1 4096 characters after entities parsing parse mode string optional mode for parsing entities in the message text entities array optional parameter for send message entities type string optional type of the entity entities offset number optional offset in utf 16 code units to the start of the entity entities length number optional length of the entity in utf 16 code units entities url string optional for “text link” only, url that will be opened after user taps on the text entities user object optional for “text mention” only, the mentioned user entities user id number optional unique identifier for this user or bot this number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it entities user is bot boolean optional true, if this user is a bot entities user first name string optional user's or bot's first name entities user last name string optional user's or bot's last name entities user username string optional user's or bot's username entities language string optional for “pre” only, the programming language of the entity text entities custom emoji id string optional for “custom emoji” only, unique identifier of the custom emoji link preview options object optional link preview generation options for the message link preview options is disabled boolean optional true, if link previews for messages should be disabled link preview options url string optional url to use for the link preview if empty, then the first url found in the message text will be used link preview options prefer large media boolean optional true, if the media in the link preview is supposed to be enlarged link preview options prefer small media boolean optional true, if the media in the link preview is supposed to be shrunk link preview options show above text boolean optional true, if the media content should be shown above the text input example {"json body" {"business connection id" "string or null","chat id" 123456789,"message thread id" 123,"direct messages topic id" 1234,"text" "your message text here","parse mode" "markdownv2","entities" \[{"type" "bold","offset" 0,"length" 4,"url" "https //google com","user" {"id" 123456789,"is bot"\ false,"first name" "john","last name" "doe","username" "john doe"},"language" "en","custom emoji id" "1234567890"}],"link preview options" {"is disabled"\ false,"url" "https //google com","prefer large media"\ false,"prefer small media"\ false,"show above text"\ false},"disable notification"\ false,"protect content"\ false,"allow paid broadcast"\ false,"message effect id" "1234567890","suggested post parameters" {"price" {"amount" 100,"currency" "usd"},"send date" 26784},"reply parameters" {"message id" 123456789,"chat id" 123456789,"allow sending without reply"\ true,"quote" "123456789","quote parse mode" "markdownv2","quote entities" \[{"type" "bold","offset" 0,"length" 4,"url" "https //google com","user" {"id" 123456789,"is bot"\ false,"first name" "john","last name" "doe","username" "john doe"},"language" "en","custom emoji id" "1234567890"}]},"reply markup" {"inline keyboard" \[\[{"text" "button 1","callback data" "data1"},{"text" "open google","url" "https //google com"}]]}}} output parameter type description status code number http status code of the response reason string response reason phrase ok boolean output field ok result object result of the operation result message id number unique identifier result from object result of the operation result from id number unique identifier result from is bot boolean result of the operation result from first name string name of the resource result from username string name of the resource result chat object result of the operation result chat id number unique identifier result chat first name string name of the resource result chat type string type of the resource result date number result of the operation result text string result of the operation output example {"status code" 200,"response headers" {"server" "nginx/1 18 0","date" "thu, 04 dec 2025 06 39 43 gmt","content type" "application/json","content length" "244","connection" "keep alive","strict transport security" "max age=31536000; includesubdomains; preload","access control allow origin" " ","access control allow methods" "get, post, options","access control expose headers" "content length,content type,date,server,connection"},"reason" "ok","json body" {"ok"\ true,"result" {"message id" 5,"from" response headers header description example access control allow methods http response header access control allow methods get, post, options access control allow origin http response header access control allow origin access control expose headers http response header access control expose headers content length,content type,date,server,connection connection http response header connection keep alive content length the length of the response body in bytes 25 content type the media type of the resource application/json date the date and time at which the message was originated thu, 04 dec 2025 06 39 43 gmt server information about the software used by the origin server nginx/1 18 0 strict transport security http response header strict transport security max age=31536000; includesubdomains; preload