Для AI-агентов: markdown этой страницы — /docs/mcp-tool-site-page-nudge-set.mdиндекс документации — /llms.txt
site_page_nudge_set
Обновлено
Replace the nudge setting of one published, visible site page (`seq_num` from `site_list_pages`); the whole setting, not a patch. When a person opens the page as a mini app and reaches no goal within `delayMinutes` (5 to 10080, seven days), the business sends them the funnel step `stepSeq` (a step `seq_num`, or null for none) and then, when `aiEnabled`, the AI Manager works on `aiPrompt` (1 to 2000 characters; the task for the AI, not a message to the person). One wait per person at a time: a second open of the page restarts the timer; another page replaces the wait only when its nudge is on with a step or AI and the person is not in the 30-day cooldown of that page. After a nudge the same person gets none on that page for 30 days. A goal ends the wait: any form submission of the person, any order, event registration or booking, and a tap on a goal link (`goalLinkCodes`: codes of links the business owns, bare or `dl_…`, at most 50) set on any page of the business. A running wait uses the setting as it was when it started; but if the nudge is off or the page hidden or unpublished when the timer fires, the wait is cancelled (`superseded`, nothing sent). A live dialog does not block the step; the AI stays silent while an operator holds the chat and is skipped without tokens. `aiEnabled` needs a plan with the AI Manager. Refusals: SITE_NUDGE_PAGE_NOT_ELIGIBLE, SITE_NUDGE_DELAY_OUT_OF_RANGE, SITE_NUDGE_STEP_NOT_FOUND, SITE_NUDGE_GOAL_LINK_NOT_FOUND, SITE_NUDGE_AI_NOT_ON_PLAN, SITE_NUDGE_AI_PROMPT_REQUIRED. Stop with `isEnabled: false`: pending waits are cancelled when their timer fires.
Права и условия
required_scopes: ALL.
| Поле | Значение |
|---|---|
| description | "Replace the nudge setting of one published, visible site page (`seq_num` from `site_list_pages`); the whole setting, not a patch. When a person opens the page as a mini app and reaches no goal within `delayMinutes` (5 to 10080, seven days), the business sends them the funnel step `stepSeq` (a step `seq_num`, or null for none) and then, when `aiEnabled`, the AI Manager works on `aiPrompt` (1 to 2000 characters; the task for the AI, not a message to the person). One wait per person at a time: a second open of the page restarts the timer; another page replaces the wait only when its nudge is on with a step or AI and the person is not in the 30-day cooldown of that page. After a nudge the same person gets none on that page for 30 days. A goal ends the wait: any form submission of the person, any order, event registration or booking, and a tap on a goal link (`goalLinkCodes`: codes of links the business owns, bare or `dl_…`, at most 50) set on any page of the business. A running wait uses the setting as it was when it started; but if the nudge is off or the page hidden or unpublished when the timer fires, the wait is cancelled (`superseded`, nothing sent). A live dialog does not block the step; the AI stays silent while an operator holds the chat and is skipped without tokens. `aiEnabled` needs a plan with the AI Manager. Refusals: SITE_NUDGE_PAGE_NOT_ELIGIBLE, SITE_NUDGE_DELAY_OUT_OF_RANGE, SITE_NUDGE_STEP_NOT_FOUND, SITE_NUDGE_GOAL_LINK_NOT_FOUND, SITE_NUDGE_AI_NOT_ON_PLAN, SITE_NUDGE_AI_PROMPT_REQUIRED. Stop with `isEnabled: false`: pending waits are cancelled when their timer fires." |
| domain | "site" |
| name | "site_page_nudge_set" |
| platform_version | "1.0.24" |
| required_scopes | ["site:write"] |
| risk | "write" |
| scope | "site:write" |
| title | "Site Page Nudge Set" |
Входные параметры
site_page_nudge_set: inputSchema
Результат
null