WordPress Telegram Bot - Log (Checking Performed Rules)

Log (Checking Performed Rules)

Back to User Guide

What is This Feature

With the WordPress Telegram Bot plugin you can check all performed actions in the log. It helps you monitor the bot responses and operation and, in case of errors, lets you understand what is the rule that did not work as expected.

Capturing Group ID

The log is also useful for detecting the group ID. Once adding the Bot to a group as an admin, it will start sending the content of that group to the plugin. In such case you can find out what is the group number without using the command line within the group stream.

To access the log, head to WP Admin → CM Telegram Bot → Log.

Navigation to the log - Telegram Group Bot Manager
Navigation to the log

The log shows, for each each action:

  • Group ID - This field can be useful to retrieve this number
  • User Name 
  • Message - All group messages are logged, even if they don't trigger any rule
  • Actions - Identifies the rules and
  • Status
  • Date 


Example of the log - WordPress Telegram Plugin
Example of the log

TIP 1: Identifying Rule

The column "Actions" shows which rule was triggered. The example below shows Sending SMS.

If the message was empty or had an unsupported format (for instance, audio), the description will be "empty message", also shown below.

Examples of logged actions - Telegram WordPress Widget
Examples of logged actions

TIP 2: Rules With Multiple Groups/Mobile Numbers

When a rule affects multiple groups or SMS or mobile numbers, the log will display the status of each side by side:

Actions for multiple groups - Telegram Plugin for WordPress
Actions for multiple groups

More information about the WordPress Telegram Bot plugin

Other WordPress products can be found at CreativeMinds WordPress Store

Let us know how we can Improve this Product Documentation Page

To open a Support Ticket visit our support center
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.