Reference
Turn nurturing on / off for an account
Turn nurturing on or off for one account.
View MarkdownThis page is generated from the source code on every release.
Turn nurturing on or off for one account.
Overview
| Name | Value |
|---|---|
| Code | nurture.set_enabled |
| New code (v2) | nurture_plans.set_enabled |
| Scope needed | nurture.write |
| Risk | Write |
| May need confirmation | No |
| Runs as | Answers right away |
Needs Idempotency-Key |
No |
| Member roles allowed | owner, manager |
| In the app | Account nurture → account |
Input fields
| Field | Type | Required | Description |
|---|---|---|---|
accountId |
uuid |
Yes | |
enabled |
true/false |
Yes |
Example request
curl -X POST https://tlg.builera.app/api/public/v2/ops/nurture.set_enabled \
-H "Authorization: Bearer $TELEGRAM_AUTO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"accountId":"00000000-0000-0000-0000-000000000000","enabled":true}'Output fields (data)
| Field | Type | Required |
|---|---|---|
ok |
true |
Yes |
Example answer
{
"data": {
"ok": true
}
}Using it over MCP
Not listed on any profile: call tools_describe then tools_run with code: "nurture.set_enabled". Tool name when listed: nurture_set_enabled.