Skip to main content
Four ways results leave Openpulse, and they are meant to be used together. This page covers email, urgency alerts and export; the other two live in their own tabs because they are built for a machine rather than a person — see Webhooks, the API reference, and MCP & agents.

​
Email

A run summary after every completed run, with the top signals inline, and a short note when a run fails. Recipients resolve most-specific-first: the listener’s own list, then the workspace’s, then the workspace admins.

​
Urgency alerts

Most signals wait for the run summary. A few are worth interrupting somebody for, and one rule decides which — set once, by an admin, in workspace settings:
Deliberately not a rule builder. Low and medium urgency are not offered: a signal that is neither urgent nor high-scoring is not an interruption, it is a list. The daily cap is load-bearing. An alert that fires forty times in a morning gets muted by lunch, and a muted channel is worse than no channel. When more signals qualify than the cap allows, the highest-scoring ones are sent. Custom alerts — bespoke rules built for you on request — are available on higher plans; see openpulse.cloud/pricing.

​
CSV and CRM export

Three exports, each mirroring a screen: signals, accounts and pipeline. Each takes the same filters as the screen it mirrors, so what downloads is what was on screen. Admins may export unfiltered; members must narrow it with a filter first. An unfiltered export is the whole workspace in one file, and every export is written to the audit log with the actor, the filter and the row count. See openpulse.cloud/pricing for the monthly export allowance and which formats each plan includes. Files carry a UTF-8 byte-order mark so Excel on Windows does not mangle non-ASCII company names, and any cell that a spreadsheet would execute as a formula is neutralised without losing a character of the original. The equivalent export endpoints — /v1/exports/signals.csv, /v1/exports/accounts.csv and /v1/exports/pipeline.csv — are in the API reference under the export:read scope.