Skip to content
Private BetaGet Early Access Get Early Access

Integrations and Data

Updated 2026-08-165 min read

Integrations allow INTERA to use information from the business systems your company already relies on.

They connect INTERA with external applications, databases, files, and data services so that Assets, Metrics, Dashboards, and Role Packages can use relevant business information.

What Is an Integration?

An Integration is a connector that allows INTERA to communicate with a specific type of external system.

An Integration defines:

  • how INTERA connects;
  • which authentication methods are supported;
  • which settings are required;
  • which DataSources are available;
  • which filters and functions are supported;
  • how errors are reported.

Examples include accounting systems, billing platforms, CRM systems, databases, banking APIs, and external data services.

Integration Module and Integration Instance

An Integration Module is the installed connector.

An Integration Instance is one configured connection created from that module.

For example:

Integration Module:
Microsoft Business Central

Integration Instances:
Business Central Production
Business Central Test

Each Integration Instance may have its own:

  • server address;
  • credentials;
  • tenant or company;
  • account;
  • configuration.
Create an Integration Instance

To create a connection:

  1. Go to Settings → Integrations.
  2. Select Add Integration.
  3. Choose the required Integration Module.
  4. Enter a clear name.
  5. Enter the connection and authentication settings.
  6. Complete any Integration-specific parameters.
  7. Save the Integration Instance.
  8. Test the connection.

The exact configuration depends on the selected Integration.

Use dedicated service credentials where possible.

What Is a DataSource?

A DataSource is a structured set of information made available by an Integration.

Examples include:

  • invoices;
  • payments;
  • customers;
  • tickets;
  • balances;
  • network alarms;
  • bank transactions.

An Integration may provide multiple DataSources.

Each DataSource defines:

  • available fields;
  • supported filters;
  • supported parameters;
  • the business information it can provide.
DataSource Fields and Filters

Fields are the values available from a DataSource.

For an invoice DataSource, fields may include:

  • invoice number;
  • customer;
  • issue date;
  • due date;
  • amount;
  • status.

Filters limit the information used by INTERA.

Examples include:

  • customer;
  • status;
  • currency;
  • region;
  • date range;
  • billing period.

Always configure filters according to the intended business definition.

Using Integration Information

Information supplied by Integrations may be used by:

  • Assets;
  • Metrics;
  • Dashboards;
  • Role Packages;
  • other supported INTERA functions.

For example, an Integration may provide information used to populate Asset fields or calculate a Metric.

Detailed configuration is covered in the Assets and Data Modelling and Metrics chapters.

Metrics and DataSources

A Metric may use:

  • an Integration Instance;
  • a DataSource;
  • filters;
  • a result field;
  • an aggregation or calculation;
  • a time context.

For example:

Metric:
Total Overdue Balance

DataSource:
Invoices

Filters:
Status = Unpaid
Due Date < Today

Operation:
Sum

Common aggregation methods include:

  • count;
  • sum;
  • average;
  • minimum;
  • maximum.
Time Context

Many business values depend on a specific period.

Examples include:

  • today;
  • current month;
  • previous month;
  • billing period;
  • accounting period;
  • custom date range.

The intended period should always be defined explicitly.

Terms such as current period or recent data should only be used when their meaning is clearly defined.

Synchronization

Synchronization updates configured INTERA information using connected Integrations.

Depending on the configuration, this may update:

  • Asset information;
  • Metric values;
  • status;
  • timestamps;
  • Metric history.

Metrics may use the INTERA system default schedule or define their own update schedule.

Where supported, an administrator can also run an update manually.

Data Status

INTERA may show the technical status of synchronized information.

Typical states include:

  • Valid — the latest update completed successfully;
  • Delayed — the information has not been updated within the expected period;
  • Synchronization Error — the latest update failed;
  • Permanent Error — configuration requires administrator action;
  • Disabled — automatic updates are turned off.

Always consider both the value and its last-update status.

Data Validation

A successful connection does not automatically mean that the business result is correct.

When configuring a new DataSource or Metric, verify:

  • the correct fields are used;
  • filters are correct;
  • the time period is correct;
  • aggregation is correct;
  • currency and units are correct;
  • the result matches the source system.

Start with a simple test case before expanding the configuration.

Identifiers

Different systems may use different identifiers for the same business concept.

Where configuration depends on identifiers, use stable business or system IDs whenever possible.

Avoid relying on display names where a more reliable identifier is available.

Detailed Asset modelling is covered in Assets and Data Modelling.

Data Quality

INTERA depends on the quality of information supplied by connected systems.

Common issues include:

  • missing values;
  • duplicate records;
  • incorrect dates;
  • inconsistent statuses;
  • currency differences;
  • inconsistent business periods.

Where possible, source-data problems should be corrected in the system responsible for that information.

Data Security

Integrations may access sensitive business information.

Recommended practices include:

  • use dedicated service accounts;
  • grant only required permissions;
  • protect credentials;
  • use encrypted connections;
  • review access regularly.

Do not expose passwords, API keys, tokens, or certificates in visible Dashboard content or documentation.

Write-Back Capabilities

Some Integrations may provide supported write-back forms or other controlled actions.

Availability depends on the specific Integration.

The Integration defines:

  • which actions are supported;
  • which fields can be submitted;
  • required permissions;
  • validation;
  • error handling.

Write-back support does not mean that every connected system can be edited through INTERA.

Common Problems

Connection Fails

Check:

  • server address;
  • credentials;
  • network access;
  • firewall;
  • certificate;
  • external service availability.
DataSource Returns No Data

Check:

  • filters;
  • selected period;
  • company or account;
  • permissions.
Metric Result Is Incorrect

Check:

  • field;
  • aggregation;
  • period;
  • currency;
  • business definition.
Information Is Delayed

Check:

  • last-update time;
  • synchronization status;
  • Integration status;
  • update schedule.

Recommended Configuration Sequence

When connecting a new system:

  1. create the Integration Instance;
  2. enter connection and authentication settings;
  3. test the connection;
  4. review available DataSources;
  5. select the required fields and filters;
  6. define the required time context;
  7. configure the Asset or Metric;
  8. run a test update;
  9. compare the result with the source system;
  10. add the information to a Dashboard.

Best Practices

  • Use clear names for Integration Instances.
  • Keep business logic explicit.
  • Use stable identifiers.
  • Start with simple test cases.
  • Check data freshness.
  • Revalidate important configurations after source-system or Integration changes.

Naming changed in v0.003
KPI is now Metric across the product and the docs. Existing roles were migrated automatically; saved dashboards keep working.
What are your Feelings