> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pulsedive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrate with FortiSOAR

> Use the FortiSOAR Pulsedive connector to enrich IPs and domains with Pulsedive risk data, and pull related indicator links into playbooks.

[FortiSOAR](https://www.fortinet.com/products/fortisoar) is Fortinet's security orchestration, automation, and response platform, used to automate enrichment, investigation, and response through playbooks.
The Pulsedive connector adds three Pulsedive actions to FortiSOAR's playbook library, so a playbook can look up an IP or domain's reputation, or pull an indicator's related links, without a custom API call.
The connector is authored by SpryIQ, a Fortinet partner, and isn't Fortinet-certified, so support runs through SpryIQ and the community rather than Fortinet's support channel.

## Prerequisites

Before you connect FortiSOAR to Pulsedive, make sure you have the account and access the connector needs, so installation and configuration go smoothly:

* A Pulsedive account and API key.
  Find your API key on your [Pulsedive account page](https://pulsedive.com/account).
* FortiSOAR version 5.0.0 or later, with outbound connectivity to port 443 and permission to install and configure connectors.

## Connecting FortiSOAR to Pulsedive

Follow these steps to install the Pulsedive connector and configure it with your API key, so its actions become available in your playbooks:

1. In FortiSOAR, go to **Content Hub**.
   Select the **Connector Store** tab and search for **Pulsedive**.

   Alternatively, install from an SSH session as root with `yum install cyops-connector-pulsedive`.
2. On the **Connectors** page, select the Pulsedive connector row and open the **Configurations** tab.
3. Enter details for the connector:

   | Field Name | Description |
   | - | - |
   | **Server URL** | Use `https://pulsedive.com` |
   | **API Key** | Your Pulsedive API key |
   | **Verify SSL** | Leave enabled unless your environment requires otherwise |
4. Save the configuration.

For the current connector version and full parameter reference, visit the [Pulsedive connector on GitHub](https://github.com/fortinet-fortisoar/connector-pulsedive).

## Available Actions

These actions cover indicator lookups and related-indicator pivoting, so a playbook can enrich a value or explore what's connected to it.

* **Get IP Reputation**: Retrieves threat intelligence and context for an IP address.
* **Get Domain Reputation**: Retrieves threat intelligence and context for a domain.
* **Get Links of Indicator**: Retrieves related indicators and their associations for any IOC.

Once you install it, the connector ships with a sample playbook for each action under **Automation** > **Playbooks**.
Clone these before editing because the sample collection is removed on connector upgrade or deletion.

## Verifying the Connection

Confirm that FortiSOAR can reach Pulsedive before you build the connector into a playbook.

1. Run one of the sample playbooks, such as **Get IP Reputation**, against a known indicator.
2. Confirm that Pulsedive data appears in the playbook's output.

## Using Pulsedive Data in FortiSOAR

Once configured, add any Pulsedive action as a playbook step, so its output feeds directly into your existing investigation and response workflows.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.