How do I import "Execute an SQL query in Microsoft SQL" into n8n?

Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.

Which integrations does "Execute an SQL query in Microsoft SQL" use?

It uses: manual, microsoftSql. The flow diagram above shows how each service connects across the 2 nodes. Filter OpenRuna by integration to find related workflows and tools.

Can I import a sanitized export without credentials?

Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own manual and microsoftSql credentials in n8n after import.

What trigger type does "Execute an SQL query in Microsoft SQL" use?

Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.

Is "Execute an SQL query in Microsoft SQL" free to use?

OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for manual, microsoftSql.

← Workflows

Execute an SQL query in Microsoft SQL

2 nodes · manual, microsoftSql

Engine: n8n
Nodes: 2
Trigger: scheduled/triggered
Source file: 1234_Manual_Microsoftsql_Automation_Triggered.json

Workflow flow

IntegrationsManualMicrosoftSql

100%

TRIGGER

On clicking 'execute'

Manual

Microsoft SQL

MicrosoftSql

2 steps · flows top to bottom, branches left to right

Browse by integration

manual microsoftSql

Browse all integrations →

Download n8n JSON Download sanitized JSON Download flow graph

Import into n8n

Download the n8n JSON file (full or sanitized).
In n8n: Workflows → Import from file.
Open each node and reconnect credentials to your accounts.
Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

Execute an SQL query in Microsoft SQL is a free n8n workflow on OpenRuna — 2 nodes connecting manual, microsoftSql. Download the JSON, view the flow diagram, and import it into your n8n instance.

What this workflow does

"Execute an SQL query in Microsoft SQL" automates a manual-to-microsoftSql flow in n8n across 2 nodes. 2 nodes · manual, microsoftSql It starts from a scheduled/triggered trigger and routes data through every node in order. On OpenRuna you get the visual graph, the integration list, and a downloadable JSON ready to import into n8n. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

Benchmark it against your current manual integration to spot missing steps or redundant nodes.
Fork it to add error handling, retries, or a notification step without designing the 2-node flow from scratch.
Share it with your team as a documented reference for scheduled/triggered automations in the manual stack.
Study how data moves from manual to microsoftSql before building your own variant.

Example output

Imported into n8n, "Execute an SQL query in Microsoft SQL" exposes 2 configured nodes. Trigger type: scheduled/triggered. Integrations: manual, microsoftSql. Open each node after import to map credentials to your own manual and microsoftSql accounts. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Paste the exported JSON for "Execute an SQL query in Microsoft SQL" into Claude and ask it to explain each of the 2 nodes. Claude is good at suggesting credential mappings for manual, microsoftSql, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "Execute an SQL query in Microsoft SQL" to your accounts — which manual, microsoftSql credentials to create and which node parameters to change first.

Cursor

Open the downloaded JSON in Cursor and use Agent mode to refactor hard-coded URLs into env vars, or to generate tests for any Code nodes. Keep the OpenRuna flow diagram open so you do not break connection order across the 2 nodes.

Frequently asked questions

How do I import "Execute an SQL query in Microsoft SQL" into n8n?: Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "Execute an SQL query in Microsoft SQL" use?: It uses: manual, microsoftSql. The flow diagram above shows how each service connects across the 2 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?: Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own manual and microsoftSql credentials in n8n after import.
What trigger type does "Execute an SQL query in Microsoft SQL" use?: Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "Execute an SQL query in Microsoft SQL" free to use?: OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for manual, microsoftSql.