Navigate to destination
The Navigate to destination action sends an address, place name, or map link to your Tesla vehicle’s navigation, the same as sharing a location to the car from your phone.
Using this action from the user interface
If you prefer building automations and scripts visually, Home Assistant walks you through this action step by step. You pick what to target, tweak a few options, and save. No YAML knowledge required.
To send a destination from an automation or a script:
- Go to Settings > Automations & scenes.
- Open an existing automation or script, or select Create automation > Create new automation.
- If you’re setting up a new automation, add a trigger in the When section. Scripts don’t need a trigger. They run when something else calls them.
- In the Then do section, select Add action.
- From the search box, search for and select Tesla Fleet: Navigate to destination.
- Select the Vehicle to send the destination to.
- Enter the Destination.
- Select Save.
Options in the UI
Using this action in YAML
If you work directly in YAML, or you want to know exactly what Home Assistant does under the hood, this section has the technical reference. It lists the field names you use in YAML, their types, and which ones are required. For how an automation or a script is built in YAML, refer to Automations in YAML and Scripts.
In YAML, refer to this action as tesla_fleet.navigate_to_destination. A basic example looks like this:
action: tesla_fleet.navigate_to_destination
data:
device_id: 0d462c0c4c0b064b1a91cdbd1ffcbd31
destination: "1600 Amphitheatre Parkway, Mountain View, CA"
Options in YAML
Good to know
- The vehicle is woken up if needed, and the Vehicle Commands scope is required.
Try it yourself
Ready to test this? Open Settings > Tools > Actions, search for this action, fill in the fields, and select Perform action. You see what happens on your actual entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more] without writing a line of YAML.
More examples
Real scenarios where this action shows up in automations and scripts. Copy any example and adapt it to your setup. In the visual editor, select the UI options listed in the example or paste the YAML code.
You don’t need to edit YAML to use these examples. Copy a YAML snippet from this page, open the visual automation editor in Home Assistant, and press Ctrl+V (or Cmd+V on Mac). Home Assistant automatically converts the pasted YAML into the visual editor format, whether it’s a full automation, a single trigger, a condition, or an action.
Automation: navigate to your next appointment
Half an hour before a calendar event starts, send the event’s location to the car.
- Trigger: Calendar: 30 minutes before an event starts
- Condition: The event has a location
- Action: Navigate to destination, with the event’s location
YAML example for navigating to your next appointment
alias: "Navigate to next appointment"
triggers:
- trigger: calendar
entity_id: calendar.personal
event: start
offset: "-0:30:0"
conditions:
- condition: template
value_template: "{{ trigger.calendar_event.location | default('', true) != '' }}"
actions:
- action: tesla_fleet.navigate_to_destination
data:
device_id: 0d462c0c4c0b064b1a91cdbd1ffcbd31
destination: "{{ trigger.calendar_event.location }}"
Automation: send a destination from your dashboard
Type a destination into a text field on your dashboard and send it to the car. The text field is an input text helperA helper is a virtual entity you create inside Home Assistant. It is not backed by a physical device. Helpers store values, track state, or do calculations that your automations and dashboards need. [Learn more] that you create separately.
- Trigger: Input text: the value changes
- Action: Navigate to destination, with the new value
YAML example for sending a destination from your dashboard
alias: "Send destination to car"
triggers:
- trigger: state
entity_id: input_text.car_destination
conditions:
- condition: template
value_template: "{{ trigger.to_state.state not in ['', 'unknown', 'unavailable'] }}"
actions:
- action: tesla_fleet.navigate_to_destination
data:
device_id: 0d462c0c4c0b064b1a91cdbd1ffcbd31
destination: "{{ trigger.to_state.state }}"
Still stuck?
To test the action on its own, run it in the automation editor with Run action, and check the message that it shows. To see what the action did when the automation ran, open the trace of that run. For details, refer to Testing automations. For common problems and their solutions, refer to Troubleshooting automations.
If that doesn’t help, the Home Assistant community is quick to help: join Discord for real-time chat, post on the community forum with the action you’re calling and what you expected to happen, or share on our subreddit /r/homeassistant.
AI assistants like ChatGPT or Claude can also explain actions or suggest the right one when you describe what you want in plain language.
Related actions
Explore related actions:
- Navigate to coordinates: Sets the vehicle’s navigation to a specific latitude and longitude.