NEQTO Docs
  • Languages iconEnglish
    • 日本語
  • Docs
  • API
  • FAQ

›NEQTO Console

Getting Started

  • NEQTO Hello World!
  • Tutorial Step 1. NEQTO Console Setting
  • Tutorial Step 2. Device Settings & Launching Service (NEQTO Bridge)
  • Tutorial Step 2. Device Settings & Launching Service (STM32 Discovery)
  • Tutorial Step 2. Device Settings & Launching Service (SPRESENSE)
  • Tutorial Step 3. Application development using scripts

NEQTO

  • NEQTO Account Registration
  • Sub-accounts
  • API Usage
  • NEQTO Engine Firmware List
  • Support Guidelines
  • For safe and secure use of the NEQTO products
  • Vulnerability Disclosure Policy

NEQTO Console

  • Introduction
  • Fundamentals
  • Administrative Actions
  • Device Management
  • Linux-based Device Management
  • Batch Registration
  • Scripts
  • Actions and Contacts
  • View Data from the Console
  • NEQTO Apps

    • About NEQTO Apps
    • NEQTO Infinitypool
    • NEQTO Insights
    • NEQTO Custodia
    • NEQTO Flow
  • Machine Driver
  • Recommended Browsers
  • Billing Information

SPRESENSE

    Hardware Specifications

    • 01. About Spresense

    Software Specifications

    • 01. Operational Flow
    • 02. Initial Installation
    • 03. Spresense Wi-Fi Initial Setup
    • 04. Spresense LTE-M Initial Setup
    • 05. Debug Log Acquisition
    • 06. System LED Indications
    • 07. Event Messages
    • 08. Updating Firmware

    neqto.js

    • 01. About neqto.js
    • 02. Log
    • 03. Timers
    • 04. HTTP
    • 05. HTTPS
    • 06. MQTT
    • 07. Secure
    • 08. Storage
    • 09. Sleep
    • 10. RTC
    • 11. GPIO
    • 12. UART
    • 13. SPI
    • 14. I2C
    • 15. ADC
    • 16. GNSS
    • 17. Camera
    • 18. Utils
    • 19. nqSpresense
    • 20. nqService
    • 21. nqMqtt
    • 22. nqFOTA
    • 23. nqWiFi
    • 24. nqLte

STM32 Discovery

    Hardware Specifications

    • 01. About STM32 Discovery Kit (B-L4S5I-IOT01A)

    Software Specifications

    • 01. Operational Flow
    • 02. Initial Installation
    • 03. STM32 Discovery Wi-Fi Initial Setup
    • 04. Debug Log Acquisition
    • 05. System LED Indications
    • 06. Event Messages
    • 07. Updating Firmware

    neqto.js

    • 01. About neqto.js
    • 02. Log
    • 03. Timers
    • 04. HTTP
    • 05. HTTPS
    • 06. MQTT
    • 07. Secure
    • 08. Storage
    • 09. Sleep
    • 10. RTC
    • 11. UserSW
    • 12. GPIO
    • 13. UART
    • 14. SPI
    • 15. I2C
    • 16. ADC
    • 18. Utils
    • 19. nqDiscovery
    • 20. nqService
    • 21. nqMqtt
    • 22. nqFOTA
    • 23. nqWiFi

NEQTO Bridge

    Hardware Specifications

    • 01. NEQTO Bridge Module
    • 02. NEQTO Bridge Wi-Fi Module
    • 03. NEQTO Bridge LTE-1 Module
    • 04. NEQTO Bridge LTE-M/NB Module
    • 05. NEQTO Bridge IO Board
    • 06. NEQTO Bridge Digital IO Board
    • 07. NEQTO Bridge Connector Board

    Software Specifications

    • 01. Operational Flow
    • 02. NEQTO Bridge Wi-Fi Module Initial Setup
    • 03. NEQTO Bridge LTE Module Initial Setup
    • 04. Debug Log Acquisition
    • 05. System LED Indications
    • 06. Event Messages
    • 07. Updating Firmware

    neqto.js

    • 01. About neqto.js
    • 02. Log
    • 03. Timers
    • 04. HTTP
    • 05. HTTPS
    • 06. MQTT
    • 07. Secure
    • 08. Storage
    • 09. Sleep
    • 10. RTC
    • 11. UserSW
    • 12. GPIO
    • 13. UART
    • 14. SPI
    • 15. I2C
    • 16. ADC
    • 17. BLE
    • 18. Utils
    • 19. nqBridge
    • 20. nqService
    • 21. nqMqtt
    • 22. nqFOTA
    • 23. nqWiFi
    • 24. nqLte
    • 25. nqLAN
    • 26. nqEx

Linux-based device

    Software Specifications

    • 01. System Requirements
    • 02. Installation
    • 03. Software Configurations
    • 04. Operational Flow
    • 05. Debug Log Acquisition
    • 06. Event Messages
    • 07. Updating Software

    neqto.js

    • 01. About neqto.js
    • 02. Log
    • 03. Timers
    • 04. HTTP
    • 05. HTTPS
    • 06. MQTT
    • 07. Secure
    • 08. Storage
    • 09. RTC
    • 10. UNIXSocket
    • 11. FileSystem
    • 12. SubProcess
    • 13. SubTask
    • 14. Queue
    • 15. Utils
    • 16. nqLinux
    • 17. nqService
    • 18. nqMqtt
    • 19. nqFOTA
    • 20. nqLAN

neqto.js Libraries

  • About neqto.js Libraries
  • UART

    • GM65 Barcode Reader
    • SRF Ultrasonic Range Finder - Serial Mode

    I2C

    • HTS221 v2 Temperature and Humidity Sensor
    • LIS2DW12 v2 Accelerometer
    • SRF Ultrasonic Range Finder - I2C Mode
    • [Archive] HTS221 Temperature and Humidity Sensor
    • [Archive] LIS2DW12 Accelerometer

    Utils

    • RTC Alarm Synchronized Scheduler

    Integration

    • AWS S3 v2
    • AWS IoT Core v2
    • Azure IoT v2
    • [Archive] GCP IoT Core
    • [Archive] AWS S3
    • [Archive] AWS IoT Core

neqto.js Snippets

  • About neqto.js Snippets
  • DataDog
  • Dropbox
  • Google Sheets
  • InfluxDB
  • Oracle Cloud Object Storage
  • Salesforce
  • Splunk
  • Niagara
  • [Archive] SAP Cloud Platform Internet of Things

Release Notes

  • NEQTO Console Updates
  • NEQTO Firmware (Bridge Wi-Fi/LTE Module) Releases
  • NEQTO Firmware (STM32 Discovery Wi-Fi) Releases
  • NEQTO Firmware (Spresense Wi-Fi/LTE-M) Releases
  • NEQTO Engine for Linux Releases
  • neqto.js Libraries Releases

Actions and Contacts

Actions and contacts are accessed by several features in NEQTO and allow dynamic actions to be triggered, such as sending dynamic Slack messages or emails to whitelisted contacts.

Actions

A core value of IoT is the increase in speed in which businesses can react and respond.

Actions are triggered by various events in NEQTO Console, and include responses such as sending e-mails, sending Slack messages, or sending alerts to Salesforce.

NEQTO Spark charges per action performed. For more information, please refer to the Pricing.

For more information on the currently available action options, please refer to Action Types.

Before these event-driven systems can be used in NEQTO Console it is necessary to first register actions.

Regardless of type, all actions share the same meta data.

FieldDetail
Name (Required)Enter a name.
NoteEnter a description.
Action Type (Required)Select from the available action types.
  1. For the desired Group, access the "Actions" page. The link to this page is in the Group navigation menu.
  2. Click on the "Add Action" button in the upper-right hand corner.
  3. Input the required fields.
  4. Click "Save" to register the action.
  • It is possible to insert NEQTO Console information and data as dynamic content variables into actions.
  • Frequently used variables can be inserted from the buttons above the entry field. Clicking "more" will display additional options.

Dynamic Content

Some action types support the usage of variables, which in turn allow for dynamic content. You can select them from the toolbar.

Variable Toolbar

Common Variable List

VariableValue
{region}Region
{group_name}Group Name
{node_name}Node Name
{node_note}Node Note
{component_name}Component Name
{timestamp}Datetime of occurrence (UTC) ISO 8601 (Example: 2019-01-02T03:04:05+00:00)
{value}Sensor Value
{graph}Graph of the component
{event_type}When triggered by an event notification, the kind of event.
{event_level}When triggered by an event notification, the level or the event.
{event_message}When triggered by an event notification, the event message/details.

Special Variables

timestamp

Timestamps allow you to select a desired timezone to be used in the action's message. Example Case: Japan Timezone

{timestamp__Asia_Tokyo}
{timestamp__[TTIMEZONEHERE]} (Replace slashes with underscore)

unixtime

Unix/Epoch time values can also be accessed.

{unixtime} (Seconds)
{unixtime_ms} (Milliseconds)

graph

It is possible to specify graph links leading to other components on the same node. Please check the component list for correct parameters to specify.

{graph__3303_5700_0}
{graph__[OBJECTID]_[RESOURCEID]_[INSTANCEID]}

Action Types

There are several available action types. Information on the configurations of each type can be found below.

Mail

FieldDetail
To (Required)Please input the To destinations. ¹
CCPlease input any CC destinations. ¹
BCCPlease input any BCC destinations. ¹
Subject (Required)Please input the subject of the mail.
Body (Required)Please input the body of the mail.

¹ Only confirmed contacts can be selected. Please refer to the Contacts documentation for more information.

The Add Action screen, on the Action Settings tab, with the Mail Action type selected, displaying the auto-complete functionality with a partial text entry in the To: field

"To", "CC", and "BCC", are auto-complete enabled. When typing an email address, the text field will complete based on the confirmed contacts in the address book.

Slack

FieldDetail
URL (Required)Slack Webhook URL.
ChannelDesired channel to post message to.
MentionUsernames of members to mention. (Ex : @user.name)
Body (Required)The message to be transmitted.

Webhook

FieldDetail
URL (Required)The POST endpoint for the Webhook.
Token (Required)A token passed to payload that can be used for various purposes.
MethodOnly POST is supported. At present, the method value cannot be changed.

Currently, the generic Webhook provided sends a JSON payload via post to your endpoint that contains ALL of the following information.

The request header will be Content-Type: application/json.

{
  "domain": "string", // NEQTO Console URL
  "group_id": "uuidv4", // Group ID
  "group_name": "string", // Group Name
  "node_id": "uuidv4", // Node ID
  "node_name": "string", // Node Name
  "node_note": "string", // Node Note
  "value": "dynamic", // Component's date value
  "component_name": "string", // Component Name
  "resource_id": "number", // LwM2M Resource ID for the component
  "object_id": "number", // LwM2M Object ID for the component
  "instance_id": "number", // Instance of the component
  "timestamp": "number", // Epoch/Unix time of the data in seconds.
  "region": "string", // The NEQTO API region the action was triggered in
  "judge_name": "string", // When action is triggered by NEQTO Insights, returns the name of the judge that was triggered.
  "condition": "string", // When triggered by NEQTO Insights, the mathematical equation used.
  "event_type": "string", // When triggered by an event notification, the kind of event.
  "event_level": "number", // When triggered by an event notification, the level or the event.
  "event_message": "string", // When triggered by an event notification, the event message/details.
  "token": "string" // The data you enter in the "token" field. Can be anything you like.
}

Salesforce

It is possible to send "Alert" data to Salesforce, enabling various business divisions and sales teams to act on IoT Data. To use the Salesforce Integration, a Salesforce account and custom object are required.

FieldDetail
Username (Required)Salesforce Username. ²
Password (Required)Salesforce Password. ²
Object Name (Required)Name of the custom object to send to in the Salesforce environment.
Body (Required)The Salesforce API payload. Map to Salesforce environment by YAML.

² As per security best practices, please use a Salesforce sub-account with minimal permissions.

Example Body:

Component__r:
  external_id__c: "{node_name}-{component_name}"
Thing__r:
  external_id__c: "{node_name}"
message__c: {value}
Code__c: "{judge_name}"
Priority__c: "High"
Timestamp__c: {unixtime_ms}

Contacts

In order to prevent misuse of email, NEQTO Console utilizes a mutual whitelist system for all email notifications.

Before it is possible to utilize email notifications, both parties must approve.

To add a a recipient:

  1. For the desired Group, access the "Contacts" page. and in the upper-right hand corner click the "Add Contact" button.
  2. Input the email of the desired recipient.
  3. Click "Save".

The Add Contact screen

In the "Contacts" resource page, the status of the email addresses will be displayed.

The Contacts list

Shortly after entering a new contact, the new contact will receive a confirmation e-mail. Contacts who have not yet clicked the confirmation link in their email will be listed with the "Pending" status. Newly added contacts will need to access the confirmation link within 24 hours, otherwise the process will need to be repeated.

After clicking the confirmation link, the status of the contact's email address will be updated in the "Contacts" page. When a contact's email address has been registered successfully, the status will be "Confirmed".

To delete a contact/email address from contact page click the "X" icon to the right of the email, then input the email to confirm deletion.

  • Upon deleting a contact, the deleted contact will no longer be able to receive e-mail from any event notifications or notifications from NEQTO Insights.

Updated: 2023-01-13
← ScriptsView Data from the Console →
  • Actions
  • Dynamic Content
    • Common Variable List
  • Special Variables
    • timestamp
    • unixtime
    • graph
  • Action Types
    • Mail
    • Slack
    • Webhook
    • Salesforce
  • Contacts
AboutNewsProductsFAQPrivacy PolicyVulnerability Disclosure Policy
NEQTO Console
IntroductionFundamentalsAdministrative ActionsDevice Management NEQTO Apps
NEQTO Bridge
NEQTO Bridge ModuleNEQTO Bridge Wi-Fi ModuleNEQTO Bridge LTE-1 ModuleError Logging Event Messages
API Documentation
API UsageGlobal APIRegional APIAPI Terms of Service
Jigsaw, Inc.
© 2025 JIG-SAW INC.