Integration

Foundation CMS and Time Hive

Time Hive keeps an honest ledger of the time automations save; Foundation CMS puts that number on a website. On swarmlabs.io the home page's counter of minutes recovered is a Foundation CMS entry that a workflow updates from Time Hive every five minutes.

Overview

This integration connects Foundation CMS with Time Hive, Swarm Labs' automation ROI ledger. Foundation CMS is Swarm Labs' multi-tenant content management system on Cloudflare Workers. It holds a site's content and hands it to the site as whole, typed records, and every site runs as its own Worker with its own database and media bucket. Time Hive logs every automation run as an immutable record and turns it into one number: the time automations save.

Business Context and Core Use Case

A claim like "our automations save hundreds of hours" is more convincing when the number is live and comes from a ledger rather than a slide. Showing it on a website usually means hard-coding it and forgetting to update it. With Foundation CMS the figure is content, held as an entry the site draws, and an automation keeps it current.

The Applications Involved

Time Hive (Time Hive) holds the ledger and the running total.

Foundation CMS (Foundation CMS) holds the figure as an entry and the site draws it; the home page's counter and progress bar follow it.

How the Integration Works

A scheduled n8n workflow reads Time Hive's total every five minutes. When it has changed, the workflow updates the figure's entry through the Foundation CMS content API, with a key that belongs to that one site. The site reads the entry like any other content, so the next visitor sees the new number.

Immediate Operational Value

The number on the site is never stale and never invented: it is the ledger's figure, a few minutes old at most. Because it is ordinary content, editors can change how it is presented without touching the automation.

Security, Access, and Governance

The workflow's key belongs to one site and carries only the abilities given to it, and a key can be limited to the figure's content type alone. Writes are skipped when the number has not changed, and each one records a revision.

Summary

Time Hive counts the time automations save; Foundation CMS shows it, live, as content the site already knows how to draw.

Frequently asked questions

Is the number on the website live?

It is updated every five minutes from Time Hive, whenever it has changed.

Can the automation change anything else on the site?

Only what its key allows. Keys are scoped to one site and to named abilities, and can be limited to the figure's content type alone.

Can editors restyle the counter?

Yes. The figure is ordinary content, so its presentation is the site's, separate from the automation.

Want Foundation CMS and Time Hive
wired up for you?