Once triggered, Zapier can make things happen in other apps; these are called actions. Here are actions that Zapier can take within Safari Portal.

Actions that Edit

Add Traveler to File

This action adds one or more existing traveler contacts to an existing File in Safari Portal. You map in the traveler contact ID(s) and the File ID to add them.

Example: When a new traveler signs up for a trip through a Typeform, a Zap automatically finds or creates their contact record in Safari Portal, then instantly adds them to the correct File using the Add Traveler to File action, so they're ready for trip planning without manual data entry.

Update Contact

This action updates an existing contact (Traveler, Partner Agent, or Supplier) in Safari Portal. You specify which contact to update by ID and map in the fields you want to change, like email, phone, preferences, or custom attributes.

Example: When a traveler updates their dietary preferences in a Typeform, a Zap automatically finds their contact record in Safari Portal and updates their dietary restrictions and allergies, so the latest info is always available to suppliers and the travel team.

Update File

This action updates an existing File in Safari Portal. You specify which File to update by ID and map in the fields you want to change, like file name, consultant assignment, pipeline stage, or custom attributes.

Example: When a payment is received in Stripe, a Zap automatically finds the corresponding File in Safari Portal and updates its financial status to "Deposit Received," triggering downstream supplier confirmations without manual intervention.

Actions that Create

Create Contact

This action creates a new contact (Traveler, Partner Agent, or Supplier) in Safari Portal. You specify the contact type and map in detail, like name, email, phone, and other contact information from your trigger data.

Example: When a lead fills out a landing page form in HubSpot, a Zap automatically creates a new Traveler contact in Safari Portal with their name, email, and phone number pulled directly from the form submission, so Sophie's contact database stays in sync.

Create File

This action creates a new File in Safari Portal. You map in details like file name, pipeline, consultant assignment, and other file properties from your trigger data.

Example: When a deal moves to "Closed Won" in Pipedrive, a Zap automatically creates a new File in Safari Portal's Planning pipeline, assigns it to the right consultant based on territory, and pre-fills the file name with the client name and trip dates, so the planning process kicks off instantly.

Actions that Search

Find Consultant

This action finds an existing consultant in Safari Portal by ID or by name. Use this to look up a consultant so you can reference them in downstream actions.

Example: When a new File is created in Safari Portal, a Zap uses Find Consultant to look up the assigned consultant's email address so it can automatically send them a welcome message in Slack with file details and next steps.

Find Contact

This action finds an existing contact in Safari Portal by ID, type, or name. Optionally, you can set it to create a contact if none are found, which is useful for deduplication.

Example: When a name appears in an incoming email or form, a Zap uses Find Contact to check if that person already exists in Safari Portal as a Traveler; if they don't, it automatically creates them, preventing duplicates and saving manual lookup time.

Find File

This action finds an existing File in Safari Portal by File ID. Optionally, you can set it to create a File if none are found, which is useful for ensuring a File exists before you add travelers or update it.

Example: When a client name and trip date come through from a booking confirmation email, a Zap uses Find File to locate the matching File in Safari Portal; if it doesn't exist yet, the Zap automatically creates it so downstream actions have a File to work with.