> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/integrations/business-systems/netsuite.md).

# NetSuite

Learn how to integrate NetSuite using the NetSuite API connector

## Overview

The NetSuite connector allows Couchdrop to connect directly to the NetSuite API and use NetSuite data within Couchdrop Automations.

Because loading every possible NetSuite record and path would significantly affect performance and loading times, Couchdrop provides commonly used records such as Accounts, Customers, Payments, and Invoices.

If your organization requires a record type that is currently unsupported, please reach out to us at <sales@couchdrop.io>.

### How NetSuite works with Couchdrop

NetSuite is a direct API integration rather than a file-based storage connection. This type of integration does not appear directly as a [virtual folder](/storage/file-browser.md), as it deals directly with API data.&#x20;

After you configure the connection, it becomes available within [Automations & Actions](/automations/overview.md). In the workflow builder, NetSuite connections appear under **External API**, with actions available for the NetSuite records selected when the connection was configured.

This allows NetSuite data to be used in workflows alongside file-based actions and other connected platforms.

## Configuration steps

Using the NetSuite connector requires initial setup in two areas: Creating an application in NetSuite and integrating the NetSuite Application with Couchdrop.&#x20;

{% hint style="warning" %}

#### Before you start

To configure the NetSuite API connector, you will need:

* A Couchdrop plan that includes Automations
* Administrator access to NetSuite with permission to manage Users, Roles, and Integrations
* A NetSuite application to connect to Couchdrop
* The required NetSuite features enabled at the Company level
  {% endhint %}

### Step 1: Creating an application in NetSuite

1. Log in to NetSuite as an Admin who has access to edit Users and Roles
2. Go to **Setup > Company > Setup Tasks > Enable Features.** Enable **`REST Web Services, SuiteAnalytics Workbook` ,** and **`OAUTH 2.0`**
3. Create a new Role for the **User in Setup > Users/Roles > New Roles**&#x20;

{% hint style="info" %}
You can also use an existing Role in **Setup > Users/Roles > Manage Roles** if it has the permissions below.&#x20;
{% endhint %}

3. Go to **Permissions > Setup** and add **`REST Web Services`** ,  **`Log in using Access Tokens`** ,  **`SuiteAnalytics Workbook`** . Make sure the Level is set to "Full" for each.&#x20;
   1. The Role will also need permissions to access the NetSuite Records you want Couchdrop to access.
4. Give the Role to the User in **Setup > Users/Roles > \[Username]**. Click Edit and go to **Access > Roles > \[New Role]** and Save.&#x20;
5. Go to **Setup > Integration > Manage Integrations > New.**&#x20;

In **OAuth 2.0** check: **`AUTHORIZATION CODE GRANT`** , **`PUBLIC CLIENT`**  , **`REST WEB SERVICES`** . In **REDIRECT URI,** paste the URI below and click Save.&#x20;

```
https://my.couchdrop.io/systemconnector/systemintegration/activate/callback
```

{% hint style="danger" %}
The Client Credentials will only show one time. Make sure to copy them. You’ll need the **Consumer Key** and **Consumer Secret** to use the NetSuite Connector in Couchdrop.&#x20;
{% endhint %}

### Step 2: Integrating the NetSuite application with Couchdrop

1. In Couchdrop, choose to add a new Platform and select **NetSuite Integration.**&#x20;
2. Name the integration. Add the **Account ID** and paste the **Consumer Key** and **Consumer Secret** from the NetSuite application, then authorize the connection.&#x20;

{% hint style="info" %}
You can find the Account ID when logged into NetSuite in the URL at \[**ACCOUNT ID].**&#x61;pp.netsuite.com
{% endhint %}

3. Select the NetSuite Records you want Couchdrop to access and click Load Schema. Available actions will populate as a preview. Save the integration.&#x20;

## Frequently asked questions

<details>

<summary>Why is NetSuite giving me permission errors as an Administrator? </summary>

A NetSuite Administrator does not necessarily have full access and permissions. Check that the Administrator has the explicit permissions listed in [Creating an application in NetSuite](#creating-an-application-in-netsuite) at the "Full" level.&#x20;

</details>

<details>

<summary>Why aren't the actions I want showing? </summary>

The NetSuite API requires you to manually choose specific Records to include in your integration. Check that your record type is enabled and save the integration. If the specific actions are still unavailable, email us at <support@couchdrop.io>.&#x20;

</details>

<details>

<summary>Can file and API data be used in the same workflow? </summary>

Yes, Couchdrop supports flows using both file and API data. You can also use the Transform actions to convert data types as part of the workflow.

</details>

<details>

<summary>Can we use SFTP or FTP with NetSuite? </summary>

Yes, Couchdrop supports FTP and SFTP for NetSuite data. This is done using the standard SFTP connector and not the NetSuite API connector.&#x20;

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.couchdrop.io/integrations/business-systems/netsuite.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
