NetSuite for Docusign IAM

1. Quick Start

1. Prepare NetSuite

• A NetSuite administrator enables the required features, creates an integration record, a role, and a user with that role.
• Copy the Client ID when you save the integration record. NetSuite shows it only once.
• See Preparing NetSuite.

2. Install the App in Docusign

• Open the Docusign App Center and search for NetSuite.
• Open the NetSuite app card, click Log In to Install, then Install and Authorize on the consent screen.

3. Connect Your Account

• On the NetSuite app page, click Connect Account, choose the connection visibility, name the connection, and click Log In.
• Allow access, enter your NetSuite account ID, download the certificate, and upload it to an M2M mapping in NetSuite.
• Enter the Client ID and the Certificate ID, then click Verify & Connect.
• See Connecting Your Account.

4. Create a Workflow

• In Docusign, open Workflow Manager and create a workflow.
• Choose your preferred workflow start type.
• Add a NetSuite step: Read, Writeback, or File Upload.

5. Available Actions

• Read from NetSuite: pull a customer, contact, opportunity, quote, or vendor into your workflow to pre-fill an agreement.
• Writeback to NetSuite: update a record or create a new one after signing.
• File Upload to NetSuite: save the signed document in the NetSuite File Cabinet and attach it to the record.

6. Useful Information

• Custom Fields: which custom field types the app supports.
• How each object behaves on read and write: Contact, Customer, Opportunity, Quote, Vendor, and Other Known Behaviors.
• Common questions: FAQ & Troubleshooting.

2. Supported Objects

Select an object in the NetSuite object dropdown of a Read or Writeback step, or a drive in a File Upload step.

• Contact
• Customer
• Opportunity
• Quote, read only
• Vendor

An object appears in the step only when the integration role has its permission. See Integration Role Permissions.

More NetSuite modules will be added to the app later. After a release, use Reload Objects on the connection to see them.

3. Contact

Contact is the NetSuite contact record: a person who works for a customer, a vendor, or another company.

Contact Fields

The Read step offers the standard fields of the contact record and your custom fields: name and salutation, job title, email and phone numbers, company, subsidiary, assistant, supervisor, owner, comments, the default address, and the created and modified dates.

Writable: First Name, Last Name, Job Title, Email, Company Internal ID, Subsidiary ID, and custom fields. Every other field is read only.

Required: First Name, Last Name, Subsidiary ID. The step marks them with an asterisk.

Writing Contacts

• First Name and Last Name are required. NetSuite builds Contact Name from them.
• Subsidiary ID takes the subsidiary's numeric ID, 5, not its name. See Subsidiary ID.
• Company Internal ID is optional. It takes the Record ID of the company the contact works for. A contact's Record ID or an ID that matches no company fails the step.
• Keep the company and the contact in the same subsidiary. NetSuite does not compare them and saves a contact whose Subsidiary ID differs from its company's.

4. Customer

Customer is the NetSuite customer record. Leads and prospects are customer records at an earlier stage, see Reading Customers.

Customer Fields

The Read step offers the standard fields of the customer record and your custom fields: Customer ID, company and individual names, email and phone numbers, status, subsidiary, currency, terms, sales rep, start and end dates, credit limit and credit hold, balances, the default address, and the created and modified dates.

Writable: Customer ID, Company Name, Individual, First Name, Middle Name, Last Name, Job Title, Email, Alt. Email, Account, Print on Check As, Start Date, End Date, Subsidiary ID, Currency ID, Sales Rep Internal ID, and custom fields. Every other field is read only.

Required: Subsidiary ID, marked with an asterisk. Company Name or First Name and Last Name, depending on the customer type, see below.

Writing Customers

• A company customer needs Company Name. An individual needs First Name and Last Name. Individual = Yes makes an individual; No, the default, a company. These fields carry no asterisk: a missing one fails the step.
• First Name, Middle Name, Last Name, and Salutation are saved only on an individual. On a company customer they are dropped and the step succeeds. Map Individual in the same step.
• NetSuite builds Customer ID from the name. A Customer ID you pass on Create is kept. Changing the name, or turning a company into an individual, rebuilds it.
• NetSuite fills Currency, Terms, and Status on Create from the subsidiary and the account defaults.
• Changing Currency ID on a customer with transactions converts its balances and clears its Credit Limit. NetSuite reports no error. Map Currency ID on Update only when the currency should change.
• Sales Rep Internal ID takes an employee marked as a sales rep, from any subsidiary. Another employee fails the step. NetSuite can also assign a sales rep on its own.
• Subsidiary ID can change only while the customer has no transactions. After the first invoice or sales order, the step fails.
• Start Date and End Date store the calendar date written in the value, without a time zone shift: 2026-10-02T23:30:00-07:00 is saved as 2 October. They read back as midnight UTC.

Reading Customers

• Status carries the stage. Lead, prospect, and customer statuses all live on the customer record, and Status is read only. Status names and IDs differ between accounts: compare the Status Name your account uses.
• Most fields come only with a read by Record ID, or with a rule that matches one record. A rule that returns several customers leaves them out.
• Balances read 0 on a customer without transactions. Balance is the open invoices, tax included. Overdue Balance is the open invoices past due. Unbilled Orders includes sales orders still pending approval. Deposit Balance is the customer deposits. The Consolidated fields equal these on a customer without sub-customers.
• Current is calculated by the app from the open invoices that are not yet due. The overdue aging buckets are not offered.
• Credit Hold Mode ID reads AUTO, OFF, or ON.

Searching Customers

• Phone is the only searchable phone field. Mobile Phone, Home Phone, Alt. Phone, and Fax cannot be used in a rule.
• Text matches in exact letter case, except Email: Last Name = tester does not find Tester.

5. Opportunity

Opportunity is the NetSuite opportunity: a deal with a customer.

Opportunity Fields

The Read step offers Opportunity #, Opportunity Date, Opportunity Title, the customer, status and stage, Probability, Expected Close, Range Low, Range High, Projected Total, Weighted Total, Sales Rep, Win/Loss Reason, Currency, Subsidiary, Details, Job, Location, the created and modified dates, and the custom fields that apply to Opportunity.

Writable: Opportunity #, Opportunity Date, Opportunity Title, Customer ID, Expected Close, Range Low, Range High, Sales Rep Internal ID, Win/Loss Reason ID, Currency ID, Job ID, Location ID, and custom fields. Every other field is read only.

Required: Customer ID, marked with an asterisk.

Writing Opportunities

• Customer ID takes the customer's Record ID, 2295, not the Customer ID text shown on the customer record. Map it from the Record ID of a Read step on Customer. A name fails the step.
• Customer ID is the only field NetSuite needs to create an opportunity. NetSuite takes the subsidiary from the customer and sets the number, currency, first stage, probability, and dates.
• Opportunity # is saved as written. Leave it unmapped to let NetSuite number the opportunity.
• The stage, Probability, Subsidiary ID, and Details are read only. NetSuite sets the subsidiary from the customer and the probability from the stage.
• Job ID takes a project of the opportunity's customer. Location ID takes a location of the opportunity's subsidiary. Another value fails the step.
• Projected Total follows Range Low, not the item lines. Weighted Total is Projected Total times Probability. Both are read only.
• Only the custom fields that apply to Opportunity in NetSuite are offered. See Custom Fields.

Searching Opportunities

• Subsidiary ID cannot be used in a rule. Read the opportunity by Record ID to get its subsidiary.
• Probability matches the percent as read: Probability = 45, or a range such as Probability >= 40. A fraction such as 0.45 finds nothing.
• Item lines are not offered.

6. Quote

Quote is the NetSuite estimate. The object is called Quote in the step, and its fields keep NetSuite's names: Estimate #, Estimate Date, Estimate Title.

• Quote is read and search only. A Create or Update step on Quote fails and nothing reaches NetSuite. Create and change quotes in NetSuite.
• Status reads as a word: Open, Processed, Closed, or Expired.
• Totals, status, and the Bill To and Ship To addresses come from NetSuite.
• Discount Rate does not say whether it is a percent or an amount. Read Discount Total for the money value.
• Item lines are not offered.
• Subsidiary ID cannot be used in a rule, and Probability matches the percent as read, as on Opportunity.
• Only the custom fields that apply to Estimate in NetSuite are offered. See Custom Fields.

7. Vendor

Vendor is the NetSuite vendor record. A vendor is a company or an individual, set by the Individual field.

Vendor Fields

The Read step offers the standard fields of the vendor record and your custom fields: Vendor ID, company and legal name, the individual's name, email, phone numbers, web address, subsidiary, currency, terms, category, primary contact, tax numbers, balances, the default address, and the created and modified dates.

Writable: Vendor ID, Company Name, Legal Name, Email, Subsidiary ID, Individual, First Name, Middle Name, Last Name, Tax ID, Business Number, VAT Registration No., Primary Contact Internal ID, and custom fields. Every other field is read only.

Required: Subsidiary ID, marked with an asterisk. Company Name or First Name and Last Name, depending on the vendor type, see below.

Company and Individual Vendors

Individual = Yes makes an individual vendor. No, the default, makes a company.

Field	Company (Individual = No)	Individual (Individual = Yes)
Company Name	Required	Optional
First Name, Last Name	Not stored	Required
Middle Name	Not stored	Optional
Legal Name	Optional, defaults to Company Name	Optional

• The type-dependent fields carry no asterisk. The step marks only fields required for every vendor. A missing Company Name on a company, or First Name and Last Name on an individual, fails the step.
• A name field that does not fit the type is dropped and the step succeeds. First Name on a company vendor is not saved.
• To turn a company vendor into an individual, map First Name and Last Name in the same step.
• Middle Name, Salutation, Job Title, Home Phone, and Mobile Phone belong to an individual vendor. On a company vendor they read empty.

Tax Numbers by Subsidiary Country

Field	Stored on a vendor in
Tax ID	a US subsidiary
Business Number	a Canadian subsidiary
VAT Registration No.	a UK subsidiary

On a subsidiary of another country the step succeeds and the value is not saved. NetSuite does not check the format of Tax ID.

Writing Vendors

• NetSuite builds Vendor ID from the name. Map Vendor ID only to set your own; it is kept as written. It is required only when the account has automatic vendor names turned off.
• Vendor ID is unique. A Vendor ID that another vendor already has fails the step.
• Changing Company Name, First Name, Middle Name, or Last Name rebuilds Vendor ID and replaces your own Vendor ID. Map Vendor ID in every step that changes the name.
• Vendor ID is not the Record ID. A rule on Record ID with a Vendor ID value finds nothing.
• A Vendor ID built from a name with non-Latin letters can differ from the name. Find such a vendor by Company Name or Record ID.
• Company Name takes up to 83 characters. A longer name fails the step.
• Primary Contact Internal ID takes a contact's Record ID. NetSuite does not check that the contact belongs to this vendor.
• Balance, Unbilled Orders, and Opening Balance are read only. NetSuite calculates them from transactions.

8. Custom Fields

When you connect, the app loads the schema of each object from NetSuite, custom fields included, and offers the custom fields of the types below in Read and Writeback steps. Other types are not supported: List/Record fields, for example, do not appear.

Supported Custom Field Types

Custom field type	In a workflow
Free-Form Text, Text Area, Email Address, Phone Number, Check Box, Date, Integer Number, Decimal Number, Currency, Percent	Read, write, and search
Long Text	Read and write. Not usable in a rule
Rich Text	Read only, as plain text
Any supported type with Store Value unchecked	Read only
List/Record, Multiple Select, Document, Image, Inline HTML, Help, Password, Hyperlink, Time Of Day	Not available

How the App Passes Custom Field Values

The app passes a custom field value as is. Your NetSuite account defines the rules of each custom field: its format, length, whether it is mandatory, who can edit it. The app does not know those rules, so it sends the value from the workflow unchanged and NetSuite applies them. Set up the workflow to follow your field settings.

• A custom field's label ends with (Custom), for example EFT Bill Payment (Custom).
• A custom field appears on the objects in its Applies To setting in NetSuite. A value for a field that does not apply to the record is dropped without an error.
• The integration role needs Custom Fields (View). Without it no custom field appears. See Integration Role Permissions.
• The field list is loaded when you connect. After adding or changing a custom field in NetSuite, use Reload Objects on the connection.
• A rule that returns several records leaves out Long Text fields. Read by Record ID, or with a rule that matches one record, to get them.
• Percent fields match by the percent value in a rule, 12.5, not 0.125.

9. Other Known Behaviors

Record ID and Linked Records

• Record ID is NetSuite's internal number for the record, the id= value in the record's address in NetSuite. It is not the Vendor ID, Customer ID, or document number NetSuite shows on the record.
• Linked records come in pairs. <Field> Internal ID takes the Record ID of a linked record, such as a company, contact, or employee. <Field> ID takes the ID of a list value, such as Subsidiary, Currency, or Terms. <Field> Name is read only.
• Pass IDs as digits. A name in an ID field fails the step.

Subsidiary ID

• Subsidiary ID is required to create a Customer, Contact, or Vendor. It takes the numeric ID, 5. Open the subsidiary in NetSuite to see the ID in the id= part of the address.
• In an Update step it can stay empty, and the record keeps its subsidiary. The asterisk still shows when you add the field. Update or Create needs it, because the step may create a record.
• A mapped Subsidiary ID moves the record to that subsidiary. On Update, map the record's current subsidiary, for example from a Read step.
• A workflow for one subsidiary can use a fixed value. Type the ID into the field instead of choosing a variable.

Searching for a Record

• A rule can use Record ID and the fields marked (Searchable). Any other field fails the step.
• Record ID joined with AND checks the other conditions on that record. When they do not hold, the rule finds nothing.
• A rule that mixes AND and OR is grouped from the right. A AND B OR C means A AND (B OR C). Put the single condition first to get C OR (A AND B).
• Email matches in any letter case. Other text matches in exact letter case.
• An empty value in a rule finds records where the field is empty. It does not skip the condition, so check that the variable is filled.
• Phone numbers read and match as digits, country code included. +1 555 010 1006 and 15550101006 find the same record; 555-010-1006 does not.
• Check boxes take Yes / No, true / false, 1 / 0, or T / F, in any letter case. A check box that was never set counts as No.
• Percent custom fields match by the percent value, 12.5, not 0.125.

Reading Values

• Date fields read as midnight UTC, 2026-10-02T00:00:00.000Z, and store the calendar date written in the value.
• Date Created and Last Modified Date read as ISO 8601 in UTC to the minute, 2026-10-02T11:59:00.000Z. They cannot be used in a rule.
• The address is read only. Default Address returns the whole address as one value. The Default Billing and Default Shipping fields return its parts: Address 1, Address 2, City, State, Zip, Country ID, Country Name, Attention, and Addressee. Without a default billing or shipping address in NetSuite, those fields are empty.
• A search that returns several records leaves out the address parts and Long Text custom fields. Read by Record ID, or with a rule that matches one record, to get them.
• Multi-select fields are not returned, for example Contact Category.

Writeback Rules

• Required fields are added to a Create step automatically. In an Update step they are not; when you add one, it can stay empty.
• An empty value leaves the field as it is. A field cannot be cleared from a workflow. A step where every mapped value is empty fails.
• Update must match exactly one record. No match or several matches fail the step and nothing is written. To create the record when it is missing, use Update or Create.
• Update or Create creates a record when the rule finds none, including a rule of Record ID AND a condition that the record fails.
• Overwrite if field value exists appears only in Update or Create, on the required fields. Unticked, a required field that already has a value keeps it. Every other mapped field is always written.
• Some values are dropped without an error, such as a tax number on a vendor in another country, or a value for a custom field that does not apply to the record. Check the record after the first run of a new workflow.
• A Create can take up to about 30 seconds. Do not run a slow step again: a second run creates a second record.
• A step that maps a read-only or removed field fails as a whole, and nothing is written. After an app update, use Reload Objects and recreate the steps.

Role Restrictions

• Records the role cannot access look missing. A record in a subsidiary the role is restricted from cannot be read, found, or written.
• A record linked to a record the role cannot access cannot be updated. For example, a contact whose supervisor belongs to such a subsidiary: every write to that contact fails.

10. Installation and Configuration

Prerequisites

• A NetSuite administrator account: the setup enables features and creates an integration record, a role, and an M2M mapping.
• A Docusign account with admin rights to install and manage apps in the App Center.

Preparing NetSuite

A NetSuite administrator does this once per NetSuite account, before the first connection. Each step links to the NetSuite guide for details.

1. Enable features. Go to Setup → Company → Enable Features. On the SuiteCloud tab, check REST Web Services and OAuth 2.0. On the Analytics tab, check SuiteAnalytics Workbook, which searches use. See Enabling Features.

2. Create the integration record. Go to Setup → Integration → Manage Integrations → New and name it, for example Docusign IAM for NetSuite. On the Authentication subtab:

   • check Client Credentials (M2M) Grant;
   • uncheck Authorization Code Grant, which is checked by default and makes NetSuite ask for a Redirect URI;
   • leave Public Client unchecked;
   • under Scope, check REST Web Services and RESTlets.

   Click Save. See Create Integration Records for Applications to Use OAuth 2.0.

   ⚠️ Copy the Client ID right after you save. NetSuite shows it only once. You will enter it when you connect, and again for every new connection to this account. The Client Secret is not needed.

3. Create the integration role. Go to Setup → Users/Roles → Manage Roles → New and name it, for example Docusign IAM Integration. Add the permissions from Integration Role Permissions. Do not use the Administrator role. See Customizing or Creating NetSuite Roles.

4. Give the role to a user. Open an employee record, go to the Access subtab, check Give Access, add the role under Roles, and click Save. An existing employee works; a separate integration user is not required. See Assigning Roles to an Employee.

Integration Role Permissions

Permissions are added as rows. On the role, open the Permissions subtab, then Transactions, Reports, Lists, or Setup, choose the permission and its level, and click Add.

Needed for	Subtab	Permission	Level
Every connection	Setup	Log in using OAuth 2.0 Access Tokens	Full
Every connection	Setup	REST Web Services	Full
Every connection	Setup	Custom Fields	View
Every connection	Reports	SuiteAnalytics Workbook	Edit
Every connection	Lists	Perform Search	Full
Contact	Lists	Contacts	Edit
Customer	Lists	Customers	Edit
Vendor	Lists	Vendors	Edit
Opportunity	Transactions	Opportunity	Edit
Quote	Transactions	Estimate	Edit
Linked lists and names	Lists	Employees, Subsidiaries, Currency, Accounting Lists	View
File Upload	Lists	Documents and Files	Edit

NetSuite moves and renames permissions between releases. If a permission is not on the subtab in the table, look for it by name on the other subtabs.

The setup page in Docusign also lists permissions for modules that will be released later. Granting them now means the role needs no changes when those modules arrive.

• Do not restrict the role by subsidiary, department, class, or location, or to its own records. NetSuite hides restricted records from the app, so they look missing. If the role must be restricted, select every subsidiary your workflows use.

How to Install the App

• Open the Docusign App Center and search for NetSuite.

  

• Click the NetSuite app card, then click Log In to Install.

  

• Review the access the app requests and click Install and Authorize.

The app now appears with an Installed status.

Connecting Your Account

Keep NetSuite open in a second browser tab: the last step of the connection happens there.

1. On the installed app page, click Connect Account. To add a connection later, click New Connection on the Connections page.

   

2. Connection Visibility: choose how the connection is shared, then click Next.

   • Private: accessible only by you in Docusign.
   • Shared: accessible by multiple users or the whole team.

   

3. Name Connection: enter a name that identifies the NetSuite account, for example Demo-Manual. It appears in workflow steps. Click Log In.

   

4. On Allow Docusign to connect to NetSuite?, click Allow & continue.

   

5. Which NetSuite account are we connecting?: enter the account ID exactly as it appears in your NetSuite address, prefix included, and click Continue.

   • A test drive account looks like TSTDRV1234567, not 1234567. A sandbox looks like 123456_SB1.
   • Copy the ID from the browser address bar, the part before .app.netsuite.com, or paste the whole address of any NetSuite page.
   • The ID is also under Setup → Company → Company Information, on the Company URLs subtab.

   

   

   ⚠️ An ID without its prefix passes this screen and fails later, at Verify & Connect.

6. One-time NetSuite admin setup: click Download certificate. The file is the public part of the certificate; the private key stays with the app.

7. In NetSuite, go to Setup → Integration → Manage Authentication → OAuth 2.0 Client Credentials (M2M) Setup and click Create New.

   

8. In Create a New Client Credentials Mapping, select:

   • Entity: the user who has the integration role;
   • Role: the integration role;
   • Application: the integration record;
   • Certificate: click Choose a file and select the downloaded certificate.

   Click Save, then copy the Certificate ID from the new row of the list. See OAuth 2.0 Client Credentials Setup.

   

9. Back on the setup page, enter the Client ID from the integration record and the Certificate ID from the mapping, then click Verify & Connect. The app signs in to NetSuite, runs one test search, and checks which objects the role can see.

   

10. If the role cannot see an object, the page names the object and the permission it needs. Grant the permission in NetSuite and click Connect anyway. Objects the role can see by then are connected; an object you do not use can stay without a permission and does not appear in workflow steps.

    

The connection is added and ready to use in workflow steps.

• Finish the setup within 120 minutes. After that the setup session expires and you start the connection again.
• One certificate serves every connection to the NetSuite account. For the next connection, the setup page says a certificate already exists: enter the same Client ID and Certificate ID and click Verify & Connect. Nothing changes in NetSuite.

Managing Connections

On the NetSuite app page, open the Manage dropdown and select Manage Connections to see every connection.

Use the three-dot (⋮) menu next to a connection:

• Edit connection name: rename the connection.
• Reconnect: run the connection setup again, for example after the certificate is replaced.
• Reload Objects: refresh the objects and fields. Run it after an app update, after granting the role a permission, or after adding a custom field in NetSuite.
• Delete Connection: remove the connection. ⚠️ This may break workflows that use it.

Replacing the Certificate

The certificate is valid for two years. Within 30 days of expiry, the setup page shows the date and how to renew.

⚠️ Replacing the certificate affects every connection to the NetSuite account. Each connection needs a reconnect afterwards.

• Start Reconnect on one connection, enter the Client ID and the Certificate ID, and click Replace certificate.
• Download the new certificate, create a new M2M mapping with it in NetSuite, and enter the new Certificate ID.
• Click Verify & Connect, then Reconnect every other connection to the account with the new Certificate ID.

Adding a New Connection

Use Manage → New Connection on the app page, or + New Connection on the Connections page. Each connection appears separately in workflow steps.

11. How to Use the App

Create a Workflow

• Log in to Docusign and go to Agreements → Workflows.

• Click Create Workflow.

  

• Build your workflow using the available steps, including the NetSuite actions.

• Publish the workflow when it is ready.

Available NetSuite Actions

Click + Add Step and search for NetSuite:

• Read from NetSuite: fetch a record and expose its fields as workflow variables. See Read from NetSuite.
• Writeback to NetSuite: update a record or create a new one. See Writeback to NetSuite.
• File Upload to NetSuite: save a document from the workflow in NetSuite and attach it to a record. See File Upload to NetSuite.

A typical contact signing flow:

1. Read from NetSuite: read the Contact.
2. Prepare eSignature Template: pre-fill the agreement.
3. Send Documents for Signature.
4. File Upload to NetSuite: attach the signed agreement to the contact.
5. Writeback to NetSuite: update the contact with the data collected during signing.

12. Read from NetSuite

The Read from NetSuite step retrieves a record and exposes its fields as workflow variables.

Choose the workflow start that fits your process. In this example the workflow starts From an API Call and receives the Record ID of the contact in a Text variable named object_id.

1. Add the Read Step

On the workflow canvas, click + below Start Workflow.

Search for NetSuite and select Read from NetSuite.

2. Configure Connection and Object

• Connection: select the connection you created during installation.
• NetSuite object: choose one of the supported objects. This example uses Contact.

Click Next.

3. Select Fields

Click Add or Remove Fields and tick the fields your workflow needs. The selected fields become workflow variables for later steps.

The fields of each object are described under the object's section, for example Contact.

Click Next.

4. Identify the Record

Create a rule that tells the step which record to read. In this example, match Record ID to the object_id variable from the workflow start:

• NetSuite field: Record ID
• Operator: Equal to
• Workflow field: object_id, under Variables From Workflow Start

Click Done. Under How many records should this step return?, pick one:

• A single record: the first record that matches.
• Multiple records: up to five matching records.

Use preview this step to check the rule against live data. Click Apply.

The rules for matching fields are under Searching for a Record.

13. Writeback to NetSuite

The Writeback to NetSuite step updates a record or creates a new one.

1. Add the Writeback Step

On the workflow canvas, click + where the writeback belongs, for example after Send Documents for Signature. Search for NetSuite and select Writeback to NetSuite.

2. Configure Connection, Object, and Write Setting

• Connection: select your NetSuite connection.

• NetSuite object: choose the object to write to. In most workflows it is the object of your Read step. Quote is read only and cannot be written.

  

• Write settings:

  • Update or Create: updates the matching record, or creates one if the rule finds nothing.
  • Update: updates an existing record only. The rule must match exactly one record, or the step fails.
  • Create: always creates a record.

  

Click Next.

3. Map Fields

Required fields of the object are already on the list. Click Add or Remove Fields to add the other fields you want to write, and map each one to the workflow variable that supplies the value.

⚠️ Map from the right source. The variable picker also lists the output of your Read from NetSuite step. Mapping from there writes the original values back unchanged. Map from the step that produced the new data, such as Send Documents for Signature or Collect Data with Web Forms.

The writable and required fields of each object are listed under the object's section. Overwrite if field value exists is described under Writeback Rules.

Click Next.

4. Identify the Record to Write

For Update or Create and Update, create a rule that finds the record. In this example, match Record ID to object_id from the workflow start. A rule can also use the Record ID from a Read step on the same object, or any field marked (Searchable).

Click Done, then Apply.

14. File Upload to NetSuite

The File Upload to NetSuite step saves a document from the workflow in the NetSuite File Cabinet and attaches it to a record.

Check File Upload Known Behaviors before you build the step.

1. Add the File Upload Step

Add a step after signing completes, search for NetSuite, and select File Upload to NetSuite.

2. Select the File

Choose the file or envelope from an earlier step. In this example it is the Combined Envelope File from Send Documents for Signature.

An empty list means no earlier step produced a file. Check that a step such as Send Documents for Signature comes before File Upload.

3. Choose the Drive

• Select connection: your NetSuite connection.
• Select drive: the object of the record to attach the file to. Each record drive reads <Object> (use Record ID as subfolder). This example uses Contact (use Record ID as subfolder). To save a file without attaching it, use the Docusign Workflow Documents drive.

4. Put the Record ID in the Folder

File Upload takes the record to attach to from the folder. The folder holds the Record ID of a record of the drive's object.

• Click Add Folder.

  

• Open the Select folder dropdown and pick New Subfolder.

  

• In the New folder dialog, click Add Variable and choose the step that returns the record.

  

• Select Record ID.

  

• The variable appears in the Folder name field. Click Add.

  

• Select folder now shows the Record ID variable. Click Next.

  

⚠️ Take the Record ID from a step on the drive's object. With the Contact drive, use Contact / Record ID from a Read or Writeback step on Contact. A Read step on Customer returns a customer's Record ID, which points to no contact, and the file is not attached.

5. Name the File

Build the file name from Add Text and Add Variable. A timestamp variable keeps repeat runs from producing identical names.

Click Apply. The file is saved in the Docusign Workflow Documents folder and attached to the record.

The Docusign Workflow Documents Drive

Docusign Workflow Documents saves the file in the Docusign Workflow Documents folder and attaches it to nothing. Use it for documents that belong to no supported object.

Where Files Are Stored

Every upload goes to one folder, Attachments Received / Docusign Workflow Documents, in the File Cabinet. The app creates the folder on the first upload and keeps using it. The folders in the step only point to the record: the app does not create them in NetSuite.

• A folder you create at the top level of the File Cabinet is not used, whatever its name.
• The file appears on the record's Files subtab on Customer, Contact, and Vendor. On an Opportunity it is under Activities → Files.

File Upload Known Behaviors

• Record ID goes in the last folder. Folders before it are ignored.
• The stored name adds the record and a short code to your file name: Signed Agreement (Contact 1993) 4fc486ce.pdf.
• Record ID takes digits only, without leading zeros. A number NetSuite shows on the record, such as a Vendor ID, does not work.
• A Record ID that matches no record does not fail the step. The file is saved in Docusign Workflow Documents without a record. Look for it there when it is missing from the record.

⚠️ A folder before the Record ID made of digits only fails the step. The app reads a folder such as 2026 or 0001 as a second Record ID. Letters and digits together, such as FY2026 or 2026-Q4, work.

15. FAQ & Troubleshooting

Verify & Connect fails although the account ID is right.

Enter the ID with its prefix, as in your NetSuite address: TSTDRV1234567, or 123456_SB1 for a sandbox. See Connecting Your Account.

I did not copy the Client ID.

NetSuite shows it once. Reset the credentials on the integration record to get a new one, then reconnect every connection that used the old Client ID.

An object is missing from the NetSuite object list.

The integration role has no permission for it. Grant the permission from Integration Role Permissions, then use Reload Objects on the connection.

No custom fields appear.

Grant the role Custom Fields (View), then use Reload Objects. Check that the field type is supported, see Custom Fields.

A record I can see in NetSuite is not found.

The role is restricted from the record's subsidiary, or the rule uses a value written differently. Copy the value as the Read step returns it, for example a phone number as digits only.

The Update step failed.

The rule matched no record or several. Use the Record ID from a Read step, or use Update or Create.

The step succeeded, but a vendor field is empty in NetSuite.

The field does not apply to this vendor: a tax number of another country, or a name field of the other vendor type. See Vendor.

Vendor ID changed after the name changed.

NetSuite rebuilds Vendor ID from the name. Map Vendor ID in the same step.

How do I clear a field?

Not from a workflow. An empty value leaves the field as it is. Clear it in NetSuite.

Where is the uploaded file?

In the File Cabinet, under Attachments Received / Docusign Workflow Documents. See Where Files Are Stored.

The file is in the folder, but not on the record.

The Record ID in the last folder matched no record of the drive's object. Map the Record ID from a step on the same object.

File Upload fails with my own folders in the path.

One of the folders before the Record ID is made of digits only. Rename it, for example FY2026 instead of 2026.

Changing a customer's currency cleared its credit limit.

NetSuite converts the balances of a customer with transactions to the new currency and clears Credit Limit. Map Currency ID only when the currency should change.

Every connection stopped working after the certificate was replaced.

Each connection to the account needs a Reconnect with the new Certificate ID. See Replacing the Certificate.