Read monitoring definitions for one explicit project.
Practical procedure
- Supply the required projectId query parameter to /pulse/monitors.
- Read the monitors array and retain each monitor identity separately from its display title.
- Render an empty list separately from an unavailable-storage response.
Define an evidence-backed Pulse monitor
Pulse monitors track an objective against selected Knowledge sources. A definition records cadence, timezone, source policy, materiality rule and notification mode. Review and approve the exact definition version before running it. An occurrence records a particular run; it is distinct from the monitor definition and from any resulting email delivery.
Contract example
Developer examples below describe routes on an authorized, configured GoCux control-plane base URL. They are request shapes or operation references, not claims that a particular public hostname exposes the API. Use the workspace for the corresponding human workflow; availability and permissions depend on the actual deployment.
Operation reference for this workflow
GET /pulse/monitors?projectId=project-idInspect the result
Inspect occurrence state and available evidence before reporting a change. A new or missing source passage can change the support for a value even when the displayed value is unchanged. Notification mode can be none or email; choosing email is not evidence that delivery is configured or that a message reached its recipient.
What to keep explicit
The list request needs the authenticated company context as well as a project identifier. A title is not a durable lookup key.
Handle incomplete and refused work
Creation requires at least one unique Knowledge source identifier. Decisions and transitions use explicit version checks and Idempotency-Key. A stale definition or a monitor that is not active can return 409. A 503 is unavailable monitor storage or materialization, not a statement that nothing changed. Pause or archive intentionally when the monitoring objective ends.
Continue with related guides
Bring this workflow into your workspace.
Set the scope. Review the evidence. Approve the steps that need it.