Merge pull request #644 from novuhq/fix/worklfow-trigger-identifier

fix: add workflow trigger identifier

concepts/controls.mdx

@@ -2,7 +2,7 @@
 title: "Controls"
 ---
 
-Controls are defined using [JSON Schema](/recipes/json-schema) or Zod, providing a strong run-time validation system for your workflows.
+Controls are defined using [JSON Schema](/recipes/json-schema) or [Zod](https://zod.dev), providing a strong run-time validation system for your workflows.
 
 This ensures that you as the developer and your non-technical peers are speaking the same language.
 Those responsible for styling and copy can edit with confidence, knowing their changes are tested in code.
@@ -49,7 +49,7 @@ The snippet below shows a configuration for the Step Control schema. If you don
       {
         controlSchema: z.object({
           hideBanner: z.boolean().default(false),
-          subject: z.string().defaul('This is the default title'),
+          subject: z.string().default('This is the default subject'),
           components: z.array(z.object({
             type: z.enum(['header', 'cta-row', 'footer']),
             content: z.string()
@@ -83,7 +83,7 @@ The snippet below shows a configuration for the Step Control schema. If you don
           // Specify the properties to validate. Supports deep nesting.
           properties: {
             hideBanner: { type: "boolean", default: false },
-            subject: { type: "string" },
+            subject: { type: "string", default: 'This is the default subject' },
             // Allowing no code control over the component in the Dashboard UI
             components: {
               type: "array",
@@ -97,7 +97,7 @@ The snippet below shows a configuration for the Step Control schema. If you don
             },
           },
           // Specify the array of which properties are required.
-          required: ["complianceFooter"],
+          required: ["hideBanner"],
           // Used to enforce full type strictness, with no rogue properties.
           additionalProperties: false,
           // The `as const` is important to let Typescript know that this
@@ -111,6 +111,6 @@ The snippet below shows a configuration for the Step Control schema. If you don
 </CodeGroup>
 
 ## Supported Schema Types
-- **ZodSchema** - A TypeScript-first schema declaration and validation library.
-- **[JSON Schema](/recipes/json-schema)** - The most popular schema language for defining JSON data structures.
+- [Zod Schema](https://zod.dev/) - A TypeScript-first schema declaration and validation library.
+- [JSON Schema](/recipes/json-schema) - The most popular schema language for defining JSON data structures.
 

concepts/endpoint.mdx

@@ -2,7 +2,7 @@
 title: "Bridge Endpoint"
 ---
 
-Novu Framework requires a **single** `HTTP` endpoint (`/api/novu` or similar) to be exposed by your application. This endpoint is used to receive events from our Worker Engine.
+Novu Framework requires a **single** `HTTP` endpoint (`/api/novu` or similar) to be exposed by your application. This endpoint is used to receive events from our **Worker Engine**.
 
 You can view the Bridge Endpoint as a webhook endpoint that Novu will call when it needs to retrieve contextual information for a given subscriber and notification.
 

concepts/workflows.mdx

@@ -18,10 +18,10 @@ A workflow acts as the blueprint for the notifications that will be sent. This i
 
 <Steps>
     <Step title="Name and Identifier">
-        Every workflow will have a name and an identifier that are used to uniquely identify each workflow.
+        Every workflow will have a name and trigger identifier. The workflow trigger identifier is used to uniquely identify each workflow. Two workflows can have same name but always have different trigger identifiers.
     </Step>
     <Step title="Trigger">
-        The "Trigger" refers to an event or action that initiates the workflow. It signifies a call to the Novu API with a specified workflow ID, along with the necessary payload data that the workflow content will utilize.
+        The **Trigger** refers to an event or action that initiates the workflow. It signifies a call to the Novu API with a specified workflow trigger identifier, along with the necessary payload data that the workflow content will utilize.
     </Step>
     <Step title="Steps">
         Within the Novu framework, steps are categorized into various types, each of which is linked with at least one corresponding action: