Skip to main content
An external alias is Liftify’s note of what one of your records is called in your other software — this Liftify location is business unit 12 in ServiceTitan, this Liftify contact is customer 90210 over there. Your integration writes these itself as data syncs, and in normal use you never touch them.
This page is for whoever administers your integrations. If your account doesn’t sync from an external system, the page is empty and there is nothing here for you to do. Most people never need to open it.
There are exactly two situations that bring you here on purpose, and both are flagged for you at the top of the page: a business unit with nowhere to route its jobs, and a synced customer that couldn’t be matched safely. Everything else on the page is a reference list. You need the Manage external systems and their aliases permission. Viewing is enough to browse; adding, editing and removing are additionally closed to users whose access is restricted to specific locations.

​
Open the page

  1. In the left sidebar, click the circle with your initials, then User Settings.
  2. Under Integrations, click External Aliases.
The page describes itself: “Manage the mappings between Liftify records and their identifiers in registered external systems. Integrations register most aliases automatically; aliases can also be added, edited, and removed by hand here — removing one breaks the link for any integration that resolves it.”

​
Unmapped business units

If a panel headed Unmapped business units appears, deal with it — jobs are sitting still because of it.
These business units have appeared in synced data but have no location mapping. Jobs in them wait as deferred until a mapping is added — map the ones you want routed, and leave deliberately out-of-scope units unmapped.
Each row names the business unit, its identifier in the external system, and which system it came from.
  • If those jobs belong to one of your Liftify locations, click Map to location. The alias form opens with the system, the entity type and the identifier already filled in. Add the Liftify record ID of the location and click Create Alias.
  • If the business unit is something you deliberately don’t want in Liftify — an internal cost centre, a line of work you don’t ask for reviews on — leave it alone. Unmapped is the correct answer for those, and the panel keeps listing it.
Business unit mappings are never created automatically. Jobs in an unmapped unit keep waiting until you map it, and start flowing once you do.

​
Customer identity conflicts

The second panel, Customer identity conflicts:
Synced customers that matched an existing customer by email or phone but could not be linked automatically. Each waits as deferred until you register the correct alias here; syncs pick it up on the next run.
Each row carries a badge saying why: Click Resolve to open the alias form with the details filled in, check that the Liftify record ID is the contact you actually mean, and click Create Alias. The next sync picks the customer up. Liftify deliberately stops rather than picking one — a wrong link means one customer’s job history, and their review requests, land on another customer’s record.

​
The alias list

Below the panels, every alias on your account, newest first: Narrow the list with the External System, Entity Type and Aliasable Type filters. Clear Filters resets them. With filters that match nothing you get No external aliases found — “No external aliases match the current filters.”

​
Add an alias by hand

Use the Map to location and Resolve buttons where you can — they fill most of the form in for you. To start from scratch, click Add External Alias. The form is “Bind a Liftify record to its identifier in an external system.” Click Create Alias. Liftify confirms with “External alias created.”, or “External alias already existed.” if that exact mapping was already there — no harm done either way. If the record you named isn’t on your account you’ll see “Record not found: Customer #123 does not exist on this account.” and nothing is saved.
Liftify record ID is not the same as the Location ID shown on a location’s page. That one starts with loc-. This field wants the plain number from the address bar.

​
Correct or remove one

Click the pencil on a row to open Edit External Alias — “Correct the identifier or re-point it to a different Liftify record. Saving replaces the alias, and lookups resolve the new values immediately.” Change what’s wrong and click Update Alias. Some rows have no pencil; those can only be removed. Click the bin icon to remove one. You’re asked to confirm, and the confirmation spells out the consequence: “Remove this external alias? [entity type] [id] will no longer resolve to this record.”
Removing an alias breaks the link for every integration that relies on it. Data that used to attach itself to the right Liftify record stops finding it on the next sync. Remove one only when you know the mapping is wrong — if you’re unsure, correct it with the pencil instead.