-
Notifications
You must be signed in to change notification settings - Fork 185
/
Copy pathconfig.yml-sample
28 lines (23 loc) · 1.4 KB
/
config.yml-sample
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
api_id: 123456 # This has to be an integer. Read more [here](https://core.telegram.org/api/obtaining_api_id)
api_hash: 'abcdefg' # Long 32 characters hash identifier. Read more [here](https://core.telegram.org/api/obtaining_api_id)
session_name: 'forwardgram' # Session name. Only one session (with a unique session name) can run at a time
# The channel names that you'd like to forward messages from.
# The user running the client must have these channels present on it's dialogs.
input_channel_names:
- 'Input Channel Name 1'
- 'Input Channel Name 2'
# The output channel names that the messages will be forwarded to.
# The user running the client must have a write access to those channels, and have the channels present on theirs dialogs.
output_channel_names:
- 'Output Channel Name 1'
- 'Output Channel Name 2'
# The channel IDs that you'd like to forward messages from. (You can get a channel ID by forwarding any message from it to @userinfobot , and removing the -100 from the start )
input_channel_ids:
- ID1 # Input Channel ID without quotes ''
- ID2
# The output channel IDs that the messages will be forwarded to. (You can get a channel ID by forwarding any message from it to @userinfobot , and removing the -100 from the start )
output_channel_ids:
- ID1 # Output Channel ID without quotes ''
- ID2
# An empty list should be set like this:
# input_channel_ids: []