Short answer: Drop the "Zoho Books → Create Expense" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Organization ID organization_id | string | Required | Organization ID. Example: 10234695 |
Expense Account ID account_id | string | Required | Expense Account ID. Example: 460000000000400 |
Paid Through Account ID paid_through_account_id | string | Required | Paid Through Account ID. Example: 460000000000361 |
Amount amount | string | Required | Amount. Example: 250.00 |
Date date | string | Required | Date. e.g. "YYYY-MM-DD" |
Description description | string | Optional | Description. Example: Office supplies purchase |
Vendor ID vendor_id | string | Optional | Vendor ID. Example: 460000000030001 |
Billable is_billable | options | Optional | Billable. Options: No, Yes |
{"organization_id": "e.g. 10234695","account_id": "e.g. 460000000000400","paid_through_account_id": "e.g. 460000000000361","amount": "e.g. 250.00","date": "YYYY-MM-DD"}
{"code": 0,"expense": {"date": "2025-01-15","amount": 250,"expense_id": "460000000035001"},"message": "The expense has been created."}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.