cantrip_entity_add
Add new entities like customers, pain points, or experiments to Cantrip's GoToMarket platform to organize and track business development data.
Instructions
Create a new entity. Automatically marked as 'accepted'. Fields vary by type:
icp: name, description, demographics, jobs_to_be_done, willingness_to_pay, current_alternatives, priority, is_beachhead
pain_point: description, severity (low|medium|high|critical), frequency (rare|occasional|frequent|constant), evidence
value_prop: framing (required — use instead of 'name'; 'description' is stored in extensions), tagline, evidence
channel: name, channel_type, lifecycle_stage (exploring|testing|scaling|maintaining|killed), cac, estimated_reach, conversion_rate (note: 'description' maps to 'notes' column)
experiment: title (required — use instead of 'name'), hypothesis, description, status (proposed|designed|active|completed|analyzed|abandoned), success_metrics, outcome_notes, value_prop_id, channel_id
competitor: name, description, url, positioning, strengths, weaknesses, pricing_model
contact: name, email, phone, company, role, source, url, notes Extra fields (any field not in the schema above) are stored in extensions. After adding entities, pause and confirm with the user before adding more. Pass
projectto override.cantrip.json— useful in cloud-hosted or multi-project contexts.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| entity_type | Yes | Entity type: icp, pain_point, value_prop, experiment, channel, competitor, contact | |
| name | No | Entity name (mapped to 'framing' for value_prop, 'title' for experiment) | |
| description | No | Entity description | |
| fields | No | Additional fields as key-value pairs (e.g. {severity: 'high', frequency: 'constant'}) | |
| project | No | Project slug — overrides .cantrip.json. Required in environments where cantrip_connect cannot write to the filesystem. |