Reference
Today's nurture tasks
Today's planned nurture tasks per account.
View MarkdownThis page is generated from the source code on every release.
Today's planned nurture tasks per account.
Overview
| Name | Value |
|---|---|
| Code | nurture.today |
| New code (v2) | nurture_plans.today |
| Scope needed | accounts.read |
| Risk | Read |
| May need confirmation | No |
| Runs as | Answers right away |
Needs Idempotency-Key |
No |
| Member roles allowed | owner, manager, agent, viewer |
| In the app | Account nurture → Today |
Input fields
This operation takes no fields.
Example request
curl -X POST https://tlg.builera.app/api/public/v2/ops/nurture.today \
-H "Authorization: Bearer $TELEGRAM_AUTO_API_KEY" \
-H "Content-Type: application/json" \
-d '{}'Output fields (data)
| Field | Type | Required |
|---|---|---|
jobs |
object[] |
Yes |
generatedAt |
text |
Yes |
Example answer
{
"data": {
"jobs": [
{
"id": "00000000-0000-4000-8000-000000000000",
"accountId": "00000000-0000-4000-8000-000000000000",
"action": "join",
"status": "held",
"at": "text",
"channel": "text",
"reason": "text",
"react": true
}
],
"generatedAt": "2026-10-22T12:00:00.000Z"
}
}Using it over MCP
Not listed on any profile: call tools_describe then tools_run with code: "nurture.today". Tool name when listed: nurture_today.