Back to Integrations
integrationRecorded Future node
HTTP Request
integrationSpike node
HTTP Request

Recorded Future and Spike integration

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

How to connect Recorded Future and Spike

  • 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.

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

Step 2: Add and configure Recorded Future and Spike nodes using the HTTP Request nodes

You can find the Recorded Future node in the nodes panel and drag it onto your workflow canvas. It will be added as the HTTP Request node with a pre-configured credential type. To add the Spike app to the workflow, select the HTTP Request node and use a generic authentication method. The HTTP Request node makes custom API calls to Recorded Future and Spike. Configure Recorded Future and Spike nodes one by one: input data on the left, parameters in the middle, and output data on the right.

Recorded Future and Spike integration: Add and configure Recorded Future and Spike nodes using the HTTP Request node

Step 3: Connect Recorded Future and Spike

A connection establishes a link between Recorded Future and Spike (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.

Recorded Future and Spike integration: Connect Recorded Future and Spike

Step 4: Customize and extend your Recorded Future and Spike 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 Recorded Future and Spike with any of n8n’s 1000+ integrations, and incorporate advanced AI logic into your workflows.

Recorded Future and Spike integration: Customize and extend your Recorded Future and Spike integration

Step 5: Test and activate your Recorded Future and Spike workflow

Save and run the workflow to see if everything works as expected. Based on your configuration, data should flow from Recorded Future and Spike 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.

Recorded Future and Spike integration: Test and activate your Recorded Future and Spike workflow

Build your own Recorded Future and Spike integration

Create custom Recorded Future and Spike 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

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

Supported methods for Spike

Delete
Get
Head
Options
Patch
Post
Put

Requires additional credentials set up

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

FAQs

  • Can Recorded Future connect with Spike?

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

  • Can I use Spike’s API with n8n?

  • Is n8n secure for integrating Recorded Future and Spike?

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

Looking to integrate Recorded Future and Spike in your company?

Over 3000 companies switch to n8n every single week

Why use n8n to integrate Recorded Future with Spike

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

red iconyellow iconred iconyellow icon