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

# Freshsales

> Connect Freshsales to Iru Compliance with an API key and bundle alias to collect user roles, permission matrices, and territory-based access controls.

### About Freshsales

Iru reads **users with their roles**, **roles with permissions**, **territories**, and **field-level permissions for sensitive data** from the Freshsales (Freshworks CRM) API. Authentication uses an **API key** together with your **bundle alias**, both found under **Profile Settings** → **API Settings**. Requests target `https://YOUR_BUNDLE_ALIAS.myfreshworks.com/crm/sales/api`. The connector wizard collects the **API key** first, then the **bundle alias**.

Freshsales and **Freshservice** are different products with **different authentication schemes**. If you are connecting IT service management data, use the [Freshservice](/en/compliance/sources/freshservice-source) article instead.

### How It Works

```http theme={null}
Authorization: Token token=YOUR_API_KEY
```

Freshsales does **not** use Basic auth or a Bearer prefix. The key goes in the `Authorization` header in the literal form `Token token=YOUR_API_KEY`. The API is **unversioned**. There is no version header or dated revision.

The **bundle alias** selects which CRM account to read when your Freshworks organization has more than one. That is why the field is required. An API key is **per user** and inherits **exactly that user's role**, with no per-endpoint scopes.

| Detail             | Value                          |
| ------------------ | ------------------------------ |
| **Category**       | CRM                            |
| **Authentication** | Token (API key + bundle alias) |

Official references: [Freshworks CRM API](https://developers.freshworks.com/crm/api/).

### Prerequisites

* Your **bundle alias** and **API key**, both on the same **API Settings** page.
* A **dedicated admin-level CRM user** to generate the key from. The key inherits that user's role and has no scopes, so a key from a sales user with territory restrictions returns an incomplete permission picture.

### Connect Freshsales to Iru

<Tabs>
  <Tab title="Freshsales">
    <Note>
      Complete this tab before you connect the source in Compliance.
    </Note>

    <Steps>
      <Step title="Sign in to Freshsales">
        Sign in to your Freshsales account as the **admin-level user** whose access the integration should inherit.
      </Step>

      <Step title="Open Profile Settings">
        Select your **profile picture** in the top-right corner, then **Profile Settings**.
      </Step>

      <Step title="Open API Settings">
        Select the **API Settings** tab.
      </Step>

      <Step title="Copy the API key and bundle alias">
        Copy the value shown under **Your API key**. Copy the **Bundle alias**, shown on the same tab just below the API key. If your organization has only one CRM account this is still required.
      </Step>
    </Steps>

    <Note>
      Continue on the [**Iru Compliance**](#iru-compliance) tab.
    </Note>
  </Tab>

  <Tab title="Iru Compliance">
    <Note>
      Finish the [**Freshsales**](#freshsales) tab first.
    </Note>

    <Steps>
      <Step title="Open Sources">
        In Iru Compliance, on the left navigation bar, expand **Compliance** and select **Sources**.

        <Frame>
          <img src="https://mintcdn.com/iru/tI0HDLDwHj8r9Ile/assets/media/images/iru-navigation-compliance-sources.png?fit=max&auto=format&n=tI0HDLDwHj8r9Ile&q=85&s=87dcef15fc17d2fb9a6e53f454e41710" alt="Left navigation: Compliance expanded, Sources selected" width="410" height="1024" data-path="assets/media/images/iru-navigation-compliance-sources.png" />
        </Frame>
      </Step>

      <Step title="Turn on Freshsales">
        Find **Freshsales** (use **Category** or **Search by name or description**). On that card, turn on the **toggle**. A browser tab or window may open for the connector wizard.
      </Step>

      <Step title="Enter the API key">
        The first wizard step is **Enter API Key (Authorization)**. Paste the API key into the **Authorization** field. The wizard shows the header format `Token token=<api_key>`.
      </Step>

      <Step title="Submit the API key">
        Click **Submit API Key**.
      </Step>

      <Step title="Enter the bundle alias">
        Enter the **bundle alias** only (for example `acme`, not the full `myfreshworks.com` URL). Confirm the preview URL if the wizard shows one. When the connection succeeds, the wizard shows **Connection Configured**.
      </Step>

      <Step title="Confirm the source is Active">
        Close the **Iru is requesting access to external services** browser tab, then return to **Compliance** → **Sources** and confirm the **Freshsales** card is **Active**.
      </Step>
    </Steps>
  </Tab>
</Tabs>

### Troubleshooting

<AccordionGroup>
  <Accordion title="Nothing opens when you turn the source on">
    Check **pop-up blocker** settings for the Iru site and try again.
  </Accordion>

  <Accordion title="401 Authentication Failure">
    Confirm the API key is complete and that the **bundle alias** matches the CRM account the key belongs to. A valid key against the wrong bundle host fails the same way an invalid key does.
  </Accordion>

  <Accordion title="You copied a Freshservice key by mistake">
    The two products issue different credentials and authenticate differently. A Freshservice key will not work here.
  </Accordion>

  <Accordion title="Users appear but roles or territories are incomplete">
    The key belongs to a user whose own role cannot see them. Regenerate from an admin-level user.
  </Accordion>

  <Accordion title="The wizard reports an unreachable host">
    The bundle alias is the subdomain only. Do not include `https://` or `.myfreshworks.com`.
  </Accordion>
</AccordionGroup>

### Related Articles

<CardGroup cols={2}>
  <Card title="Sources Management" icon="plug" href="/en/compliance/sources-management">
    Browse and manage every Compliance source.
  </Card>

  <Card title="Freshservice" icon="headset" href="/en/compliance/sources/freshservice-source">
    Connect Freshservice for ITSM evidence.
  </Card>

  <Card title="Getting Started With Compliance" icon="rocket" href="/en/compliance/getting-started-with-compliance">
    Frameworks, actions, and **Artifacts**.
  </Card>

  <Card title="Artifacts Management" icon="folder-open" href="/en/compliance/artifacts-management">
    Upload, review, and organize evidence from sources and actions.
  </Card>
</CardGroup>