This is a paid bot, and its usage will be counted toward your plan's credit limit. For more information about credit usage, refer to this article.
General
Attach files from NetSuite records to your workflow documents during the signing session.
Use case: When onboarding a new client, this bot can automatically attach their contract, purchase history, or project brief from NetSuite—ensuring all necessary documents are included without manual uploads.
To set up the bot, use these document types:
Attachment request;
Document placeholder;
Web form with an Attachment request widget.
How to set up
To add the bot:
1. In the step settings, select Add bot or click the plus icon after a specific action.
2. Choose Bot and search for the Import files from NetSuite record bot.
3. Click on the bot to install it.
Trigger
A trigger is an event that causes the bot to start working. The moment of the bot's activation depends on its placement in the flow:
If the bot is added after a step or any other element, it will run once that element finishes its job.
If within the step, the bot will run based on the trigger you specify. Choose the trigger type most relevant to your case:
According to this, select the bot's trigger type that will be most relevant to your case:
Trigger type | Description |
Step started | The bot activates when you start the workflow |
Document opened | The bot activates when signers start filling out the documents or switch between them. |
Field changed | Use for cases where a response or action is needed immediately after a user enters or updates information in the specific field. Select the document and the field that the bot should pay attention to complete the setup. |
Document completed | The bot activates once the signer completes a document you specify in the trigger settings. |
Connection settings
To connect the bot to your NetSuite account, select Connect in the Source section.
If needed, you can add multiple accounts, edit, or disconnect them at any time. You may add the same account several times, as every new connection is saved separately.
Select a base object in NeSuite. The base record is needed to choose the object you’d like to base the process on (Lead, Customer, Project, Partner, etc.) It can be any data available in NetSuite.
Find record
In Find record, set rules to locate the NetSuite source record:
Manual setup: match document fields to record fields or custom values.This option can be used for workflows started outside or from NetSuite with different starting records.
Starting record:: the system auto-defines the record ID. Use this option only if the process starts from the NetSuite record you want to pre-fill data from.
In case of manual setup, start by selecting an object field that must work as an identifier.
Then, select the value type that your object field has to match.
Value based on | Explanation |
Document field value | This option allows the bot to find records by matching the value in the specified object field with a corresponding value in a document field.
For example, if your document has a field that captures a record ID or name, the bot will search for records where the object field contains this value.
|
Signer details | This matching type uses the details the signer provides, such as their email, first name, or last name, to find a corresponding record in the object.
It’s useful for workflows where the signer’s identity must be cross-referenced with your system's records. |
Text input | This option allows you to manually enter a custom text value, which the bot will use to find a matching record in the object.
This is particularly useful when the value to be matched isn't defined by the document or the signer but is a specific input the workflow creator provides.
|
After that, provide the value that must match the object field, according to your choice.
Note: If you choose a document field as a lookup, remember to put your Trigger to Field changed.
You can add as many lookups as you need by clicking Add match.
Import
By default, all available NetSuite files will be imported.
If you want to limit imports to specific files, you can define filtering rules based on file attributes.
Create conditional rules to match specific document names.
Destination
In Import destination, select where to attach files. You can select multiple destinations.
Testing
In the Test section, check how the bot works by selecting Test. You will see a success message if everything is set up correctly. If there are issues, review the connection, mapping, or trigger configuration.
If you skip testing by selecting Skip testing, you may miss issues with the bot setup. Testing is recommended to ensure everything works as expected.
Conditions
Set conditions to control when the bot activates, tailoring it to your specific needs for more efficient automation. For detailed guidance, refer to this article.
Advanced settings
This section allows you to choose how the process proceeds in case the bot fails:
Select Proceed to allow the workflow to move to the next signer and automation if the bot isn't crucial.
Select Stop if the bot is critical; this prevents the next signer from receiving documents if data wasn't pre-filled from the source of your choice.