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

# Inserve

> Connect Inserve to Triggr with an Inserve API key and your Inserve address.

Triggr works with Inserve companies, contacts, tickets, assets, products, time registrations and custom cloud distributors. In Triggr's action names, clients are contact persons (Contactpersonen) and companies are your customers' organisations.

## Set up Inserve

Sign in as the account Triggr should work as: the key has that account's rights.

<Steps>
  <Step title="Open the API settings">
    Click the profile menu at the top right and choose **API instellingen**.
  </Step>

  <Step title="Generate a key">
    On the API sleutels tab, enter `Triggr` in Naam voor sleutel and click **Nieuwe sleutel genereren**.
  </Step>

  <Step title="Copy the key">
    Copy the new key. To see it again later, click Bekijken in the Sleutel column.
  </Step>
</Steps>

See Inserve's [API documentatie](https://docs.inserve.nl/nl/article/api-documentatie).

## Connect it in Triggr

<Steps>
  <Step title="Open the integration">
    Go to **Integrations > Inserve** 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 key and address">
    Paste the API Key, enter your Inserve address as Site URL, such as `https://yourcompany.inserve.nl`, with no trailing slash or `/api`, and click Save Configuration.

    <Frame>
      <img src="https://mintcdn.com/triggr/nyuVXZ1rouDTTEvu/images/inserve/configure.png?fit=max&auto=format&n=nyuVXZ1rouDTTEvu&q=85&s=84544e3e5bc6a133ca10928a6e53f64e" alt="The Inserve configuration window with API Key and Site URL fields, an Allow insecure TLS switch under Advanced, and a Save Configuration button." width="1344" height="1126" data-path="images/inserve/configure.png" />
    </Frame>
  </Step>
</Steps>

One connection covers all your clients. Run the me action to check it. JSON bodies use the field names in Inserve's [API reference](https://documenter.getpostman.com/view/14835414/2s935kQ6UW).

## Troubleshooting

<AccordionGroup>
  <Accordion title="Every action fails">
    Site URL must start with `https://` and have nothing after the domain.
  </Accordion>

  <Accordion title="Authentication errors">
    Check API Key holds the full key with no spaces, and that it still exists under API instellingen.
  </Accordion>

  <Accordion title="Actions refused">
    The account that created the key lacks the right. Give it a role with that right under Rollen and Rechten; you don't need a new key.
  </Accordion>

  <Accordion title="Rate limits">
    Inserve allows 3,600 API calls an hour per environment, across all integrations. Spread large workflows out or run them in smaller batches.
  </Accordion>
</AccordionGroup>


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