# site\_page\_nudge\_set Source: Locale: ru releaseGitSha: 45cdd4e19c6d3956d1bfa48c79fcb8dfec11fa9e sourceContentDigest: 3d469996d18593503ad66f88b9ef6cddd4757ce08c17262136ef31218f003a6c Version: 1 # 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](https://telegafirst.com/docs/schema-23bedcfc8b58d6f1fcb5fc832e59f082bb7f5041afcc4c3110025c041cd02af7) ## Результат null