Flow reference: Logic
Regex Match
Test text against a regular expression.
Test text against a regular expression.
When and how to use it
Connect the input from the preceding step on the path that should perform this operation.
Fill the fields with data available in the trigger's context.
Connect the needed outputs; an unconnected path cannot run later blocks.
Configuration fields
Text — text
Text input for this check, transformation or suggestion. If it comes from a member, avoid treating it as trusted code or configuration.
Input: Text with variable suggestions.
Default:
{message.content}.Pattern — pattern
Regular-expression pattern, not ordinary text to insert. Test a short match and non-match before using live user input.
Input: Text.
Default: ``.
Flags — flags
Regular-expression flags such as i for case-insensitive matching. Use only flags supported by the runtime.
Input: Text.
Default:
i.Store first match as — storeAs
Choose a short result prefix such as result. Later blocks must use this same prefix and run after this block. It is not a Discord channel or a persistent table.
Input: Text.
Default:
match.Outputs and next steps
true: The condition matched.false: The condition did not match.Read the result after this block, using its configured prefix and the fields supported by the selected operation. Do not assume every response has a text or id field.
Test and troubleshoot
Invoke the correct trigger with simple inputs and verify the expected effect. Confirm variables exist on this path. A preview alone does not verify Discord delivery.
Save, validate and publish. Perform one real test and read the first relevant log error. [Testing](/docs/flow-testing) · [Variables](/docs/flow-variables) · [Permissions](/docs/flow-permissions).
Save, validate and publish. Perform one real test and read the first relevant log error. [Testing](/docs/flow-testing) · [Variables](/docs/flow-variables) · [Permissions](/docs/flow-permissions).