Skip to content
Nappai Documentation

Amadeus Api Toolkit

The Amadeus Api Toolkit lets you add travel‑related search capabilities to your Nappai workflows. Pick the tools you need—such as flight search or hotel search—set a default currency and language, and the toolkit will handle the rest. It’s a ready‑made bridge to the Amadeus Travel API, so you can focus on building your automation rather than writing API calls.

How it Works

When you add the component to a workflow, you choose which Amadeus tools you want to use. The component then creates a small “toolkit” that contains the selected tools. Each tool knows how to talk to the Amadeus API using the credentials you provide. The toolkit is returned as a BaseToolkit object, which can be passed to other components that expect a toolkit (for example, a language‑model component that can call the tools).

The component does not perform any API calls itself; it only builds the toolkit. The actual API requests happen when the toolkit’s tools are invoked later in the workflow.

Inputs

This component requires a credential of type Amadeus Travel API.
How to set it up

  1. Go to the Credentials section of Nappai and add a new credential of type Amadeus Travel API.
  2. Enter your Amadeus Client ID and Amadeus Client Secret (you can get these from https://developers.amadeus.com/get-started).
  3. In the component, select the credential you just created in the Credential field.

Input Fields

  • Default Currency: Select the default currency for the API.
  • Default Language: Select the default language for the API.
  • Selected Tools: Choose which Amadeus tools you want to include in the toolkit (City Search, Flight Search, Hotel Search, Location Search, Activity Search, Airport Search).

Outputs

  • BaseToolkit: A BaseToolkit object that contains the selected Amadeus tools. This output can be fed into other components that accept a toolkit.

Usage Example

Below is a simple example of how you might use the toolkit in a workflow that searches for flights and hotels.

  1. Add the Amadeus Api Toolkit component.
  2. In the Credential field, select the Amadeus Travel API credential you created.
  3. Set Default Currency to USD and Default Language to en-US.
  4. In Selected Tools, check Flight Search and Hotel Search.
  5. Connect the BaseToolkit output to a Language Model component that calls the tools.
  6. In the language model prompt, ask for flight and hotel options for a given destination and date range.

The language model will use the toolkit to call the flight and hotel search tools, and you’ll receive the results directly in the workflow.

  • Amadeus Flight Search Tool – Performs flight availability queries.
  • Amadeus Hotel Search Tool – Retrieves hotel listings and rates.
  • Amadeus City Search Tool – Looks up city information.
  • Amadeus Location Search Tool – Finds geographic locations.
  • Amadeus Activity Search Tool – Searches for local activities and tours.
  • Amadeus Airport Search Tool – Retrieves airport details.

Tips and Best Practices

  • Choose the right currency: Set the default currency to match the currency used by your customers to avoid conversion confusion.
  • Limit the tools: Only select the tools you need; this keeps the toolkit lightweight and reduces unnecessary API calls.
  • Use mapping mode (if available in future updates) to feed dynamic values into the currency or language fields from earlier steps in the workflow.
  • Test with a small dataset first to ensure the API responses are as expected before scaling up.

Security Considerations

  • Credentials are stored securely in Nappai’s credential store and are never exposed in the workflow UI.
  • The component only passes the credential reference to the toolkit; the actual API keys are never displayed.
  • Make sure to restrict credential access to authorized users only.