Automating SAP B1 journal entries using JSON, Google Sheets, and GPT-4o
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 21 nodes and runs when an HTTP GET request hits its webhook URL. Along the way it connects Google Sheets and OpenAI.
How it runs
Trigger: When an HTTP GET request hits its webhook URL.
- SAP Login (HTTP Request): calls an HTTP API
- Route by Source (Switch): routes items into branches
- Map JSON Fields (Edit Fields (Set)): sets or maps fields
- Set SAP Data (Edit Fields (Set)): sets or maps fields
- LLM Transform (Manual) (OpenAI): uses OpenAI
- Post Journal (JSON) (HTTP Request): calls an HTTP API
- Load Sheet Data (Google Sheets): uses Google Sheets
- Merge: merges the data from its input branches
- Post Journal (Manual) (HTTP Request): calls an HTTP API
- Log Success (JSON) (Google Sheets): uses Google Sheets
…plus 10 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- Webhook
n8n-nodes-base.webhook - HTTP Request
n8n-nodes-base.httpRequest - Switch
n8n-nodes-base.switch - Edit Fields (Set)
n8n-nodes-base.set - Google Sheets
n8n-nodes-base.googleSheets - OpenAI
@n8n/n8n-nodes-langchain.openAi - Code
n8n-nodes-base.code - Merge
n8n-nodes-base.merge
From the author
HOW IT WORKS: This workflow automates the creation of Journal Entries in SAP Business One (SAP B1). Depending on the source of the input data, it dynamically transforms and sends accounting records in the appropriate format using the Service Layer API. It…