Skip to main content
update_prospect Change saved opportunity context or supplied progress at its current revision. Supplied outcomes cannot declare a verified win; existing checks and monitoring preferences are preserved.
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

Use the current opaque revision from get_prospect. Omitted fields retain their saved values. After an uncertain response or revision conflict, read the record and compare the intended fields before retrying; do not blindly repeat an old revision. Context and supplied progress edits preserve evidence, jobs and monitoring preferences. They do not send outreach or establish a verified win. A verified win cannot be manually downgraded. An unverified legacy won label can be corrected. Explicit candidate on an unarchived, unverified record sets intent to prospect. This reopens retired or closed records without resuming checks. Metadata-only edits do not reopen them. A record with check history keeps its original placement. A record with supplied outcome history keeps its publisher and destination. A conflicting placement refuses changes without merging records. archived true is compensating rollback for an unused saved opportunity with checks off and no check or outcome history. It retains the row and excludes it from lists. Changing progress never restores an archived record.

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
  • prospect (object, required).
  • replayed (boolean, required): True when the response reuses an earlier request with the same idempotency value.
Types, allowed values, limits and nested fields:
Download input schema · Download output schema

Errors and retries

This write is annotated idempotent without a caller-supplied idempotency key. Reconcile saved state after an uncertain response, then use the same inputs for the same intended operation. Do not add an unsupported key. Operation-specific errors include UNAUTHORIZED, INSUFFICIENT_SCOPE, CAMPAIGNS_NOT_READY, PROSPECT_ACCESS_DENIED, INVALID_PROSPECT_INPUT, PROSPECT_NOT_FOUND, PROSPECT_REVISION_CONFLICT, PROSPECT_VERIFIED_WIN, PROSPECT_PLACEMENT_IMMUTABLE, PROSPECT_PLACEMENT_CONFLICT, PROSPECT_ROLLBACK_UNSAFE, WATCH_QUOTA_EXCEEDED. 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 · verify_prospect · set_prospect_monitoring Follow the related workflow. See capability status for availability or the command index for another operation.