Skip to main content
Glama

Simpler.Asia

interaction_create

Log an interaction — call, meeting, email, message, visit, payment, or other — against a contact. The ONE activity-logging door every lane funnels through, so the contact's last_contact_at freshness bumps no matter which surface logged the touch; the bump never moves backward, so importing older history can never regress a fresher touch. Accepts contact_name, contact_email or contact_phone in place of contact_id. NEXT: contact_read to see the bumped last_contact_at.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryNo
contact_idNo
source_refNo
occurred_atNo
contact_nameNoNo contact_id handy? Resolves the contact by exact name — a unique match wins; ambiguity refuses with the candidate ids.
contact_emailNoResolves the contact by exact email when contact_id is absent.
contact_phoneNoResolves the contact by exact phone when contact_id is absent.
interaction_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources