Step 2: Connect Google Sheets

All finance entries are appended to the Budgets and Expenses sheets in the Finances spreadsheet.

1. Open Append Budget Sheet Row and set Document to [YOUR_ID] and Sheet to Budgets.
2. Map the column values in Append Budget Sheet Row to expressions like {{$json.output.Month}}, {{$json.output['Budget Amount']}}, and {{$json.output.UpdatedAt}}.
3. Credential Required: Connect your googleSheetsOAuth2Api credentials in Append Budget Sheet Row (not configured in the template).
4. Open Append Expense Sheet Row and confirm the Document is [YOUR_ID] and Sheet is Expenses.
5. Ensure Append Expense Sheet Row maps fields like {{$json.output.Amount}}, {{$json.output.Category}}, and {{$json.output.MessageId}}.
6. Credential Required: Connect your googleSheetsOAuth2Api credentials in Append Expense Sheet Row, Append Credit Expense Row, and Append Debit Expense Row.

Step 3: Set Up the AI Parsing Chain

The workflow uses multiple Gemini chat engines and structured parsers to interpret budgets and expenses from Telegram and Gmail inputs.

1. Open Gemini Chat Engine A and add your Gemini credentials for use by Telegram Message Parser.
2. Credential Required: Connect your googlePalmApi credentials in Gemini Chat Engine A (not configured in the template).
3. Confirm Telegram Message Parser uses Text set to {{$json.message.text}} and its system message includes the required JSON-only output rules.
4. Verify Budget Detail Extractor and Expense Detail Extractor use Text set to {{$json.text}} and Prompt Type set to define.
5. Ensure Gemini Chat Engine B and Gemini Chat Engine C are connected as the language models for Budget Detail Extractor and Expense Detail Extractor respectively.
6. Credential Required: Gemini Chat Engine B and Gemini Chat Engine C must use googlePalmApi credentials (already configured).
7. For the structured parsers, keep Expense Schema Parser and Budget Schema Parser schemas as provided. Credentials for these parsers must be added to their parent nodes (Budget Detail Extractor and Expense Detail Extractor), not the sub-nodes.
8. Confirm LLM Email Structuring uses Text set to {{$json.snippet}} and is connected to Gemini Chat Engine D, which already has googlePalmApi credentials configured.
9. Confirm Parse Email Details uses Text set to {{$json.text}} and is connected to Gemini Chat Engine E with googlePalmApi credentials configured.

Step 4: Configure Filtering and Routing Logic

Routing nodes determine whether the input is a budget or expense and where expense entries should be stored.

1. In Filter Finance Email Sources, keep the existing JavaScript to whitelist finance email senders and identify the account value.
2. Confirm Initial Budget vs Expense Check uses the condition {{ JSON.parse($json.text.replace(/```json\n?|```/g, '').trim()).type }} equals budget.
3. Ensure Final Budget vs Expense Gate checks {{$json.output.type}} equals budget before writing to the budgets sheet.
4. Verify Credit vs Debit Branch checks {{$json.output.type}} equals Credit to route to Append Credit Expense Row; the false branch routes to Append Debit Expense Row.

Step 5: Configure Output Notifications

After a row is appended, the workflow sends a Telegram confirmation to the originating user.

1. Open Send Telegram Confirmation and confirm Chat ID is set to {{$('Telegram Intake Trigger').item.json.message.from.id}}.
2. Update the confirmation Text message if needed, keeping the spreadsheet URL updated: https://docs.google.com/spreadsheets/d/[YOUR_ID]/edit?usp=sharing.
3. Credential Required: Connect your telegramApi credentials in Send Telegram Confirmation (already configured).

Step 6: Test and Activate Your Workflow

Run end-to-end tests from both Telegram and Gmail to validate routing and sheet updates.

1. Click Execute Workflow and send a Telegram message like “Set budget for groceries 5000” to trigger Telegram Intake Trigger.
2. Verify a new row appears in the Budgets sheet via Append Budget Sheet Row and a Telegram response is sent by Send Telegram Confirmation.
3. Send a test bank alert email to the Gmail inbox used by Gmail Intake Trigger and confirm Filter Finance Email Sources passes it through.
4. Check that the entry is routed through Credit vs Debit Branch and appended by either Append Credit Expense Row or Append Debit Expense Row.
5. Once verified, switch the workflow to Active for production use.