HubNext
Help
Help Management

Integrations

Integrations connect HubNext to external systems. Available connectors: Fizix Mate (sensor events: alarms, diagnoses, device connection), Fizix API (names instead of codes) Pulse (ticket numbers from support replies) and WhatsApp (Corta) (WhatsApp connection, connection check only for now).

Where to find it

Management → Integrations. Manager and above can see it; the Settings tab is available to Head and above only. The section shows cards of the connectors your system administrator has opened for you. If it is empty, no access has been granted yet. Click a card to open the connector: Events and Settings tabs (Log and Settings for Pulse).

How to connect Fizix Mate

  1. Open the connector, Settings tab, and click Create URL: the Webhook URL appears. Click Copy.
  2. Click Generate next to Secret Key, then next to API key. The value is shown only once, so copy it right away.
  3. In Fizix Mate open the webhook settings and enter the URL in Endpoint and the keys in API Key and Secret Key. Enable the notification types you need.
  4. Click Test in Mate and open the Events tab in HubNext: the test event should appear in the feed.

If you click Regenerate, the previous value stops working and must be replaced in Mate.

Events

The Events tab is the connector's event feed, newest first. Columns: Event (alarm, diagnosis or device connection), Device, Event type (for example vibration or temperature), State (normal, monitor, warning, danger), Connection (online or offline). Filters: Event, State, Device, period. Click a row to open the event: main fields, all event data, the raw JSON and other events of the same alarm (start, stage change, close). Event time is shown in UTC. The Download .md button exports the current selection (up to 1000 events) or, inside an event, that event — handy for an AI tool or a report.

The Organization column and filter show which Fizix organization the event came from.

Events report

The Report tab (next to Events) shows statistics grouped by Organization and Device: how many events in total and how many of each kind, by Event (alarm, diagnosis, connection) and by State (normal, watch, warning, danger). The period is Week (default, last 7 days), Month (last 30 days) or Period with the From date and To date you choose; you can limit the report to one organization. An organization row holds the totals of all its devices.

Fizix API: names instead of codes

The second connector of the integration is Fizix API. It pulls organization, system and device names from Mate, so events show more than codes.

  1. Open the Fizix API connector, Settings tab. Fill in API URL, API email, API password, API key (issued by Fizix support) and click Save.
  2. Click Synchronize. Organizations, systems and devices are loaded. Mate allows 50 requests per key per day, one synchronization uses 3, and you cannot repeat it more than once a minute.
  3. See the result on the Directory tab. After synchronization the feed shows the system under the device code, and the event card shows system, organization, device model and measurement point.

If synchronization fails, the reason is shown under the button (wrong credentials, limit, no connection). The previous data stays on error.

The Equipment monitoring page (Fizix portal) can be shown to people who do not have a HubNext account. Administrators have the Publish button right on the page.

  1. Pick an organization and click Publish: a short link like hubnext.cc/ab3xy9k appears.
  2. Enter an address in Viewer e-mail and click Add. The system creates a password and shows it once: copy it and pass it on yourself. The key button issues a new password, the trash button removes access.
  3. The person opens the link, signs in with the e-mail and password and sees a read-only page: just your one organization, with live data.

After five wrong passwords, sign-in for that e-mail is blocked for 15 minutes. Unpublish closes the link for everyone; Publish again brings back the same link.

WhatsApp via Corta

The WhatsApp (Corta) connector links HubNext to WhatsApp through the Corta Integration Hub gateway. For now it covers setup only: entering the keys and checking the connection. Receiving and sending messages will arrive in later stages.

  1. A system administrator creates the connector and opens it to your organization.
  2. A Head opens Management → Integrations, the connector, the Settings tab. The API address is already filled in; enter the Client ID and Client secret issued by Corta and press Save. The secret is not shown after saving: leaving the field empty on the next save keeps the old value.
  3. Press Check connection. If everything is fine you will see Connection works, the number of channels and the status of each WhatsApp channel (for example Active or Number authorization required). On failure the reason and Corta's response code are shown.

An "Access denied" error with the FORBIDDEN code means the integration is not yet activated at Corta: send them the Client ID.

Pulse: ticket number from the support reply

The Pulse connector reads the mailbox that receives support replies (for example an automatic confirmation with a case number) and writes the Redmine ticket number into the meta of the task the email was sent from. No need to copy the number by hand.

How it works:

  1. You email a task (the Send by email button in the task card).
  2. The support service replies with an automatic confirmation containing a case number.
  3. Every few minutes Pulse picks up new messages, finds the task the original email was sent from and writes the number into the redmine_task_id parameter on the Meta tab.

Matching is done by the reply to your email, so it works for emails sent from HubNext after Pulse was connected. Each message is processed once. If the task already has a different number, it is left as is and the log shows Conflict.

How to connect

There is one mailbox for all organizations: you do not set it up for each organization separately.

  1. A system administrator creates the Pulse connector (Admin → Integrations → Connectors) and ticks the organizations in Who can use the connector.
  2. Below, in Organization settings, leaves All selected organizations, fills in IMAP server, Port, Encryption, Login, Password and clicks Save. You can leave the rest: Folder defaults to INBOX, Sender domains to websky.tech, Address task emails are sent from to the login.
  3. Click Check connection: the number of messages in the folder is shown. Process now runs the processing without waiting. On the first run HubNext only marks the current position in the mailbox: old messages are not processed, only new ones.
  4. A Head of an organization opens Management → Integrations, the Pulse connector: they see the status and the Log tab. Mailbox settings and the check buttons are available to the system administrator only.

The number is written only into tasks of organizations that have the connector opened.

If you change the server, login, folder, port or encryption, processing starts again "from now".

Log

The Log tab (visible to Head and above) shows received messages: a Head sees only those linked to tasks of their organization, a system administrator sees all messages of the mailbox. It shows time, sender, subject, ticket number, task and Result. The Result filter and the search by ticket, task or address help you find a message. Message texts are not stored, and log entries are deleted after 90 days.

Results: Linked to task — the number was written; Already linked — the task already has this number; Conflict: the task has a different number — decide by hand; Skipped — the message is from another sender, the sender is not verified, there is no ticket number, the task was not found or the message is too large; Parse error — tell your administrator.

For the system administrator: Connector registry

Administration → Integrations → Connector registry lists all external connections of HubNext: who and where we connect to, what we receive and send, where it is used, which organizations have it set up and how often the exchange runs. No secrets are stored in the registry. A new connection is added to the registry first; the address and default polling frequency are taken from it.