Automate SAP B1 Journal Entries via JSON, Sheets & GPT-4o

Automates SAP Business One journal entries from JSON, Google Sheets, or manual inputs using dynamic branching, LLM transformation, and Service Layer API. Logs transactions for traceability.

n8n
Automate SAP B1 Journal Entries via JSON, Sheets & GPT-4o

This workflow streamlines the creation of Journal Entries in SAP Business One (SAP B1) by accepting inputs from multiple sources: JSON payloads, Google Sheets data, or manual structured entries via LLM prompts. It begins with a webhook receiving POST requests containing data and SAP credentials, followed by secure login to retrieve a session cookie. A switch node then branches based on the 'origen' field to handle each input type appropriately.

For JSON inputs, it restructures and sends directly to SAP. Google Sheets data is loaded, merged with context, and transformed via OpenAI GPT-4o into SAP-compatible JSON. Manual entries use LLM prompts to parse and format lines into JournalEntryLines arrays, ensuring clean JSON output without extras. All paths culminate in a POST to the SAP Service Layer /JournalEntries endpoint, with transactions logged to Google Sheets for audit trails.

Benefits include reduced manual data entry errors, flexible multi-source integration, and time savings for accounting teams. Use cases span finance automation, reconciling sheet-based records with ERP, or ad-hoc journal creation via chat-like inputs, ideal for SMBs leveraging SAP B1.

$24.99
Last updated October 10, 2026
30-day money-back guarantee
Instant download
Lifetime updates included

New buyers can create an account from the cart to unlock a controlled $10 first-purchase credit on eligible orders of $25+.

Secure checkout powered by Stripe

Support

How to import this workflow into n8n

  1. 1Purchase or download the workflow to get the n8n workflow JSON file.
  2. 2In your n8n instance, open Workflows and choose "Import from File" (or paste the JSON with Ctrl+V on the canvas).
  3. 3Open each node marked with a credential warning and connect your own accounts and API keys.
  4. 4Run the workflow once manually to verify the data flow, then toggle it to Active.

Related Human Resources workflows

More from Tobias Zielinski

Need this deployed? We'll set it up for you.

Our automation experts deploy this workflow in your stack, connect your accounts, and verify it works — or build a custom solution from scratch.