This is enabled by default.Ĭ-start-producer Whether to enable auto configuration of the telegram component. By default the consumer will use the .ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. when you want to test the component against a mock Telegram API.Ĭ-error-handlerĪllows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.Ĭan be used to set an alternative base URI, e.g. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. The default Telegram authorization token to be used when the information is not provided in the endpoints.Ĭ-enabled It gets converted automatically into a OutgoingTextMessageĬ-token It requires the CamelTelegramMediaType header to be set to the appropriate media type To send information about a venue (sendVenue)

To stop updating a live location message sent by the bot or via the bot (for inline bots) before live_period expires (stopMessageLiveLocation) To send changes to a live location (editMessageLiveLocation) To delete a message, including service messages. To edit only the reply markup of message. To edit animation, audio, document, photo, or video messages. To edit captions of messages (editMessageCaption) To edit text and game messages (editMessageText)

To send a file to a chat (any media type)

Telegram rss bot rss.xml atom.xml