Add to Chrome
Most websites do not expose webhooks or APIs for real-time events. Browser Triggers solve this by monitoring your open tabs for web push notifications and executing workflows when matching notifications arrive.
How Browser Triggers Work
The extension injects an interceptor into monitored tabs that patches Notification and ServiceWorkerRegistration.showNotification. Notification title/body metadata is matched against your trigger filters, and matching events run the linked workflow automatically.
- 01
Intercept notifications from page and Service Worker paths
- 02
Match by hostname plus optional title/body contains filters
- 03
Run linked workflow in a new tab when a match is found
- 04
Store execution history with matched payload and status
Creating a Browser Trigger
- 01
Run a workflow successfully in side panel chat
- 02
Click the "Trigger" button on the workflow response
- 03
Enter the URL to monitor (for example: x.com, app.slack.com)
- 04
Add optional title/body filters
- 05
Set cooldown to prevent rapid re-firing
- 06
Save to activate monitoring
Notification Matching
| Filter | Example | Matches |
|---|---|---|
| Title contains | "new message" | Notifications with "new message" in title |
| Body contains | "price drop" | Notifications with "price drop" in body |
| Both | Title: "alert", Body: "urgent" | Only when both match |
| None | — | All notifications from monitored hostname |
Cooldown Recommendations
| Site Type | Recommended Cooldown |
|---|---|
| Chat apps (Slack, Discord) | 5-15 minutes |
| Social apps (X, LinkedIn) | 15-30 minutes |
| Price alerts | 30-60 minutes |
| Daily digests | 1440 minutes (24 hours) |
Monitored Tab Groups
- 01
Matching tabs are grouped into a yellow "Monitored" tab group
- 02
Closing a tab pauses monitoring for that tab
- 03
Reopening the URL resumes monitoring automatically
Manual Testing
Use the "Test" action in the Triggers dropdown to run the workflow immediately without waiting for a live notification.
Limitations
- 01
Monitored tabs must stay open
- 02
Pure Service Worker push flows may not always be interceptable
- 03
Chrome must be running; for 24/7 inbound signals use /docs/webhooks
Best Practices
- 01
Use specific filters to avoid false positives
- 02
Set cooldowns for chatty sources to manage credit burn
- 03
Validate every trigger with Test before production usage