← BACK TO ALL USE CASES
Data from Multiple Pages & Sources

Automatically enrich a manufacturing issue log with product data from CSV

Context and Challenge

A manufacturing team uses a native Confluence table as a digital logbook for problems on the production floor. Employees record the article number and a description of each issue. Article names are stored separately in a CSV product catalog.

As a result, the Confluence issue log contains article numbers but no corresponding names. Without connecting the two tables, anyone reviewing the log has to manually search the product catalog for each article number and copy the article name into the report.

Result

The issue log is automatically enriched with data from the CSV product catalog.

How it is built

Table from CSV brings the product catalog with article numbers and article names into Confluence. The native Confluence issue log and Table from CSV are placed inside Table Transformer. The Lookup Tables preset matches the two tables using the shared Article number column and automatically adds the corresponding article name to the issue log.

THE APP MACROS USED

  • Table from CSV
  • Table Transformer
← BACK TO ALL USE CASES

Similar use cases

Data from Multiple Pages & Sources

Build a dynamic catalog of 550+ APIs from Confluence and Jira data — instead of maintaining an Excel table

Turn 550+ API pages and related Jira data into a searchable, self-service catalog instead of maintaining one error-prone Excel table.

VIEW CASE → Data from Multiple Pages & Sources

Build a data-backed dashboard for 1-on-1 meetings

Bring time-tracking and Jira data into one Confluence page to use as a shared reference during 1-on-1 meetings.

VIEW CASE →

Level up the way your team works in Confluence

Turn your Confluence space into a single source of truth, reduce manual work and copy-paste, and create the visibility your team and stakeholders need.

TRY FREE (opens in a new tab)