See llms.txt for all machine-readable content.
Save yourself the work of writing custom integrations for Lighthouse and Microsoft SQL and use n8n instead. Build adaptable and scalable Development, workflows that work with your technology stack. All within a building experience you will love.

| Delete | |
|---|---|
| Get | |
| Head | |
| Options | |
| Patch | |
| Post | |
| Put |
To set up Lighthouse 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 Lighthouse to query the data you need using the API endpoint URLs you provide.
See the example hereRequires additional credentials set up
Use n8n's HTTP Request node with a predefined or generic credential type to make custom API calls.
| Execute Query | Execute an SQL query |
|---|---|
| Insert | Insert rows in database |
| Update | Update rows in database |
| Delete | Delete rows in database |
Discover our latest community's recommendations and join the discussions about Lighthouse and Microsoft SQL integration.

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…

