Case StudyAutomation & Integration

Nea Attiki Odos

Incident update automation

Nea Attiki Odos relied on Twitter as the main channel for informing drivers about road incidents in real time. The goal was to surface this information reliably and automatically on the official website.

Twitter APIZapierGoogle SheetsRSS/XML FeedCustom Logic

Key challenges

Single source

Twitter was the single source of incident updates

No alternative data source existed. Dependency was complete.

No API

No simple or stable feed was available for the website

A custom solution was needed to transfer data in real-time.

Real-time

Information had to be updated in near real time

A delay of a few minutes could affect thousands of drivers.

Platform Risk

Twitter introduced paid API access

The original free-tier access was removed, requiring a complete redesign.

Design goals

Resilience

Operate regardless of platform changes

Control

Full oversight of data flow

Flexibility

Easy adaptation to future changes

Solution evolution

Fetch latest tweets
Store in Google Sheets
Display via headline carousel

Worked reliably, but was directly dependent on Twitter API access.

Before & After

Before

Manual updates
Twitter dependency
No control
Downtime risk

After

Automatic updates
Platform independent
Full oversight
Zero downtime

Outcome

Website updated automatically
Information remained controlled
Dependency reduced
Adaptable solution

This project demonstrates how:

Business-critical problems are solved through proper architecture
Automation is not about tools, but about thinking
Solutions must be built to last

Do your processes depend on third-party platforms? Let's see how they can become more resilient.

5% of every collaboration goes back to humanitarian causes.