X1 FBO Email Integration
Stop manually entering trip details from X1 FBO handling confirmation emails. AirPlx reads those emails automatically — extracting tail numbers, aircraft types, operators, and arrival/departure times — and creates trips on your schedule in under two minutes. Less data entry, fewer typos, faster turnaround.
How It Works
Handling email Parses email
X1 FBO ---------------> AirPlx ---------------> Trip
System (CC/BCC/fwd) Inbox auto-creates Created- A handling request is created in X1 FBO (e.g., for an arriving aircraft)
- X1 FBO sends a request confirmation email
- A copy of that email is sent to your AirPlx ingestion email address
- AirPlx parses the email and creates the trip with all the details filled in
- The trip appears on your schedule, ready to manage
Your Ingestion Email Address
Every AirPlx FBO has a dedicated ingestion email address in this format:
ingest+{your-slug}@airplx.comThe slug (your FBO’s unique identifier) is assigned when your FBO is set up. For example, if your slug is miami-ops, your ingestion email address is:
ingest+miami-ops@airplx.comYou can find your slug in Settings > Configuration under the Email Ingestion section, or contact AirPlx support if you need help locating it.
The slug must be exact. A single typo in the ingestion email address means emails will silently fail to reach your FBO — there is no bounce or error notification.
Setup
Set Your Timezone
X1 FBO sends arrival and departure times in local time. AirPlx needs your timezone to convert these correctly to UTC.
- Go to Settings > Configuration
- Find the Timezone field
- Select your FBO’s local timezone (e.g.,
America/New_York,America/Chicago) - Save your changes
If your timezone is not set, times will silently default to UTC, which will make every arrival and departure time incorrect. Always set your timezone before enabling the integration.
Select X1 FBO as Your FBO System
- Go to Settings > Configuration
- Enable Email Ingestion (toggle must be on)
- Find the FBO System dropdown
- Select X1 FBO
- Save your changes
This tells AirPlx to use the X1 FBO email parser for incoming emails, ensuring dates, tail numbers, and other fields are extracted correctly.
Configure X1 FBO to Send Emails to AirPlx
You need X1 FBO to send a copy of request confirmation emails to your AirPlx ingestion email address. There are two ways to do this:
Option A: BCC in X1 FBO (Recommended)
In X1 FBO:
- Navigate to Notifications > Settings (or your email configuration area)
- Add your
ingest+{slug}@airplx.comaddress as a BCC recipient for request confirmations - Save the settings
If you’re using SendGrid for outbound email, you can also configure a BCC address at the SendGrid level. Contact your X1 FBO administrator or X1 FBO support for the exact steps — the navigation may vary depending on your X1 FBO configuration.
Email deliverability note: X1 FBO uses SendGrid to send emails. If emails aren’t being delivered, check with your X1 FBO administrator that SendGrid is properly configured with valid SPF and DKIM DNS records.
Set a Default Location (Optional)
You can configure a default hangar or ramp where all email-ingested trips are automatically assigned. This is useful if most incoming aircraft go to the same location.
- Go to Settings > Configuration
- Find the Default Assignment Location field under the Email Ingestion section
- Select a hangar or ramp
- Save your changes
You can always reassign a trip to a different location after it’s created.
Verify It’s Working
- Have a request confirmation sent from X1 FBO (or ask your administrator to send a test)
- Wait about 60 seconds — AirPlx checks for new emails once per minute
- Check your AirPlx schedule — the trip should appear automatically
- If the trip doesn’t appear, check the Operations Inbox for items queued for review (see Queued for Review below)
What Gets Imported
Each X1 FBO request confirmation email creates a trip with the following details:
| Field | Description | Example |
|---|---|---|
| Tail Number | Aircraft registration | N456JS, N789KL |
| Aircraft Type | ICAO type code | G280, CL35, GL7T |
| Operator | Operating company name | Jet Aviation, NetJets |
| Arrival | Arrival date/time (local, converted to UTC) | 02/15/2026 10:30 AM |
| Departure | Departure date/time (local, converted to UTC) | 02/17/2026 03:00 PM |
| Request Number | X1 FBO’s internal reference | MIA-4521 |
Email Format Examples
Below are examples of the emails AirPlx processes from X1 FBO. These are the request confirmation emails that X1 FBO generates.
Example 1: Standard Trip (Arrival + Departure)
The most common scenario — an aircraft arriving and departing on known dates.
Email received:
From: notifications@x1fbo.com
Subject: Request Confirmation - MIA-4521
Request Confirmation
Request #: MIA-4521
Aircraft: N456JS
Type: G280
Operator: Jet Aviation
Arrival: 02/15/2026 10:30 AM
Departure: 02/17/2026 03:00 PM
Passengers: 4
Crew: 2
This is an automated notification from X-1FBO.Trip created in AirPlx:
| Field | Value |
|---|---|
| Tail Number | N456JS |
| Aircraft Type | G280 |
| Operator | Jet Aviation |
| Arrival | Feb 15, 2026 10:30 AM local |
| Departure | Feb 17, 2026 03:00 PM local |
| Reference | MIA-4521 |
Example 2: Arrival Only (No Known Departure)
When an aircraft arrives but there is no departure date scheduled yet, X1 FBO uses a placeholder for the departure.
Email received:
From: notifications@x1fbo.com
Subject: Request Confirmation - TEB-0892
Request Confirmation
Request #: TEB-0892
Aircraft: N789KL
Type: CL35
Operator: XOJET
Arrival: 03/10/2026 02:45 PM
Departure: TBD
Passengers: 6
Crew: 2
This is an automated notification from X-1FBO.Trip created in AirPlx:
| Field | Value |
|---|---|
| Tail Number | N789KL |
| Aircraft Type | CL35 |
| Operator | XOJET |
| Arrival | Mar 10, 2026 02:45 PM local |
| Departure | Not set |
| Reference | TEB-0892 |
The trip is created with an open-ended stay. You can update the departure time later when it becomes known.
Accepted placeholders for unknown departure: -, TBD, TBA, N/A
Example 3: Returning Home-Based Aircraft
Sometimes an aircraft is based at your FBO and departs for a trip, then returns later. In this case, X1 FBO records the departure date before the arrival date (since the aircraft left first and is coming back).
Email received:
From: notifications@x1fbo.com
Subject: Request Confirmation - MIA-4380
Request Confirmation
Request #: MIA-4380
Aircraft: N221QS
Type: GL7T
Operator: NetJets
Arrival: 03/15/2026 08:00 AM
Departure: 02/28/2026 06:30 PM
Passengers: 2
Crew: 2
This is an automated notification from X-1FBO.What’s happening: The aircraft departed on Feb 28, 2026 and is returning on Mar 15, 2026. AirPlx recognizes this pattern and creates the trip accordingly.
| Field | Value |
|---|---|
| Tail Number | N221QS |
| Aircraft Type | GL7T |
| Operator | NetJets |
| Arrival | Mar 15, 2026 08:00 AM local |
| Departure | Feb 28, 2026 06:30 PM local |
| Reference | MIA-4380 |
Example 4: Departure Only (Aircraft Already at Your FBO)
When an aircraft is already parked at your FBO and only has a scheduled departure, X1 FBO sends an email with an arrival placeholder and a known departure.
Email received:
From: notifications@x1fbo.com
Subject: Request Confirmation - MIA-4590
Request Confirmation
Request #: MIA-4590
Aircraft: N100HG
Type: FA8X
Operator: Flight Options
Arrival: -
Departure: 02/20/2026 11:00 AM
Passengers: 3
Crew: 2
This is an automated notification from X-1FBO.Trip created in AirPlx:
| Field | Value |
|---|---|
| Tail Number | N100HG |
| Aircraft Type | FA8X |
| Operator | Flight Options |
| Arrival | Not set |
| Departure | Feb 20, 2026 11:00 AM local |
| Reference | MIA-4590 |
The same placeholders accepted for unknown departure also work for unknown arrival: -, TBD, TBA, N/A
Queued for Review
Not every email results in an immediate trip. When AirPlx can’t fully process an email — for example, if the aircraft’s tail number isn’t in the database — the item is sent to your Operations Inbox for manual review.
To find queued items:
- Go to Operations > Inbox from the main navigation (or look for the Inbox icon in your navigation bar)
- Items from email ingestion will appear with details about what needs attention
- Resolve the issue (e.g., add the missing aircraft) and then process the item from the Inbox
Common reasons an email is queued rather than processed automatically:
- Unknown aircraft — The tail number isn’t in the AirPlx database. Add the aircraft manually, then process the queued item from the Operations Inbox.
- Parsing issues — The email format didn’t match what AirPlx expected. Your ops team can review the details and create the trip manually.
Good to Know
There are a few behaviors and limitations worth understanding as you use the integration day to day.
Cancellations Are Not Supported Yet
AirPlx currently processes request confirmation emails only. If a trip is cancelled in X1 FBO, you’ll need to cancel or remove the trip manually in AirPlx. This is on our roadmap.
Amended Confirmations Create New Trips
If a trip’s times change and X1 FBO sends a new confirmation email, AirPlx treats it as a separate email and will attempt to create a new trip. If a trip already exists for the same aircraft with overlapping dates, the duplicate may be automatically skipped. However, if the dates have changed enough to not overlap, a second trip will be created. Review your schedule after amendments and remove any duplicates.
Duplicate Trip Prevention
AirPlx tracks every email by its unique ID, so the same email processed twice will not create a duplicate trip. Additionally, if a trip already exists for the same aircraft with overlapping dates, the system will skip creating a duplicate.
Departure-Only Emails
AirPlx supports emails where the aircraft is already at your FBO and only has a scheduled departure (Arrival is - or TBD). See Example 4 above.
Troubleshooting
Emails are not appearing as trips
The most common cause is a missing or incorrect timezone setting. Check this first.
- Check your timezone — Go to Settings > Configuration and make sure your timezone is set correctly
- Check your FBO System setting — Make sure X1 FBO is selected in the FBO System dropdown under Email Ingestion
- Verify the ingestion email address — Confirm X1 FBO is sending to the correct
ingest+{slug}@airplx.comaddress. A single typo in the slug will silently prevent processing with no error notification - Check email delivery — Ask your X1 FBO administrator to verify that emails are being sent successfully via SendGrid
- Wait 60 seconds — AirPlx checks for new emails once per minute
- Check the Operations Inbox — The email may have been received but queued for review rather than processed automatically. Go to Operations > Inbox to check
Aircraft not found
If an aircraft’s tail number isn’t in the AirPlx database, the email is queued for review in your Operations Inbox rather than creating a trip immediately. To resolve:
- Go to Operations > Inbox and find the queued item
- Add the aircraft to AirPlx manually
- Process the queued item from the Inbox
Arrival or departure times are wrong
If all times are off by the same number of hours, your timezone is almost certainly set incorrectly.
- Check your timezone setting in Settings > Configuration
- X1 FBO sends times in local time (US date format: MM/DD/YYYY HH:MM AM/PM)
- AirPlx converts local time to UTC using your configured timezone
- If no timezone is configured, times default to UTC
FAQ
Can I change my ingestion email address? The slug is assigned based on your FBO setup. Contact AirPlx support if you need it changed.
Can I choose where incoming trips are assigned? Yes — you can set a default hangar or ramp location during setup. See Set a Default Location in the setup steps above.
How quickly do trips appear after the email is sent? AirPlx checks for new emails every 60 seconds, so trips typically appear within 1-2 minutes.
What happens if the same email is processed twice? Each email has a unique ID. Duplicate emails are automatically ignored — you won’t get duplicate trips.
Does AirPlx have access to my other emails?
No. AirPlx only processes emails sent to your specific ingest+{slug}@airplx.com ingestion email address. Emails sent to other addresses are not read or accessible.
What happens when a request is cancelled in X1 FBO? Cancellation emails are not processed at this time. If a trip is cancelled in X1 FBO, you’ll need to remove it from AirPlx manually. Cancellation support is planned for a future release.
What if I get a non-X1 FBO email at my ingestion email address? AirPlx uses parser auto-detection to identify email sources. Emails that don’t match any known format are ignored.
Where do I find emails that couldn’t be processed automatically? Check your Operations > Inbox. Items that need manual review — such as unknown aircraft — appear there with details about what went wrong.