query-activity-history

name	query-activity-history
description	Query activity history; never create or modify it.
metadata	{"short-description":"Retrieve a clear CRM activity timeline"}

Query Activity History

Outcome

A filtered, chronological interaction history with source coverage and meaningful gaps.

CRM-neutral operating contract

• Discover available CRM, communication, calendar, knowledge, and file capabilities before choosing a retrieval plan. If no live CRM is available, use user-supplied exports when that still satisfies the request; never imply a live write is possible.
• Map records by meaning, not vendor labels: organization, person, lead, opportunity, activity, product, service record, user or team, and knowledge item. Inspect schemas and custom fields, preserve native IDs, stages, currencies, timezones, and fiscal periods.
• Keep observed facts, derived conclusions, and missing information distinct. Anchor consequential claims to record IDs, fields, timestamps, or named sources, and state access or freshness limits.
• Start read-only. Before creating, updating, assigning, sending, or scheduling, show the exact proposed action and obtain confirmation unless the current request already authorized that exact mutation.
• Obey connected-system permissions, resolve ambiguous records or people instead of guessing, check for duplicates before creation, and report partial failures without repeated retries.

Workflow

1. Resolve the user, target records, requested scope, reporting window, timezone, and business objective. Ask only for missing details that materially change the result.
2. Retrieve the minimum authorized evidence needed from the following inputs: Target entity, time window, activity types, owners or participants, completion status, related records, and desired level of detail.
3. Normalize relevant entities and fields while retaining native record identifiers and source timestamps.
4. Apply the analysis rules below. When evidence conflicts, show the conflict rather than averaging it away.
5. Deliver the required output in a compact form suited to the scope. Put urgent or decision-relevant items first.

Analysis rules

1. Resolve the target and filters before querying and state any provider limits or inaccessible activity sources.
2. Deduplicate synced and manually logged representations while preserving distinct interactions.
3. Order by actual interaction time rather than record update time and normalize timezones for presentation.
4. Summarize meaningful cadence, commitments, and gaps without interpreting no logged activity as proof of no contact.

Required output

• Query scope
• Chronological timeline
• Activity summary by type or period
• Open commitments
• Coverage and capture caveats

Actions and boundaries

Strictly read-only. Route creation or correction requests to the appropriate workflow.