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

# Cove Data Protection

> Connect N-able Cove Data Protection to Triggr with a Cove API user and its token.

Triggr reads Cove device statistics, devices, customers and backup job records, and changes or removes devices. Cove deletes a removed device's backed-up data with it.

## Set up Cove

<Steps>
  <Step title="Add an API user">
    Sign in to the Cove Management Console as a SuperUser or Administrator, go to **Management > Users > API Users** and click Add API user.
  </Step>

  <Step title="Fill in the details">
    Set Customer to your top-level customer, usually your own company, so it contains every customer your workflows use, and note its name exactly. Enter a Requested login name such as `triggr` (Cove adds a suffix, such as `-ab12c34d`). Any Role can view devices and customers; to change or remove devices, choose one that can edit and delete them, such as Manager or SuperUser.
  </Step>

  <Step title="Copy the token">
    Click Save and continue, then Copy token to clipboard. Cove shows the token only once. Note the full login name, including the suffix.
  </Step>
</Steps>

See N-able's guide to [adding users](https://documentation.n-able.com/covedataprotection/USERGUIDE/documentation/Content/service-management/console-new/user-management/add-user.htm).

## Connect it in Triggr

<Steps>
  <Step title="Open the integration">
    Go to **Integrations > Cove Data Protection** and click **Configure** on the Base Configuration card.

    <Frame>
      <img src="https://mintcdn.com/triggr/nyuVXZ1rouDTTEvu/images/integrations-common/base-configuration.png?fit=max&auto=format&n=nyuVXZ1rouDTTEvu&q=85&s=bb81acb082055015f91beda7b4876f35" alt="The Base Configuration card with Status Not Configured, Admin Consent Not Required and a Configure button." width="2272" height="330" data-path="images/integrations-common/base-configuration.png" />
    </Frame>
  </Step>

  <Step title="Enter the credentials">
    Enter your top-level customer's name as Partner (customer) name, the token as API user token and the full login name as API user login name, then click **Save Configuration**.

    <Frame>
      <img src="https://mintcdn.com/triggr/nyuVXZ1rouDTTEvu/images/cove/configure.png?fit=max&auto=format&n=nyuVXZ1rouDTTEvu&q=85&s=78791f1f631b0f5093a55c4560c57151" alt="The Cove Data Protection configuration window with Partner (customer) name, API user token and API user login name fields, an Allow insecure TLS switch under Advanced, and a Save Configuration button." width="1344" height="1450" data-path="images/cove/configure.png" />
    </Frame>
  </Step>
</Steps>

One configuration covers every customer the API user can reach, with no client mapping. Workflows pass the customer's numeric ID from Management > Customers (not the UID) as `partnerId` or `PartnerId`.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Cove login failed">
    Partner (customer) name must match exactly, and API user login name must include the suffix. If you've lost the token, delete the API user and create a new one.
  </Accordion>

  <Accordion title="Customers or devices are missing">
    The API user only works within its own customer. Create one under your top-level customer.
  </Accordion>

  <Accordion title="A step returns an error object">
    Cove can report failures in the body with status 200. Method and parameter names are case-sensitive, and changing devices needs a role that can edit and delete them.
  </Accordion>
</AccordionGroup>


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