Find a file
2023-10-05 22:31:27 +03:00
.github/workflows Blacken and isort code, add pre-commit and CI linting 2023-10-05 22:22:10 +03:00
reactbot Blacken and isort code, add pre-commit and CI linting 2023-10-05 22:22:10 +03:00
samples Fix linting 2023-10-05 22:31:27 +03:00
.gitignore Initial commit 2019-06-21 14:49:50 +03:00
.gitlab-ci.yml Move CI script to main maubot repo 2022-06-19 14:27:31 +03:00
.pre-commit-config.yaml Fix linting 2023-10-05 22:31:27 +03:00
base-config.yaml Separate per-user and per-room flood limits 2019-06-23 14:20:25 +03:00
LICENSE Initial commit 2019-06-21 14:49:50 +03:00
maubot.yaml Bump version to 2.2.0 2021-08-18 00:03:06 +03:00
pyproject.toml Blacken and isort code, add pre-commit and CI linting 2023-10-05 22:22:10 +03:00
README.md Update README.md 2023-10-05 22:13:26 +03:00

reactbot

A maubot that responds to messages that match predefined rules.

Samples

Config format

Templates

Templates contain the actual event type and content to be sent.

  • type - The Matrix event type to send
  • content - The event content. Either an object or jinja2 template that produces JSON.
  • variables - A key-value map of variables.

Variables that start with {{ are parsed as jinja2 templates and get the maubot event object in event. As of v3, variables are parsed using jinja2's native types mode, which means the output can be a non-string type.

If the content is a string, it'll be parsed as a jinja2 template and the output will be parsed as JSON. The content jinja2 template will get event just like variable templates, but it will also get all of the variables.

If the content is an object, that object is what will be sent as the content. The object can contain variables using a custom syntax: All instances of $${variablename} will be replaced with the value matching variablename. This works in object keys and values and list items. If a key/value/item only consists of a variable insertion, the variable may be of any type. If there's something else than the variable, the variable will be concatenated using +, which means it should be a string.

Default flags

Default regex flags. Most Python regex flags are available. See docs.

Most relevant flags:

  • i / ignorecase - Case-insensitive matching.
  • s / dotall - Make . match any character at all, including newline.
  • x / verbose - Ignore comments and whitespace in regex.
  • m / multiline - When specified, ^ and $ match the start and end of line respectively instead of start and end of whole string.

Rules

Rules have five fields. Only matches and template are required.

  • rooms - The list of rooms where the rule should apply. If empty, the rule will apply to all rooms the bot is in.
  • matches - The regex or list of regexes to match.
  • template - The name of the template to use.
  • variables - A key-value map of variables to extend or override template variables. Like with template variables, the values are parsed as Jinja2 templates.

The regex(es) in matches can either be simple strings containing the pattern, or objects containing additional info:

  • pattern - The regex to match.
  • flags - Regex flags (replaces default flags).
  • raw - Whether or not the regex should be forced to be raw.

If raw is true OR the pattern contains no special regex characters other than ^ at the start and/or $ at the end, the pattern will be considered "raw". Raw patterns don't use regex, but instead use faster string operators (equality, starts/endwith, contains). Patterns with the multiline flag will never be converted into raw patterns implicitly.