# happ_crm_call_trigger_create

Создаёт триггер: при событии CRM (стадия лида/сделки) номер клиента попадает в очередь обзвона, и голосовой ассистент звонит. Нужна подключённая CRM и очередь обзвона (лучше бесконечная, isContinuous). Стадию и пути полей бери из happ_crm_call_trigger_setup; если matchPath/phonePath/variableMappings не переданы — подставятся из setup автоматически. (POST /crm-call-triggers)

Agent View of the PolicyLayer registry record for `happ_crm_call_trigger_create`. HTML page: https://policylayer.com/tools/happ-ai-platform-mcp/happ-crm-call-trigger-create

## Facts

- Tool: `happ_crm_call_trigger_create`
- Server: Platform (`@happ-ai/platform-mcp`) — https://policylayer.com/tools/happ-ai-platform-mcp.md
- Install: `npx -y @happ-ai/platform-mcp`
- Homepage: https://www.npmjs.com/package/@happ-ai/platform-mcp
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 11 (4 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `name` | string | yes | Название триггера, например «Новый лид → перезвонить» |
| `queueId` | string | yes | Очередь обзвона, в которую попадут номера (владеет расписанием и лимитами) |
| `isActive` | boolean | no | Сразу включить (по умолчанию да) |
| `companyId` | string | yes | ID компании |
| `dedupDays` | integer | no | Не звонить тому же номеру повторно N дней |
| `matchPath` | string | no | Путь к стадии в событии (guide.stagePath); по умолчанию из setup |
| `phonePath` | string | no | Путь к телефону клиента (guide.phonePath); по умолчанию из setup |
| `matchValue` | string | no | Стадия/значение, при котором звонить (stage.value из setup); пусто = любое событие |
| `templateId` | string | no | Готовый сценарий — тогда стадия и переменные подберутся сами |
| `variableMappings` | array | no | Какие поля события подставлять в промпт как {{переменные}}; по умолчанию все поля из setup |
| `companyIntegrationId` | string | yes | ID подключённой CRM |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "happ_crm_call_trigger_create",
    "arguments": {
      "name": "<name>",
      "queueId": "<queueId>",
      "companyId": "<companyId>",
      "companyIntegrationId": "<companyIntegrationId>"
    }
  }
}
```

## Why happ_crm_call_trigger_create is rated High

happ_crm_call_trigger_create triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signals: Accepts file system path (variableMappings[].path) · High parameter count (13 properties)

## Use case

AI agents invoke happ_crm_call_trigger_create to trigger actions in Platform. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Platform:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "happ_crm_call_trigger_create": {
      "limits": [
        {
          "counter": "happ_crm_call_trigger_create_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Platform (274)

- `happ_access_token_revoke` — Destructive — https://policylayer.com/tools/happ-ai-platform-mcp/happ-access-token-revoke.md
- `happ_assistant_delete` — Destructive — https://policylayer.com/tools/happ-ai-platform-mcp/happ-assistant-delete.md
- `happ_assistant_integration_unbind` — Destructive — https://policylayer.com/tools/happ-ai-platform-mcp/happ-assistant-integration-unbind.md
- `happ_call_queue_cancel` — Destructive — https://policylayer.com/tools/happ-ai-platform-mcp/happ-call-queue-cancel.md
- `happ_call_queue_delete` — Destructive — https://policylayer.com/tools/happ-ai-platform-mcp/happ-call-queue-delete.md
- `happ_call_reply_delete` — Destructive — https://policylayer.com/tools/happ-ai-platform-mcp/happ-call-reply-delete.md
- `happ_chat_delete` — Destructive — https://policylayer.com/tools/happ-ai-platform-mcp/happ-chat-delete.md
- `happ_company_delete` — Destructive — https://policylayer.com/tools/happ-ai-platform-mcp/happ-company-delete.md
- `happ_company_leave` — Destructive — https://policylayer.com/tools/happ-ai-platform-mcp/happ-company-leave.md
- `happ_company_remove_user` — Destructive — https://policylayer.com/tools/happ-ai-platform-mcp/happ-company-remove-user.md
- `happ_crm_pull_source_delete` — Destructive — https://policylayer.com/tools/happ-ai-platform-mcp/happ-crm-pull-source-delete.md
- `happ_folder_delete` — Destructive — https://policylayer.com/tools/happ-ai-platform-mcp/happ-folder-delete.md
- `happ_integration_delete` — Destructive — https://policylayer.com/tools/happ-ai-platform-mcp/happ-integration-delete.md
- `happ_invitation_revoke` — Destructive — https://policylayer.com/tools/happ-ai-platform-mcp/happ-invitation-revoke.md
- `happ_knowledge_delete` — Destructive — https://policylayer.com/tools/happ-ai-platform-mcp/happ-knowledge-delete.md
- `happ_message_style_delete` — Destructive — https://policylayer.com/tools/happ-ai-platform-mcp/happ-message-style-delete.md
- `happ_notification_channel_mute` — Destructive — https://policylayer.com/tools/happ-ai-platform-mcp/happ-notification-channel-mute.md
- `happ_phone_delete` — Destructive — https://policylayer.com/tools/happ-ai-platform-mcp/happ-phone-delete.md
- `happ_playground_reset` — Destructive — https://policylayer.com/tools/happ-ai-platform-mcp/happ-playground-reset.md
- `happ_quick_reply_delete` — Destructive — https://policylayer.com/tools/happ-ai-platform-mcp/happ-quick-reply-delete.md
- `happ_report_cancel` — Destructive — https://policylayer.com/tools/happ-ai-platform-mcp/happ-report-cancel.md
- `happ_sheets_pull_source_delete` — Destructive — https://policylayer.com/tools/happ-ai-platform-mcp/happ-sheets-pull-source-delete.md
- `happ_test_case_delete` — Destructive — https://policylayer.com/tools/happ-ai-platform-mcp/happ-test-case-delete.md
- `happ_text_campaign_cancel` — Destructive — https://policylayer.com/tools/happ-ai-platform-mcp/happ-text-campaign-cancel.md
- `happ_tool_delete` — Destructive — https://policylayer.com/tools/happ-ai-platform-mcp/happ-tool-delete.md
- `happ_analysis_run` — Execute — https://policylayer.com/tools/happ-ai-platform-mcp/happ-analysis-run.md
- `happ_call_queue_start` — Execute — https://policylayer.com/tools/happ-ai-platform-mcp/happ-call-queue-start.md
- `happ_crm_call_trigger_delete` — Execute — https://policylayer.com/tools/happ-ai-platform-mcp/happ-crm-call-trigger-delete.md
- `happ_crm_call_trigger_setup` — Execute — https://policylayer.com/tools/happ-ai-platform-mcp/happ-crm-call-trigger-setup.md
- `happ_crm_call_trigger_update` — Execute — https://policylayer.com/tools/happ-ai-platform-mcp/happ-crm-call-trigger-update.md
- …and 244 more: https://policylayer.com/tools/happ-ai-platform-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=happ-ai-platform-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/happ-ai-platform-mcp