happ_crm_call_trigger_setup
Что можно настроить для подключённой CRM: готовые сценарии (новый лид → перезвонить, заказ в работе → подтвердить, сделка успешна → отзыв, отказ → вернуть) с уже подобранной стадией из воронок этой CRM, список всех стадий, путь к телефону и переменные для промпта. Вызывай перед созданием триггера...
This record as markdown: /tools/happ-ai-platform-mcp/happ-crm-call-trigger-setup.md
What happ_crm_call_trigger_setup does on Platform
AI agents invoke happ_crm_call_trigger_setup 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
companyIntegrationId | string | Yes | ID подключённой CRM (из happ_integrations_list) |
Parameters from the server's own tool schema.
Why happ_crm_call_trigger_setup is rated High
happ_crm_call_trigger_setup 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.
Attacks that exploit this kind of access
The rule that runs happ_crm_call_trigger_setup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Platform, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For happ_crm_call_trigger_setup, this is the rule to start with:
happ_crm_call_trigger_setup stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Platform, apply this rule, and every happ_crm_call_trigger_setup call is checked against it from then on.
Questions about happ_crm_call_trigger_setup
Что можно настроить для подключённой CRM: готовые сценарии (новый лид → перезвонить, заказ в работе → подтвердить, сделка успешна → отзыв, отказ → вернуть) с уже подобранной стадией из воронок этой CRM, список всех стадий, путь к телефону и переменные для промпта. Вызывай перед созданием триггера; из ответа бери stage.value → matchValue, guide.stagePath → matchPath, guide.phonePath → phonePath. (GET /crm-call-triggers/setup/:companyIntegrationId). It is categorised as a Execute tool in the Platform MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
happ_crm_call_trigger_setup accepts 1 parameter: companyIntegrationId. Required: companyIntegrationId. The full parameter table on this page comes from the server's own tool schema.
Register the Platform MCP server in PolicyLayer and add a rule for happ_crm_call_trigger_setup: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Platform. Nothing to install.
happ_crm_call_trigger_setup is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the happ_crm_call_trigger_setup rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for happ_crm_call_trigger_setup. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
happ_crm_call_trigger_setup is provided by the Platform MCP server (@happ-ai/platform-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Platform, and thousands of servers like it.
Across the catalogue