See llms.txt for all machine-readable content.

Microsoft SQL and Totango integration

Save yourself the work of writing custom integrations for Microsoft SQL and Totango and use n8n instead. Build adaptable and scalable Development, Data & Storage, workflows that work with your technology stack. All within a building experience you will love.

How to connect Microsoft SQL and Totango

Create a new workflow and add the first step

In n8n, click the "Add workflow" button in the Workflows tab to create a new workflow. Add the starting point – a trigger on when your workflow should run: an app event, a schedule, a webhook call, another workflow, an AI chat, or a manual trigger. Sometimes, the HTTP Request node might already serve as your starting point.

Microsoft SQL and Totango integration: Create a new workflow and add the first step

Flexible currency rate uploads for SAP B1 with AI validation & multiple sources

This workflow automates currency rate uploads into SAP Business One via Service Layer, using flexible input sources such as JSON (API), SQL Server, Google Sheets, or manual values. It leverages logic branching, AI validation, and logging for complete control and traceability. ++⚙️ HOW IT WORKS:++ 🔹 1. Receive Data via Webhook The workflow listens on the endpoint /formulario-datos via HTTP POST. The request body should include: origen: one of JSON, SQL, GoogleSheets, or Manual Depending on the value, the flow branches accordingly. 🔹 2. Authenticate with SAP Business One A POST request is sent to SAP B1’s Login endpoint. A session cookie (B1SESSION) is retrieved and used in all subsequent API calls. 🔹 3. Switch by Origin The flow branches into four processing paths based on origen: JSON: The payload is normalized using OpenAI to extract an array of rates. Each rate is sent to SAP individually after parsing. SQL: The SQL query provided in the payload is executed on a connected Microsoft SQL Server. The results are checked by AI to validate the date format. If valid, rates are sent to SAP. GoogleSheets: Rates are pulled from a connected spreadsheet. Each entry is sent to SAP in sequence. Manual: Uses currency, rate, and rateDate directly from the webhook payload. Sends the result directly to SAP. 🔹 4. AI-Powered Enhancements (Optional but enabled) Normalize JSON: Uses OpenAI (LangChain node) to convert any messy structure into a uniform array under the key rate. Date Formatting: Another OpenAI call ensures RateDate is in yyyyMMdd format (required by SAP), converting from ISO, timestamp, or other formats. 🔹 5. Send to SAP Business One (Service Layer) All paths send a POST request to: /SBOBobService_SetCurrencyRate With a payload such as: { "Currency": "USD", "Rate": "0.92", "RateDate": "20250612" } 🔹 6. Log Results All success/failure results are appended to a Google Sheets log (LOGS_N8N) The log includes method, URL, sent payload, status code, and message. ++🛠 SETUP STEPS:++ 1️⃣ Create Required Credentials: Go to Credentials > + New Credential and configure: SAP Business One (Service Layer) Type: HTTP Request Auth or Token Base URL: https://<your-host>:50000/b1s/v1/ Provide Username, Password, and CompanyDB via variables or fields Google Sheets OAuth2 connection to a Google account with access Microsoft SQL Server SQL login credentials and host OpenAI API key with access to models like GPT-4o 2️⃣ Environment Variables (Recommended) Set these variables in n8n → Settings → Variables: SAP_URL=https://<host>:50000/b1s/v1/ SAP_USER=your_username SAP_PASSWORD=your_password SAP_COMPANY_DB=your_companyDB 3️⃣ Prepare Google Sheets Sheet 1: RATE (for charging the data) Columns: Currency, Rate, RateDate Sheet 2: LOGS_N8N (to save the logs, success or failed) Columns: workflow, method, url, json, status_code, message 4️⃣ Activate and Test Deploy the webhook and grab the URL. ++✅ BONUS++ Built-in AI assistance for input validation and structure Logs all results for compliance and audit Flexible integration paths: perfect for hybrid or transitional systems

Build your own Microsoft SQL and Totango integration

Create custom Microsoft SQL and Totango workflows by choosing triggers and actions. Nodes come with global operations and settings, as well as app-specific parameters that can be configured. You can also use the HTTP Request node to query data from any app or service with a REST API.

Microsoft SQL supported actions

Execute Query

Execute an SQL query

Insert

Insert rows in database

Update

Update rows in database

Delete

Delete rows in database

Supported methods for Totango

Delete
Get
Head
Options
Patch
Post
Put

To set up Totango integration, add the HTTP Request node to your workflow canvas and authenticate it using a generic authentication method. The HTTP Request node makes custom API calls to Totango to query the data you need using the API endpoint URLs you provide.

See the example here

Requires additional credentials set up

Use n8n's HTTP Request node with a predefined or generic credential type to make custom API calls.

Microsoft SQL and Totango integration details

Microsoft SQL

Microsoft SQL

SQL Server is database management system developed by Microsoft. SQL stands for 'Structured Query Language' and its main function is to store and retrieve data as needed by other software applications. It remains one of the most used databases in the world.

Totango

Totango

Totango is a customer success platform that helps businesses understand and manage their customers' interactions and experiences. By providing actionable insights and analytics, Totango enables companies to increase customer satisfaction and retention, ultimately driving growth and revenue.

Other integrations with Microsoft SQL and Totango

Save engineering resources

Reduce time spent on customer integrations, engineer faster POCs, keep your customer-specific functionality separate from product all without having to code.

Learn more

FAQ about Microsoft SQL integrations

Need help setting up your Microsoft SQL and Totango integration?

Discover our latest community's recommendations and join the discussions about Microsoft SQL and Totango integration.

  • Cathryn17

    Syntax error when inserting multiple rows using Microsoft SQL node with Azure Dedicated SQL pool

    Cathryn17

    Describe the problem/error/question When inserting multiple rows (items) into an Azure Dedicated SQL pool (on a regular Azure SQL Server), we receive a syntax error from the DB (“Parse error at line: 1, column: 73: Incor…

    Open topic

Looking to integrate Slack and VirusTotal in your company?

Trusted by teams building smarter workflows

Why

Why use n8n to integrate Microsoft SQL with Totango

Handle branching, merging and iteration easily. Pause your workflow to wait for external events.

Re-run single steps to test changes in no time. And pin your data to avoid generating trigger events every time you execute.

Your data is displayed alongside your settings, making edge cases easy to track down.

Use 1000+ workflow templates available from our core team and our community.

Copy and paste, easily import and export workflows.

Simple enough to 
understand + sophisticated 
enough to ship