yesterday - last edited 11 hours ago
In many Archicad teams, publishing is still treated as a manual ritual:
Open the project → find the right publisher set → click Publish → wait → repeat next week.
@Tibor Lorantfy already automated this process.
Inspired by his work, I created a Python based tool (powered by Tapir Add-on) that turns the manual ritual into a fully automated, cross‑platform recurring publisher for Archicad — available on Windows and macOS for Solo and Teamwork projects.
Recurring publishing per publisher set
Configure any publisher set to run on a Daily, Weekly, or Monthly schedule at a specific time. Each row in the UI is a “project + publisher set + schedule” definition, so you can drive multiple workflows in parallel.
Safe job queue + live status
Jobs are queued and processed reliably, with a clear status line. So, you always know what’s running now and what’s still waiting.
Central publishing console
A table UI shows all configured jobs with project name, teamwork user, publisher set, time, recurrence, and last run date. You can add, edit, or remove schedules without touching Archicad’s publisher UI.
Automatic project lifecycle
The tool opens the correct Archicad project for each job, publishes using the selected set, and then either keeps Archicad open for the next compatible job or closes it.
Config import / export
All schedules (including project info, recurrence definitions and last-run dates) can be exported to JSON and imported again. That makes it easy to roll out standard publishing profiles across projects, machines, or offices.
Handling Dialogs on Windows and macOS
Automating publishing is only robust if dialogs are handled reliably. A single blocking dialog can stall an entire overnight run. On both platforms this tool ensures that scheduled publishing is not blocked by unexpected dialogs. This makes the automation suitable for real production use, not just idealized scenarios where nothing ever goes wrong.
50m ago
Sounds really useful.
Is this for a specific Archicad version or can it be used with several versions?