See llms.txt for all machine-readable content.
Save yourself the work of writing custom integrations for Microsoft SQL and Recorded Future 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.

| Execute Query | Execute an SQL query |
|---|---|
| Insert | Insert rows in database |
| Update | Update rows in database |
| Delete | Delete rows in database |
To set up Recorded Future integration, add the HTTP Request node to your workflow canvas and authenticate it using a predefined credential type. This allows you to perform custom operations, without additional authentication setup. The HTTP Request node makes custom API calls to Recorded Future to query the data you need using the URLs you provide.
Take a look at the Recorded Future official documentation to get a full list of all API endpoints
Discover our latest community's recommendations and join the discussions about Microsoft SQL and Recorded Future 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…

