diff --git a/source/_integrations/transmission.markdown b/source/_integrations/transmission.markdown
index 55b97be7c90..2f3208d2543 100644
--- a/source/_integrations/transmission.markdown
+++ b/source/_integrations/transmission.markdown
@@ -54,7 +54,7 @@ Possible events are:
 - `transmission_started_torrent`
 - `transmission_removed_torrent`
 
-Inside of the event, there is the name of the torrent that is started or completed, as it is seen in the Transmission User Interface.
+Inside the event, there is the name of the torrent that is started or completed and the path where the files are downloaded, as seen in the Transmission User Interface.
 
 Example of an automation that notifies on successful download and removes the torrent from the client:
 
@@ -69,7 +69,7 @@ Example of an automation that notifies on successful download and removes the to
     - action: notify.telegram_notifier
       data:
         title: "Torrent completed!"
-        message: "{{trigger.event.data.name}}"
+        message: "{{trigger.event.data.name}} downloaded to {{trigger.event.data.download_path}}"
     - action: transmission.remove_torrent
       data:
         entry_id: eeb52bc78e11d813a1e6bc68c8ff93c8
@@ -90,6 +90,7 @@ Adds a new torrent to download. It can either be a URL (HTTP, HTTPS or FTP), mag
 | ---------------------- | -------- | ------------------------ |
 | `entry_id`             | no       | The integration entry_id |
 | `torrent`              | no       | Torrent to download      |
+| `download_path`        | yes      | Absolute path to the download directory. If not specified, the Transmission's default directory will be used. |
 
 ### Action `remove_torrent`