🔑 Get Current User Info - CALL THIS FIRST!
get-current-user-infoRetrieves the current user's contact ID, required as OwnerId and AuthorId when creating CRM records. Call this first before any create operation.
Instructions
⚠️⚠️⚠️ MANDATORY FIRST STEP ⚠️⚠️⚠️
🚨 YOU MUST CALL THIS TOOL FIRST before creating ANY Activity, Lead, Opportunity, Case, or other CRM record!
WHY CALL FIRST:
Returns the ContactId needed for OwnerId and AuthorId fields
Without this, you CANNOT create activities or CRM records correctly
Activities MUST have valid OwnerId and AuthorId (both = ContactId)
By default, ALL activities/leads/tasks are created FOR THE CURRENT USER
📋 REQUIRED WORKFLOW: Step 1: Call get-current-user-info (no parameters) ← DO THIS NOW! Step 2: Extract contactId from response Step 3: Store contactId in memory for this conversation Step 4: Use contactId as OwnerId and AuthorId in ALL create operations
Returns: { "userId": "410006e1-ca4e-4502-a9ec-e54d922d2c00", "contactId": "76929f8c-7e15-4c64-bdb0-adc62d383727", // ← SAVE THIS! "userName": "Current User", "cultureName": "en-US" }
USE CASES (when to call): ✅ User asks to create activity/meeting/task/call → CALL THIS FIRST! ✅ User asks to create lead/opportunity/case → CALL THIS FIRST! ✅ User asks who they are → CALL THIS! ✅ Beginning of ANY CRM workflow → CALL THIS FIRST! ❌ Simple queries (read/search) → Not required
CRITICAL RULES:
ContactId (NOT userId) goes into OwnerId/AuthorId fields
Cache the ContactId - don't call repeatedly
Default assumption: create records FOR current user
Only change owner if user explicitly says "for [someone else]"
Example usage: User: "Create a meeting for tomorrow" YOU: 1) Call get-current-user-info 2) Use contactId for OwnerId and AuthorId 3) Create activity with those IDs
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||