Event Modifiers
Filter and redirect GitHub events on a per-webhook or per-repository basis.
Event modifiers let you customize exactly which GitHub events get posted to Discord. You can:
- Blacklist events so they are silently dropped
- Whitelist events so only the listed types are delivered (everything else is dropped)
- Redirect specific events to a different channel
Each webhook supports a maximum of 10 event modifiers. Modifiers are evaluated in priority order (higher number = higher priority).
How priority works
When an event arrives, Octoflow evaluates your modifiers in descending priority order. The first modifier whose event list matches the incoming event type is applied. Use priority 0 for most cases; raise it on a modifier if you need it to fire before others.
Blacklist vs whitelist
| Mode | Behavior |
|---|---|
| Blacklisted | Events matching the list are dropped. Everything else passes through. |
| Whitelisted | Only events matching the list are delivered. Everything else is dropped. |
You can set both flags to false on a redirect modifier to route specific events to a different channel without blocking or allowing anything else.
When using redirect_channel, set both blacklisted and whitelisted to false. Combining redirect with whitelist/blacklist can produce confusing results.
Wildcard matching
Event names in the events list support two wildcard characters, so a single modifier can match a whole family of events:
*matches zero or more characters?matches exactly one character
For example, events:workflow_* matches both workflow_run and workflow_job, and events:pull_request* matches pull_request, pull_request_review_comment, and any other event starting with pull_request.