Getting data in from Amadeus

There’s no native Amadeus connector in FeedbackRobot today. Rather than leave you guessing, here are the three routes that do work — in order of how well they hold up.

1. Trigger surveys from your own system (best)

If your team can make an HTTP request when a booking completes or a guest checks out, that’s the cleanest option. Generate a key under the Send Survey API skill and call it with the guest’s details.

You get exact control over timing — which matters more in travel than almost anywhere, because the right moment to ask is after the stay, not after the booking.

→ Triggering surveys from your own system

2. A webhook automation

If you use a middleware tool (Zapier, Make, or something internal) that can already see Amadeus events, point it at a Webhook trigger in the automation builder. You’ll get a URL and token to call; whatever you send becomes available to the rest of the workflow.

This is usually the fastest route if you don’t have engineering time.

→ Trigger reference

3. CSV import

Export guests periodically and import them.

Least elegant and entirely manual, but it works today and needs nobody technical. Fine for a monthly satisfaction survey; poor for anything that should follow a stay closely.

→ Importing your customer list

Timing, whichever route you pick

Survey after travel, not after booking. A trip booked in January for July shouldn’t trigger anything in January — a mistake that’s easy to make when the booking record is what your system hands you.

Decide who you’re surveying. One booking can cover several travellers. The person who booked isn’t always the person with an opinion. Pick one and be consistent, or your results mix two different populations.

Want this natively?

Tell us. Which systems get built next is driven by what customers ask for, and travel platform requests carry weight.