log-activity

name	log-activity
description	Prepare an activity log; confirm before writing.
metadata	{"short-description":"Log interactions to the correct CRM records"}

Log Activity

Outcome

A complete, deduplicated activity record with accurate participants, time, type, summary, and associations.

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: User-provided interaction details or authorized source item, participant identities, timestamp and timezone, channel, related account, person, lead, opportunity, and follow-up.
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. Verify that the interaction occurred and resolve participants and target records unambiguously.
2. Check for an existing synced or manually logged copy using source identifier, participants, time, subject, and related records.
3. Map to the provider's activity type and required fields without losing the original timestamp or source.
4. Keep the summary factual and distinguish follow-up commitments from completed activity.

Required output

• Proposed activity
• Resolved associations
• Duplicate check
• Required fields and summary
• Optional follow-up tasks
• Write result

Actions and boundaries

Show the complete activity and associations, obtain confirmation, create once, and report the resulting record or exact failure.