Demo
Skip to main content
< All Topics

mTrip × Zapier — Quick Start Guide

Zapier is an automation platform that connects your apps and moves data between them using simple workflows called Zaps. Each Zap has a trigger (something that happens in one app) and one or more actions (what Zapier does in other apps).
With the mTrip Zapier app, you can automatically:

– Create trips in mTrip when something happens in another system (e.g., a booking is confirmed in your CRM).
– Add travelers to mTrip from form submissions or spreadsheets.
– Attach documents and trip information documents to trips as part of your workflow.
– Delete trips when a record is canceled or removed upstream.

 

This lets non-technical users build reliable, no-code workflows—so your mTrip data stays in sync with the tools you already use.

Support policy

We do not provide support for Zapier. This guide is provided “as is.” For platform questions or issues, please use Zapier’s help resources.

Prerequisites

  • You must have access to Account Settings on the mTrip platform to retrieve your API ID and API key.
  • In Zapier’s editor, click the “i” icon next to any field to see help text (allowed values, examples, notes).

1) Add the mTrip app to a Zap & connect your account

  1. Create a Zap in Zapier and choose mTrip API as the action app.
  2. When prompted to connect, enter:
    • Region (US or EU) – select US if you are using Trip Agent
    • API ID (from your mTrip Account Settings > Connectivity)
    • API Key (from your mTrip Account Settings > Connectivity – raw, not Base64)
  3. Save the connection.

2) Available Actions

A) Create a New Trip

Minimum required at the top of the form:

  • Trip / Name
  • mTrip Account ID
  • Start date and End date (ISO 8601 datetimes, e.g., 2025-10-01T10:00:00Z)

Optional sections (only sent if you fill them): Travelers, Destinations, Flights, Accommodation, Car Rental, Train, Transport, Activity, Documents, Trip Information Documents.

Conditional requirements (only if you start that section)
  • Flight: Departure date, Airline IATA, Flight number, Departure city, Arrival city. Based on this minimal information, our system will automatically add airport, terminal, duration, aircraft. If “Active for every traveler” is false, include traveler details with at least one traveler_identifier, use it if you need to add specific information for each traveler, eg seat or if some travelers are not on the flight.
  • Accommodation: Name, From date, To date, City. If not active for every traveler, include traveler details (traveler_identifier).
  • Car Rental: Pickup date/city and Dropoff date/city. If not active for every traveler, include traveler details.
  • Train: Departure date, Departure city, Arrival city. If not active for every traveler, include traveler details.
  • Transport: Transport type, Departure date, Departure city, Arrival city. If not active for every traveler, include traveler details.
  • Activity: Date, Name, Period. If not active for every traveler, include traveler details.
Documents (top-level)

If you enter anything in a Documents row, then these are required for that row:

  • URL (must start with https://)
  • Name

Optionally add Traveler IDs as a comma-separated list per row (e.g., 123,23132).

Trip Information Documents

If you enter anything for a row here, these are required:

  • Document name
  • Type (one of: text | link | file)

Position defaults to before if left blank. Allowed values are before or after. If you provide URL or File URL, they must start with https://. You may also include Template IDs; the app only sends the block when templates and/or documents are provided.

B) Create Traveler

Required: First name, Last name, Identifier. Other fields (email, phone, language, etc.) are optional. The action sends an array with a single traveler object to /v1/travelers.

C) Delete Trips

Required: Trip Identifier(s) (add one per line). The action sends a JSON array like [{ “identifier”: “12345” }] to /v1/trips using DELETE.

3) Field Help (“i” icons)

In the Zap editor, many fields include help text with examples, allowed values, and notes. Click the “i” icons to read these before mapping your data.

4) Data formats & tips

  • Datetimes: Use ISO 8601 (YYYY-MM-DDThh:mm:ssZ), e.g., 2025-10-01T10:00:00Z.
  • Booleans: true / false.
  • Integers/Numbers: Use numeric values (e.g., duration in minutes).
  • Section behavior: If you don’t fill any field in a section, that section won’t be sent to the API.

5) Testing

Use Zapier’s Test button in the action step to send your current inputs to the mTrip API and see the result. If the test fails, check the error text and verify you met the conditional required fields for any section you started.

mTrip does not provide support for Zapier.

More posts