When using template based releases

How to integrate external content when your itinerary is defined in GUIBO — so your external system stays the single source of truth.

When to use this

You manage routes, POIs, or text content in a third-party system and want to use that data as building blocks in GUIBO to manage your guidebooks.

Continue reading here, when you are not only managing assets in a third party system but also managing the trip structure on a booking level in another system (so you do not need to manage guidebooks in GUIBO).

Your situation	What to do
Routes managed in another geo system	Sync routes into a GUIBO library via API
Hotels/POIs managed in a booking system	Sync POIs into a GUIBO library via API
Text content managed in a CMS	Sync text pages into a GUIBO library via API
Some content external, some in GUIBO	Libraries managed in GUIBO and synced libraries work side by side — libraries behave identically regardless of how they were filled
All content managed in GUIBO	No integration needed

How it works

Your external content is synced into GUIBO libraries. These libraries feed into your guidebooks — just like manually managed content.

External system → Sync → GUIBO libraries → Guidebooks → Personlaized Releases (per booking)

Step 1: Sync your content into libraries

Set up a nightly sync that pushes routes, POIs, and text pages from your external system into GUIBO libraries.

See Set up library sync for the complete setup.

Step 2: Build guidebooks from synced libraries

Guidebooks pull content from libraries through two methods:

Method	Used for	How it works
Manual referencing	Routes	Import specific routes from a library into each day/stage category
Dynamic referencing	POIs	Connect a POI library to a guidebook — GUIBO automatically imports all POIs near the routes

Both methods create references, not copies. The guidebook always reads the current version from the library.

Typical setup per guidebook:

1. Create day/stage categories (Day 1, Day 2, …)

2. Import routes per category via manual referencing from your routes library

3. Connect your POI libraries — GUIBO pulls relevant POIs via dynamic referencing

See Create your first guidebook for the step-by-step walkthrough.

What happens when content changes in an external system

Because guidebooks reference library content, every change in a library is automatically reflected in all connected guidebooks:

What changes in the library	What happens in guidebooks
Route updated	All guidebooks referencing that route show the updated version
POI added	Dynamically referenced guidebooks pick up the new POI if it is near a route
POI removed	Dynamically referenced guidebooks no longer show the removed POI
POI updated	All guidebooks referencing that POI show the updated version
Text page updated	All guidebooks referencing that text page show the updated version

No manual updates to individual guidebooks required.

Step 3: Create releases per booking

Once your guidebooks are set up, create releases per booking — via the web portal or automated via API.

See How to publish for the API documentation.