BUSINESS & OPERATIONS
Connect your back office,
marketing and CRM.
Agree the connection your team needs
Explore back-office, marketing and CRM connections, then check what information moves between the systems. Our implementation notes below explain the documented webhook flow and the limits to plan around.
Integrations
17 tools
Documented setup
Sources below
Plan the connection
check the workflow
WHY IT MATTERS
Make the handover clear
Agree the data, trigger and owner for each connection so your team knows what should happen next.
Keep the tools you know
Start with the systems you already use. Confirm compatibility and the work needed to connect them before planning a replacement.
Name the source of each record
Agree where the customer or booking record is maintained. This helps your team resolve differences between systems.
Built to connect
Use the documented connection methods as a starting point, then test the complete workflow with your integration team.
THE INTEGRATIONS
Explore the connection directory
The existing directory lists the tools below. Confirm the supported data, direction and account requirements for each connection before relying on it.
Back-office integrations
4 tools
eTrip Agency
Travelworks
SinGs
PenAir by Penguin
Marketing tools
6 tools
Luna Marketing
Constant Contact
GetResponse
Mailchimp
MailerLite
Brevo
CRM
3 tools
Other tools
4 tools
Webhooks
Zapier
rePUSHTI
Rewardful
What moves between systems?
A connection should answer a working question: what information is sent, when is it sent and who handles a failed update? Use the supplier directory below to explore options, then agree the data flow for your business.
The published webhook documentation describes notifications sent from Travelgenix to an endpoint you configure. The message contains a summary of an event, with a route to retrieve more detail. It is not automatically a full customer or booking record.
Events in the current documentation
The documented events cover customer creation and updates, basket creation, completed orders and cancellations. Completion means paid and confirmed; cancellation can be full or partial. The documentation explicitly marks order.update as not implemented.
That distinction matters if your back-office team expects every amendment to arrive automatically. Agree another supported process for changes before relying on the connection.
An example connection brief
Suggested scenario: pass a completed booking to your back-office workflow. First name the destination system and the person who owns it. Next map the booking reference, status and other required fields. Then test how a cancellation will be reflected.
Keep this as a proposed workflow until the integration team confirms the available fields, permissions and destination behaviour. A directory listing does not prove that every field flows both ways.
Check identity, failures and ownership
Agree the identifier that links records so a repeated message does not create a second customer or booking. Ask how failures are noticed and retried, and who investigates a missing update. These checks make the operational handover clear.
The webhook guide describes optional request signing. Ask your integration team to configure and validate it where appropriate, and to agree how access is managed.
Connect and test with your own credentials
The supplier setup guide shows adding the supplier-issued credentials, saving them and using Test. Confirm the commercial account and permitted products as part of onboarding. A successful credential test is one step; your end-to-end workflow still needs checking.
Where Luna Work fits
The inbox, smart segments and Customer 360 are available to Travelgenix clients. Your account manager can confirm access for your business. The Quick Quote walkthrough describes sent quote history appearing on the customer record when Luna Work is switched on. Notes, costs and private quote links stay in Quick Quote.
Explore Luna Work or book a walkthrough of the connection you need.
Sources and review
Reviewed on 20 October 2026. Product descriptions refer to the public documentation linked below. Suggested checks are Travelgenix’s practical guidance, not measured customer results.
Tell us which systems you use and what you need to pass between them. We will discuss the supported workflow and the checks before launch.