The challenge

The integrations run in n8n, but Administrate's operational teams should not need access to the n8n interface to understand whether a sync succeeded, which records were rejected or where an issue occurred. Native execution history alone did not provide the right visibility for business users.

The solution

We built a dedicated external logging workflow that is called after every batch written to Administrate. It turns technical execution data into an operational log and publishes it through Administrate's GraphQL API.

• Captures the integration, source system, object type, batch number, watermark and record totals.
• Classifies each batch as success, warning or failed from its written and rejected record counts.
• Publishes a concise message plus record-level details, including rejected records and reasons.
• Links successfully written records where available and caps detail views safely for large batches.
• Uses retry logic so a temporary logging failure does not silently remove operational visibility.

Results

• Administrate teams can review integration health from their own platform, without direct n8n access.
• Each batch has an auditable record of written, rejected and total records.
• Rejected records and watermarks provide the context needed to investigate exceptions quickly.