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

# DefensX

> Connect DefensX to Triggr with a DefensX Partner API token.

Triggr lists and creates DefensX customers, lists policy and message templates, and lists a customer's agents. You need an admin login to your DefensX partner dashboard, such as a Global Partner Admin.

## Set up DefensX

**1. Create an API key**

Open the API Keys page and create a key for Triggr. If you restrict it to IP addresses, add both of [Triggr's IP addresses](https://kb.mspprocess.com/security/ip-allowlist.md).

**2. Generate a token**

Generate a token for the key and copy it.

See DefensX's [Using Partner API](https://kb.defensx.com/docs/categories/72-Partner-API/topics/91d5908c-ee58-4e51-8397-ba6823407ff8) guide.

## Connect it in Triggr

**1. Open the integration**

Go to **Integrations > DefensX** and click **Configure** on the Base Configuration card.

![The Base Configuration card with Status Not Configured, Admin Consent Not Required and a Configure button.](https://mintcdn.com/triggr/nyuVXZ1rouDTTEvu/images/integrations-common/base-configuration.png?fit=max\&auto=format\&n=nyuVXZ1rouDTTEvu\&q=85\&s=bb81acb082055015f91beda7b4876f35)

**2. Paste the token**

Paste it into API Token, without `Bearer` in front, and click **Save Configuration**.

![The DefensX configuration window with an API Token field and hint, an Allow insecure TLS switch under Advanced, and a Save Configuration button.](https://mintcdn.com/triggr/nyuVXZ1rouDTTEvu/images/defensx/configure.png?fit=max\&auto=format\&n=nyuVXZ1rouDTTEvu\&q=85\&s=bd24034fbdd6d4f036e3259a2fac0ffb)

One configuration covers every customer, with no client mapping. Actions on one customer take its `customerId` from List Customers. Create Customer takes DefensX's JSON body in `jsonBody`; add `policy_template_id` or `message_template_id` from List Policy Templates or List Message Templates. The Documentation button on the API Keys page lists the fields.

## Troubleshooting

> [accordion] Every action is refused
>
> Check API Token holds the full token without `Bearer`, the key still exists, and any IP restriction includes both of Triggr's addresses.

> [accordion] Create Customer is refused
>
> Check the body against DefensX's API documentation, and that template IDs come from your own account.

> [accordion] Large workflows are refused part-way through
>
> DefensX rate-limits the Partner API. Run large workflows in smaller batches.


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