Building an automation creates a reusable template. It doesn't run on anything until you attach it to a specific trip or contact. Once attached, it's live for that record and fires on its own trigger.
You can also build a one-off automation directly on a record, for a workflow you'll only ever need once.
Apply an automation template
The flow is the same for both record types. Only the starting point differs:
On a contact: open the contact and select the Automations tab.
On a trip: open the trip and select Automations from the left navigation.
From there:
Click Add Automation and choose From Template.
Browse or search the available templates. You'll only see templates matching the record type, so contact templates on a contact and trip templates on a trip.
Click the one you want. TripLoft links it and confirms.
The automation now appears in that record's list with its name, trigger, the number of emails and tasks it contains, its status, and when it was last updated. From the list you can search, filter, open an automation to review it, or use the Actions menu for more.
Good to know: An applied automation becomes its own independent copy. Later edits to the template don't reach it, and editing it doesn't affect the template or any other record using it. Open it after applying to check for warnings, since missing data or a trigger date that's already passed will stop it running silently. See Automation Warnings and Edge Cases.
Create a one-off automation
A one-off is built on the record itself and runs only for that trip or contact. It isn't saved as a template and can't be reused elsewhere.
On the record's Automations tab, click Add Automation and choose One-Off Automation.
Enter a name, confirm the type, and click Continue.
Select a trigger, add your email or task actions, configure them, and save.
Building it works the same way as building a template. See Create an Automation for triggers and actions, and Configure Automation Actions for setting each step up.
One difference: the Trip Created trigger isn't available on a one-off built inside an existing trip, since that event already happened. Use a different trigger, or build it as a template and apply it to future trips.
Which to use
Use a template for anything you'll repeat across clients or trips, like a passport expiry reminder or a payment nudge. Build it once and attach it wherever it's needed.
Use a one-off when the situation is specific to a single record and you'd never want it again.