Pulses beta
Schedule AI-generated test reports to your integrations on a recurring basis.
What you can do
- Write instructions in plain language for each report
- Pick an integration and schedule (daily, weekly, or monthly)
- Test & Save before relying on the schedule
- Enable or disable without deleting
- Review delivery history for past runs
Pulse vs AI Studio
| Pulses | AI Studio | |
|---|---|---|
| Interaction | Set once, runs on a schedule | Ad-hoc conversational Q&A |
| Output | Delivered to chat integrations | Displayed in the Portal |
| Best for | Recurring team updates | Exploring data, one-off questions |
See AI Studio overview.
How Pulses differ
- vs AI Studio — scheduled delivery to Slack, Teams, or Google Chat, not in-app chat
- vs CLI targets — analyzes Portal history on a schedule; CLI targets push per-run results from
testbeats publish. Separate config: integrations vs targets
Prerequisites
- Test results in the Portal (Getting Started)
- At least one organization integration
- Org access to manage integrations and pulses
AI credits
Pulses consume org AI credits for Test & Save and scheduled runs. Over-limit orgs skip scheduled runs until credits are available. See Service Limits.
Limits
| Limit | Value |
|---|---|
| Schedule time zone | UTC (24-hour) |
| Monthly schedule | Days 1–28 only |
| Integrations per pulse (UI) | One |
| Pulse triggers per org | Up to 100 |
| Concurrent test per pulse | One at a time |
Deleting a pulse removes its triggers and delivery history.
Start with Getting Started.