diff --git a/cookbook/core/extend_flyte/custom_task_plugin.py b/cookbook/core/extend_flyte/custom_task_plugin.py
index 06069c4335..93ffbb31dd 100644
--- a/cookbook/core/extend_flyte/custom_task_plugin.py
+++ b/cookbook/core/extend_flyte/custom_task_plugin.py
@@ -9,9 +9,13 @@
 extended to all users of Flyte, or there is a cost/visibility benefit of doing so. To understand when you should write
 a backend plugin refer to - TODO: Flow chart that helps you decide when to write a backend / flytekit plugin?
 
+The following demo shows how to build Flyte container task extensions, with an SQLAlchemy extension as an example:
+
+.. youtube:: hfKbfcJbawE
+
 This tutorial will walk you through writing your own Sensor style plugin, that allows users to wait for a file to land
 in the object store. Remember, if you follow the Flyte/flytekit constructs, you will automatically make your plugin portable
-across all cloud platforms that Flyte supports
+across all cloud platforms that Flyte supports.
 
 Sensor Plugin
 ^^^^^^^^^^^^^^