Reference
Preview the next 7 days
Forecast the next 7 days for accounts (accountIds / tags, or all): per day open hours, demand from campaigns, nurture and routines against the same daily limits as the gate, what overflows. An estimate; the gate still decides each action.
View MarkdownThis page is generated from the source code on every release.
Forecast the next 7 days for accounts (accountIds / tags, or all): per day open hours, demand from campaigns, nurture and routines against the same daily limits as the gate, what overflows. An estimate; the gate still decides each action.
Overview
| Name | Value |
|---|---|
| Code | automation.simulate |
| New code (v2) | automations.simulate |
| Scope needed | accounts.read |
| Risk | Read |
| May need confirmation | No |
| Runs as | Answers right away |
Needs Idempotency-Key |
No |
| Member roles allowed | owner, manager, viewer |
| In the app | Automation → 7-day preview |
Input fields
| Field | Type | Required | Description |
|---|---|---|---|
accountIds |
uuid[] |
No | |
tags |
text[] |
No |
Example request
curl -X POST https://tlg.builera.app/api/public/v2/ops/automation.simulate \
-H "Authorization: Bearer $TELEGRAM_AUTO_API_KEY" \
-H "Content-Type: application/json" \
-d '{}'Output fields (data)
The answer has no fixed fields.
Example answer
{
"data": "text"
}Using it over MCP
Not listed on any profile: call tools_describe then tools_run with code: "automation.simulate". Tool name when listed: automation_simulate.