Skip to main content
list_outreach_outcomes Read saved, attributed campaign updates and held conflicts for one website. Dates describe supplied events, not mailbox polling coverage. No message bodies are stored.
Name recorded in the 2026-10-27 deployment. This page describes current source; verify inputs and access in your connected catalog. Provider configuration and workspace access still apply.
This operation reads or updates saved campaign records with the contacts capability enabled. It starts no verification, schedule, message or sequence and consumes no checking credits.

Example request

Connect through MCP, CLI, or HTTP. Replace example identifiers with records from your workspace.

Returned result

Schema-validated example; IDs and dates are illustrative. MCP returns this data in structuredContent and in a text content block; generic HTTP and CLI return the JSON result directly.

Input fields

Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.

Validation and omitted values

Read the website journal, optionally filtered by watchId or contactId. Its supplied event date and received date do not claim mailbox polling coverage. Held events remain visible with their disposition. Rows are ordered by event record ID. Omit after for the first page, then pass nextAfter unchanged with the same website and filters. The cursor is a continuation ID, not an event-time checkpoint. This read starts no checks or outreach. Private contact facts erased with a deleted contact no longer appear; retained watch-owned history may have a null contact binding.

Defaults when omitted

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
  • items (array, required): Records in this bounded page.
  • nextAfter (string / null, required).
Types, allowed values, limits and nested fields:
Download input schema · Download output schema

Errors and retries

Follow the error recovery before retrying this read. Preserve the selected workspace, project, filters and feed. Recovering a read does not require an idempotency key or another verification job. Operation-specific errors include UNAUTHORIZED, INSUFFICIENT_SCOPE, CAMPAIGN_RECORDS_NOT_READY, OUTCOME_ACCESS_DENIED, CAMPAIGN_SCOPE_CLOSED, INVALID_OUTCOME_INPUT, WATCH_NOT_FOUND. See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.

HTTP resource routes

This operation has no separate resource alias. Use its generic command route in a matching environment.

Continue

get_prospect · list_contacts Follow the related workflow. See capability status for availability or the command index for another operation.