Sync SAP Business One OData records with Google Sheets daily
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 workflow has 12 nodes and runs on a schedule (every 24 hours). Along the way it connects Google Sheets.
How it runs
Trigger: On a schedule (every 24 hours).
- Post SAP Login (HTTP Request): calls an HTTP API (POST)
- Fetch SAP Page 1 Records (HTTP Request): calls an HTTP API
- Fetch SAP Page 2 Records (HTTP Request): calls an HTTP API
- Parse Page 1 Records (Code): runs custom JavaScript code
- Parse Page 2 Records (Code): runs custom JavaScript code
- Merge: merges the data from its input branches
- Set Customer Data Fields (Edit Fields (Set)): sets 7 fields: Customer Code, Customer Name, Type…
- Check Valid Email (If): checks a condition and branches into true / false
- Upsert Customer to Sheets (Google Sheets): append or update
- Log Skips Without Email (Edit Fields (Set)): sets 3 fields: skipped_code, skipped_name, reason
…plus 1 more step. 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 (7)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code - Merge
n8n-nodes-base.merge - Edit Fields (Set)
n8n-nodes-base.set - If
n8n-nodes-base.if - Google Sheets
n8n-nodes-base.googleSheets
From the author
Quick overview This workflow runs daily to sync SAP Business One Service Layer OData Business Partners to Google Sheets, handling SAP’s 20-record page limit, mapping fields into a sheet-friendly format, filtering out records without email addresses, and…