calendar-events

name	calendar-events
description	Link upcoming events to CRM context; do not create them.
metadata	{"short-description":"Connect upcoming meetings to CRM context"}

Calendar Events

Outcome

An upcoming-event view enriched with the right account, people, deal, and preparation context.

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: Calendar events, attendees, CRM people and organizations, related opportunities, tasks, and recent interactions.
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. Match attendees and event context to CRM records conservatively; show ambiguous matches instead of choosing silently.
2. Identify external versus internal attendees, timezones, overlaps, travel or buffer constraints, and missing agendas.
3. For customer meetings, surface the most relevant active opportunity, open commitments, and last meaningful interaction.
4. Do not infer attendance, account association, or meeting purpose without evidence.

Required output

• Chronological agenda
• CRM-linked event context
• Conflicts and preparation gaps
• Suggested prep actions

Actions and boundaries

This workflow is read-only. Use the scheduling workflow for invitations or calendar mutations.