The daily‑briefing workflow (projects/n8n/05_daily-briefing) includes an inline button labelled 📊 Expenses with callback data briefing:expenses. The callback is handled by the menu‑handler in project 10 (projects/n8n/10_steward/workflows/menu‑handler.json).
In the handler the callback data is split on : and the second part (expenses) is used as the action key. The agents registry in the Config node expects an expenses entry with a valid workflowId (currently a placeholder YOUR_EXPENSE_REPORT_WORKFLOW_ID). Because this placeholder is not replaced with the real workflow ID, the Normalize node resolves workflowId as an empty string and the button does nothing.
Additional observations:
- The
Whitelist node is disabled, so any user can trigger the handler – that may be intentional but worth confirming.
- Ensure the Telegram credentials (
CREDENTIAL_ID_TELEGRAM) are correct and the bot has permission to send callback responses.
Suggested fix:
- Locate the expense‑report workflow ID (you can find it in the n8n UI or via the workflow URL).
- Edit
projects/n8n/10_steward/workflows/menu‑handler.json → Config node → replace the placeholder value for agents.expenses.workflowId with the real ID.
- (Optional) Enable the
Whitelist node if you want to restrict button usage to specific chat IDs.
- Commit the change and redeploy/re‑activate the workflow.
After updating the workflow ID the 📊 Expenses button should trigger the expense‑report workflow as expected.
The daily‑briefing workflow (projects/n8n/05_daily-briefing) includes an inline button labelled 📊 Expenses with callback data
briefing:expenses. The callback is handled by the menu‑handler in project 10 (projects/n8n/10_steward/workflows/menu‑handler.json).In the handler the callback data is split on
:and the second part (expenses) is used as the action key. Theagentsregistry in theConfignode expects anexpensesentry with a validworkflowId(currently a placeholderYOUR_EXPENSE_REPORT_WORKFLOW_ID). Because this placeholder is not replaced with the real workflow ID, theNormalizenode resolvesworkflowIdas an empty string and the button does nothing.Additional observations:
Whitelistnode is disabled, so any user can trigger the handler – that may be intentional but worth confirming.CREDENTIAL_ID_TELEGRAM) are correct and the bot has permission to send callback responses.Suggested fix:
projects/n8n/10_steward/workflows/menu‑handler.json→Confignode → replace the placeholder value foragents.expenses.workflowIdwith the real ID.Whitelistnode if you want to restrict button usage to specific chat IDs.After updating the workflow ID the 📊 Expenses button should trigger the expense‑report workflow as expected.