This is a paid bot, and its usage will be counted toward your plan's credits limit. For more information about credit usage, refer to this article.
How the Notify NetSuite contacts on documents opening bot works
Alert NetSuite contacts the moment recipients open your altaFlow documents. The bot pulls contact email addresses directly from NetSuite records — customer support reps, account managers, or project stakeholders — and sends notifications automatically without manual list management.
Use case example: In a customer support workflow, automate email notifications for NetSuite contacts each time a support ticket is initiated. The bot triggers email alerts, ensuring relevant contacts are promptly informed when a support ticket is opened.
How to set up
When the bot works by default:
The bot activates when the recipient opens the document.
Add the bot depending on your needs as described in this article. You may install this bot both in the step or in the All bots tab.
Find the Notify NetSuite contacts on documents opening bot in the list of bots and click Install bot.
Connection settings
To connect the bot to your NetSuite account, select Connect in the Connection settings 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.
Insert the values and click Apply.
Action settings
Select a NetSuite base record type. It can be any data available in NetSuite.
The related object is the same by default.
Select the email fields in the base record or related records which you intend to send notifications to from the dropdown list.
Customize the text of the message and indicate the document fields from which the variable data should be taken.
Adjust the starting NetSuite record. By default it is set to run the workflow from NetSuite using the custom button.
Find record option — set the bot to act only if All records or Any record match the conditions you've set.
Both option — the bot will try to use the NetSuite record ID sent by the integration app. If this record ID is unavailable, the bot will use a record found by the lookup.
Conditions
Set conditions to notify NetSuite contacts only in specific scenarios. Common use cases include:
Support tier routing: Notify Tier 1 support only when a "Priority" field equals "Low", and Tier 2 for "High" — routes engagement alerts to the right team.
Big-account tracking: Alert account managers only when the linked NetSuite customer has a specific segment (e.g., "Enterprise" or "Strategic accounts").
Skip internal opens: Add a "recipient email does not contain @yourcompany.com" condition to avoid noisy internal test opens.
First-open detection: Combine with document tags to fire only on the first open per document — great for engagement tracking without spam.
Learn more about bot conditions usage in the dedicated bot execution conditions article.
Advanced settings
Fine-tune how the bot alerts NetSuite contacts on opens:
Run frequency: The bot fires each time the document is opened by default. To fire only on first open, combine with a "document tag is empty" condition and add a tag on trigger.
Failure handling: If the NetSuite API is unreachable or the contact email is empty, choose whether to skip silently (workflow proceeds) or halt for admin review.
Document tags: Tag documents that triggered a NetSuite opening notification (e.g., "netsuite-opened") for audit trails and engagement analytics.
Learn more about adjusting Advanced settings in the bot setup glossary.