Back to Integrations
HTTP Request
Recorded Future
integrationHTTP Request node
integrationRecorded Future node
HTTP Request

HTTP Request and Recorded Future integration

Save yourself the work of writing custom integrations for HTTP Request and Recorded Future and use n8n instead. Build adaptable and scalable Development, Core Nodes, and Cybersecurity workflows that work with your technology stack. All within a building experience you will love.

Get started
See n8n in action

How to connect HTTP Request and Recorded Future

  • Step 1: Create a new workflow
  • Step 2: Add and configure nodes
  • Step 3: Connect
  • Step 4: Customize and extend your integration
  • Step 5: Test and activate your workflow

Step 1: 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.

HTTP Request and Recorded Future integration: Create a new workflow and add the first step

Step 2: Add and configure HTTP Request and Recorded Future (using the HTTP Request node)

You can find HTTP Request and Recorded Future nodes in the nodes panel and drag them onto your workflow canvas. HTTP Request node comes with pre-built credentials and supported actions. Recorded Future can be set up with the HTTP Request node using a pre-configured credential type. The HTTP Request node makes custom API calls to Recorded Future. Configure HTTP Request and Recorded Future nodes one by one: input data on the left, parameters in the middle, and output data on the right.

HTTP Request and Recorded Future integration: Add and configure HTTP Request and Recorded Future nodes

Step 3: Connect HTTP Request and Recorded Future

A connection establishes a link between HTTP Request and Recorded Future (or vice versa) to route data through the workflow. Data flows from the output of one node to the input of another. You can have single or multiple connections for each node.

HTTP Request and Recorded Future integration: Connect HTTP Request and Recorded Future

Step 4: Customize and extend your HTTP Request and Recorded Future integration

Use n8n's core nodes such as If, Split Out, Merge, and others to transform and manipulate data. Write custom JavaScript or Python in the Code node and run it as a step in your workflow. Connect HTTP Request and Recorded Future with any of n8n’s 1000+ integrations, and incorporate advanced AI logic into your workflows.

HTTP Request and Recorded Future integration: Customize and extend your HTTP Request and Recorded Future integration

Step 5: Test and activate your HTTP Request and Recorded Future workflow

Save and run the workflow to see if everything works as expected. Based on your configuration, data should flow from HTTP Request to Recorded Future or vice versa. Easily debug your workflow: you can check past executions to isolate and fix the mistake. Once you've tested everything, make sure to save your workflow and activate it.

HTTP Request and Recorded Future integration: Test and activate your HTTP Request and Recorded Future workflow

Build your own HTTP Request and Recorded Future integration

Create custom HTTP Request and Recorded Future 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.

Supported API Endpoints for Recorded Future

  • Entities
  • Alerts
  • Intelligence
  • RiskLists
GetEntity
Retrieve details of a specific entity.
GET
/api/v2/entity/{entity_id}
SearchEntities
Search for entities based on criteria.
POST
/api/v2/entity/search
ListEntityTypes
List all entity types available.
GET
/api/v2/entity/types
GetEntityAssociations
Retrieve associations for a specific entity.
GET
/api/v2/entity/{entity_id}/associations
GetEntityRiskScore
Retrieve risk score for a specific entity.
GET
/api/v2/entity/{entity_id}/risk

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.

See the example here

Take a look at the Recorded Future official documentation to get a full list of all API endpoints

GetAlerts
Retrieve a list of alerts.
GET
/api/v2/alert
GetAlertDetails
Retrieve details of a specific alert.
GET
/api/v2/alert/{alert_id}
CreateAlert
Create a new alert.
POST
/api/v2/alert
UpdateAlert
Update an existing alert.
PUT
/api/v2/alert/{alert_id}
DeleteAlert
Delete a specific alert.
DELETE
/api/v2/alert/{alert_id}

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.

See the example here

Take a look at the Recorded Future official documentation to get a full list of all API endpoints

GetIntelligence
Retrieve intelligence for a specific query.
GET
/api/v2/intelligence
SearchIntelligence
Search for intelligence data.
POST
/api/v2/intelligence/search
GetIntelligenceTrending
Retrieve trending intelligence data.
GET
/api/v2/intelligence/trending
GetIntelligenceByCategory
Retrieve intelligence data by category.
GET
/api/v2/intelligence/category/{category_id}
GetIntelligenceSummary
Retrieve summary of intelligence data.
GET
/api/v2/intelligence/summary

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.

See the example here

Take a look at the Recorded Future official documentation to get a full list of all API endpoints

GetRiskLists
Retrieve a list of risk lists.
GET
/api/v2/risklist
GetRiskListDetails
Retrieve details of a specific risk list.
GET
/api/v2/risklist/{risklist_id}
CreateRiskList
Create a new risk list.
POST
/api/v2/risklist
UpdateRiskList
Update an existing risk list.
PUT
/api/v2/risklist/{risklist_id}
DeleteRiskList
Delete a specific risk list.
DELETE
/api/v2/risklist/{risklist_id}

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.

See the example here

Take a look at the Recorded Future official documentation to get a full list of all API endpoints

HTTP Request and Recorded Future integration details

integrationHTTP Request node
HTTP Request
integrationRecorded Future node
HTTP Request
Recorded Future

Recorded Future is a threat intelligence platform that collects and analyzes vast amounts of data from the internet to provide actionable insights on cyber threats. Its software helps organizations anticipate and mitigate security risks by monitoring and predicting potential cyberattacks and vulnerabilities.

Use case

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
Use case

The SOAR platform you want

Mountains of monotonous tasks make building and monitoring your workflows a chore. Not anymore.

Learn more

FAQs

  • Can HTTP Request connect with Recorded Future?

  • Can I use HTTP Request’s API with n8n?

  • Can I use Recorded Future’s API with n8n?

  • Is n8n secure for integrating HTTP Request and Recorded Future?

  • How to get started with HTTP Request and Recorded Future integration in n8n.io?

Looking to integrate HTTP Request and Recorded Future in your company?

Contact Sales

Over 3000 companies switch to n8n every single week

Why use n8n to integrate HTTP Request with Recorded Future

Build complex workflows, really fast

Build complex workflows, really fast

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

Code when you need it, UI when you don't

Simple debugging

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

Use templates to get started fast

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

Reuse your work

Copy and paste, easily import and export workflows.

Implement complex processes faster with n8n

Get started
red iconyellow iconred iconyellow icon

Automate without limits

Made with ♥ in Berlin
Impressum | Legal | Privacy

Report a vulnerability
© 2024 n8n | All rights reserved.