Event Testing Tool
The Event Testing Tool lets you build a fake event with your own field values and either check whether an alert's conditions would pass, or send the event into TipLink's pipeline to fire actions.
Access it from the Alerts page by clicking "Test Event".
Two Modes
The tool has two modes, selectable at the top of the payload step.
Full Pipeline
The event is injected into TipLink's normal processing pipeline — exactly as if it arrived from the real platform. Every alert that matches the event's platform, type, and conditions will fire its actions.
Use this to test a realistic event end-to-end without needing the real platform to send it.
Available button: Send Test Event — injects the event and fires all matching alerts.
Target Specific Alert
You pick one specific alert to test against. This mode gives you two separate operations:
Check Conditions (the dry-run button) Evaluates whether the selected alert's pre-filters and conditions would pass for this event — without firing any actions and without affecting rate limit counters. The results panel shows each check individually (pass/fail), the actual value seen, and a final "would fire" verdict.
Send Test Event Fires the actions in the selected alert directly, bypassing condition checking entirely. This is the same behaviour as the existing Test Actions button, but with custom event field values you choose.
After a Check Conditions run, if the alert would not fire, a "Trigger Actions Anyway" button appears in the results panel — letting you force the actions to run even when conditions fail, useful for checking that an action itself is configured correctly independent of conditions.
What "Check Conditions" Reports
The results panel breaks down every gate the alert must pass:
| Check | What it verifies |
|---|---|
| Alert Set Enabled | The alert's parent set (if any) is enabled |
| Alert Enabled | The alert itself is not disabled |
| Platform Match | The event's platform is configured for this alert |
| Event Type Match | The event type is listed as a valid trigger |
| Has Enabled Actions | At least one action is enabled |
| Account Match | The event's account is configured for this alert |
| Conditions | Each configured condition (min/max, text match, username filter, etc.) |
| Rate Limit | Whether the alert would currently be blocked by a cooldown |
The final "Would fire" / "Would NOT fire" verdict summarises the overall result.
Example: Testing a Donation Condition
You have an alert that fires only when a donation is $10 or more. Before going live:
- Click Test Event on the alert.
- Select the platform and event type (e.g. Fansly → Tip).
- Switch to Target Specific Alert mode and select the alert.
- Set
valueto9.99and click Check Conditions → should show "Would NOT fire" (amount too low). - Change
valueto10.00and click Check Conditions again → should show "Would fire". - Click Send Test Event to confirm the actions themselves look correct.
Tips
- Check Conditions is entirely read-only: no activity log entries, no actions fired, rate limits unaffected.
- Send Test Event in Target Alert mode bypasses conditions — actions fire regardless of whether the event would normally match.
- Full Pipeline mode is useful when you want to verify multiple alerts respond to the same event correctly.
- Leave a field blank to simulate a missing/empty value — useful for testing fallback behaviour in placeholders.