Why I Built a Nezasa-to-SharePoint Automation Without Being a Systems Architect

Key takeaway: Manual Nezasa/TripBuilder data entry is a solvable operations problem, not a software-budget problem. A Nezasa-to-SharePoint automation built on Make.com and the public Nezasa Bookings API eliminates manual copy-paste entirely, without new software, IT staff, or an engineering background. This automation has run in production at a live DMC since its build and processes bookings of any volume with the same effort.

What problem does manual Nezasa data entry cause for DMCs?

Manual data entry between Nezasa and internal tools like SharePoint or Excel causes lost visibility on payment due dates, duplicated work between operations and finance, and booking errors that surface only after a supplier confirmation is missed. At Andes Viva, this meant operations staff retyping hotel dates, transfer times, and supplier references from Nezasa into a spreadsheet for every single booking component — a task that scales linearly with booking volume and has no natural ceiling.

The deeper cost isn’t the time spent typing. It’s the delay between a booking changing in Nezasa and that change being visible to the people who need it — finance tracking a payment deadline, operations confirming a transfer, or management trying to get a volume overview without logging into Nezasa directly.

How did the automation start at Andes Viva?

The automation started as an internal fix for a six-year-old operational pain point, not as a planned product. After years of watching finance chase supplier confirmations and operations manually retype booking data from Nezasa into SharePoint, the same recurring bottleneck — the delay between a Nezasa change and that data reaching the team — became the specification for what to automate.

There was no external brief, no requirements document handed down by a client. The problem was lived firsthand, inside the same company that later became the proof the solution works.

What does the Nezasa-to-SharePoint pipeline actually do?

The pipeline listens for booking events from Nezasa via webhook, retrieves the full booking record — including every service component and amenity — through the Nezasa Bookings API, and writes that data directly into a SharePoint list, creating new rows for new components and updating existing rows without duplication.

Stage	What happens
Trigger	Webhook fires on booking create/update in Nezasa
Fetch	HTTP GET to Nezasa Bookings API (v1.13) pulls full booking + components + amenities
Process	Each component (hotel, transfer, activity, car rental) is mapped individually
Write	SharePoint list item created or updated by matching on a unique component ID
Cleanup	Components removed from Nezasa are detected and deleted from SharePoint automatically

Do you need to be a developer to build this?

No — building this pipeline required no computer science background and no formal automation certification, only a working understanding of the booking workflow and the willingness to read the Nezasa API documentation. The technical build uses a no-code automation platform (Make.com); the difficult part was never the code, it was knowing exactly which fields operations and finance actually needed.

This matters for any DMC evaluating whether to build something similar in-house versus paying for a certified enterprise tool: the barrier to entry is domain knowledge of your own booking workflow, not a software engineering degree.