@adminide-stack/yantra-help-browser 12.0.17 → 12.0.19-alpha.1

package/lib/pages/StatusPage/index.js

@@ -1,4 +1,4 @@
-import {jsxs,jsx}from'react/jsx-runtime';import {PageHero}from'../../components/PageHero.js';import {Card,CardContent}from'@admin-layout/tailwind-ui/shardui/card.js';import {Badge}from'@admin-layout/tailwind-ui/shardui/badge.js';import {Icons}from'../../components/Icons.js';const SYSTEMS = [{
+import {jsxs,jsx}from'react/jsx-runtime';import {PageHero}from'../../components/PageHero.js';import {Card,CardContent}from'@admin-layout/tailwind-ui/shardui/card.js';import {Icons}from'../../components/Icons.js';const SYSTEMS = [{
   name: 'API',
   status: 'operational',
   uptime: '99.99%'
@@ -33,11 +33,11 @@ const StatusPage = () => {
       children: jsxs("div", {
         className: "container mx-auto max-w-4xl px-6 lg:px-16",
         children: [jsx(Card, {
-          className: "mb-8 border-border/60 border-emerald-500/20 bg-emerald-500/5",
+          className: "mb-8 border border-success/30 bg-success/5",
           children: jsxs(CardContent, {
             className: "flex items-center gap-4 py-6",
             children: [jsx(Icons.MdCheckCircleIcon, {
-              className: "h-10 w-10 shrink-0 text-emerald-500"
+              className: "h-10 w-10 shrink-0 text-success"
             }), jsxs("div", {
               children: [jsx("div", {
                 className: "font-semibold text-foreground",
@@ -54,25 +54,30 @@ const StatusPage = () => {
         }), jsx("div", {
           className: "space-y-4",
           children: SYSTEMS.map(system => jsx(Card, {
-            className: "border-border/60",
+            className: "themed-card border-border",
             children: jsxs(CardContent, {
               className: "flex items-center justify-between py-4",
               children: [jsxs("div", {
                 className: "flex items-center gap-3",
-                children: [jsx(Icons.MdCheckCircleIcon, {
-                  className: "h-5 w-5 text-emerald-500"
+                children: [jsxs("span", {
+                  className: "relative flex h-2.5 w-2.5",
+                  "aria-hidden": "true",
+                  children: [jsx("span", {
+                    className: "absolute inline-flex h-full w-full animate-ping rounded-full bg-success opacity-60"
+                  }), jsx("span", {
+                    className: "relative inline-flex h-2.5 w-2.5 rounded-full bg-success"
+                  })]
                 }), jsx("span", {
                   className: "font-medium text-foreground",
                   children: system.name
                 })]
               }), jsxs("div", {
                 className: "flex items-center gap-4",
-                children: [jsxs("span", {
-                  className: "text-sm text-muted-foreground",
-                  children: [system.uptime, " uptime"]
-                }), jsx(Badge, {
-                  variant: "secondary",
-                  className: "bg-emerald-500/10 text-emerald-600",
+                children: [jsx("span", {
+                  className: "font-mono text-xs text-muted-foreground",
+                  children: system.uptime
+                }), jsx("span", {
+                  className: "inline-flex rounded-full bg-success/10 px-2.5 py-0.5 text-xs font-medium text-success",
                   children: system.status
                 })]
               })]

package/lib/pages/StatusPage/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sources":["../../../src/pages/StatusPage/index.tsx"],"sourcesContent":[null],"names":[],"mappings":"mRAMA,MAAM,OAAO,GAAG,CAAA;MACV,EAAA,KAAM;QACN,EAAI,aAAa;QACjB,EAAI;;MAEJ,EAAA,WAAM;EACV,MAAA,EAAA,aAAA;AAEF,EAAM,MAAA,EAAA;AACF,CAAA,EAAA;AA6CJ,EAAE,IAAA,EAAA,cAAA;AAEF,EAAA,MAAA,EAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;"}
+{"version":3,"file":"index.js","sources":["../../../src/pages/StatusPage/index.tsx"],"sourcesContent":[null],"names":[],"mappings":"oNAMA,MAAM,OAAO,GAAG,CAAA;MACV,EAAA,KAAM;QACN,EAAI,aAAa;QACjB,EAAI;;MAEJ,EAAA,WAAM;EACV,MAAA,EAAA,aAAA;AAEF,EAAM,MAAA,EAAA;;AAiDN,EAAE,IAAA,EAAA,cAAA;AAEF,EAAA,MAAA,EAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;"}

package/lib/routes.json

@@ -115,6 +115,17 @@
       "hasComponent": true
     }
   },
+  {
+    "//feedback": {
+      "path": "//feedback",
+      "key": "feedback",
+      "exact": true,
+      "hideInMenu": true,
+      "position": "MIDDLE",
+      "componentPath": "@adminide-stack/yantra-help-browser/lib/pages/Feedback/index.js",
+      "hasComponent": true
+    }
+  },
   {
     "//privacy": {
       "path": "//privacy",

package/lib/slot-fill/LogoFill.js

@@ -36,7 +36,7 @@ const defaultRenderLogoAndTitle = (props, prefersReducedMotion, renderKey = 'men
   }
   const logoDom = defaultRenderLogo(logo, prefersReducedMotion, scrolled, settings, location);
   const titleDom = jsx("h1", {
-    className: `text-2xl ${settings?.navTheme === 'dark' ? 'text-[#F9FBFF]' : titleColor || 'text-gray-900'}`,
+    className: `text-2xl ${settings?.navTheme === 'dark' ? 'text-foreground' : titleColor || 'text-foreground'}`,
     style: {
       fontFamily: fontFamily,
       fontWeight: titleFontWeight,

package/lib/slot-fill/LogoFill.js.map

@@ -1 +1 @@
-{"version":3,"file":"LogoFill.js","sources":["../../src/slot-fill/LogoFill.tsx"],"sourcesContent":[null],"names":["_jsx"],"mappings":"kUAMO,MAAM,iBAAiB,GAAG,CAC7B,IAA8B,EAC9B,oBAA6B,EAC7B,QAAQ,EACR,QAAa,EACb,QAAa,KACI;AACjB,EAAA,IAAA,OAAW,IAAA,KAAS,QAAA,EAAQ;AACxB,IAAA,OAAAA,GAAO,KAAC,EAAI;MACf,IAAA,EAAA,SAAA;AACD,MAAA,QAAW,EAAA,QAAS;cACT,EAAA,QAAO;MACjB,QAAA,EAAA;AACD,KAAA,CAAA;AACJ;AAEA,EAAA,IAAM,OAAO,IAAyB,KAAA,UAAA,EAAA;AAKlC,IAAA,OAAQ,IAAA,EAAA;;SAGF,IAAA;AACN;AACI,MAAA,yBAAY,GAAA,CAAA,KAAA,EAAA,oBAAA,EAAA,SAAA,GAAA,kBAAA,KAAA;QACf;AACD,IAAA,QAAa;IACb,MAAM;AAIM,IAAA,aAAA;AACA,IAAA,QAAA;AACA,IAAA;AACA,GAAA,GAAA,KAAA;AACA,EAAA,MAAA;cAGH;IAIT,aAAI;AACA,IAAA,eAAgB;AAChB,IAAA,WAAO;IACX,UAAC;IAED;AACI,IAAA,IAAA;IACJ;AAEA,GAAA,GAAA;AACJ,EAAE,MAAA,cAAA,GAAA,KAAA,CAAA,SAAA,IAAA,EAAA,CAAA;AAEF,EAAA,IAAM,cAAe,UAAQ,EAAA;IACzB,OAAO,IACF;AAEO;AAKA,EAAA,MAAA,OAAA,GAAA,iBAAiB,CAAA,IAAA,EAAA,oBAAA,EAAA,QAAA,EAAA,QAAA,EAAA,QAAA,CAAA;QACrB,QAEN,GAAAA,GAAA,CAAA,IAAA,EAAA;AACN,IAAE,SAAA,EAAA,CAAA,SAAA,EAAA,QAAA,EAAA,QAAA,KAAA,MAAA,GAAA,gBAAA,GAAA,UAAA,IAAA,eAAA,CAAA,CAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;"}
+{"version":3,"file":"LogoFill.js","sources":["../../src/slot-fill/LogoFill.tsx"],"sourcesContent":[null],"names":["_jsx"],"mappings":"kUAMO,MAAM,iBAAiB,GAAG,CAC7B,IAA8B,EAC9B,oBAA6B,EAC7B,QAAQ,EACR,QAAa,EACb,QAAa,KACI;AACjB,EAAA,IAAA,OAAW,IAAA,KAAS,QAAA,EAAQ;AACxB,IAAA,OAAAA,GAAO,KAAC,EAAI;MACf,IAAA,EAAA,SAAA;AACD,MAAA,QAAW,EAAA,QAAS;cACT,EAAA,QAAO;MACjB,QAAA,EAAA;AACD,KAAA,CAAA;AACJ;AAEA,EAAA,IAAM,OAAO,IAAyB,KAAA,UAAA,EAAA;AAKlC,IAAA,OAAQ,IAAA,EAAA;;SAGF,IAAA;AACN;AACI,MAAA,yBAAY,GAAA,CAAA,KAAA,EAAA,oBAAA,EAAA,SAAA,GAAA,kBAAA,KAAA;QACf;AACD,IAAA,QAAa;IACb,MAAM;AAIM,IAAA,aAAA;AACA,IAAA,QAAA;AACA,IAAA;AACA,GAAA,GAAA,KAAA;AACA,EAAA,MAAA;cAGH;IAIT,aAAI;AACA,IAAA,eAAgB;AAChB,IAAA,WAAO;IACX,UAAC;IAED;AACI,IAAA,IAAA;IACJ;AAEA,GAAA,GAAA;AACJ,EAAE,MAAA,cAAA,GAAA,KAAA,CAAA,SAAA,IAAA,EAAA,CAAA;AAEF,EAAA,IAAM,cAAe,UAAQ,EAAA;IACzB,OAAO,IACF;AAEO;AAKA,EAAA,MAAA,OAAA,GAAA,iBAAiB,CAAA,IAAA,EAAA,oBAAA,EAAA,QAAA,EAAA,QAAA,EAAA,QAAA,CAAA;QACrB,QAEN,GAAAA,GAAA,CAAA,IAAA,EAAA;AACN,IAAE,SAAA,EAAA,CAAA,SAAA,EAAA,QAAA,EAAA,QAAA,KAAA,MAAA,GAAA,iBAAA,GAAA,UAAA,IAAA,iBAAA,CAAA,CAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;"}

package/lib/templates/content/account-management/account-setup.md

@@ -8,7 +8,7 @@ Get up and running with Yantra in under 5 minutes. This guide walks you through
 
 ### Step 1 — Sign up
 
-1. Go to [yantra.ai](https://yantra.ai) and click **Get Started**.
+1. Go to [yantra.app](https://yantra.app) and click **Get Started**.
 2. Choose a sign-up method:
     - **Email + password** — Enter your work or personal email and create a strong password (minimum 12 characters).
     - **Google SSO** — Sign in with your Google account for one-click setup.
@@ -17,9 +17,9 @@ Get up and running with Yantra in under 5 minutes. This guide walks you through
 
 ### Step 2 — Verify your email
 
-Check your inbox for a verification email from **noreply@yantra.ai**. Click the verification link to activate your account.
+Check your inbox for a verification email from **noreply@yantra.app**. Click the verification link to activate your account.
 
-> **Didn't receive the email?** Check your spam folder. If it's not there, click "Resend verification" on the login page.
+**Didn't receive the email?** Check your spam folder. If it's not there, click "Resend verification" on the login page.
 
 ### Step 3 — Complete your profile
 

package/lib/templates/content/account-management/delete-account.md

@@ -19,7 +19,7 @@ Deleting your account permanently removes:
 | AI employee memory     | All learned context and preferences  |
 | Team associations      | Your membership in shared workspaces |
 
-> **This action is irreversible.** Once deleted, your data cannot be recovered.
+**This action is irreversible.** Once deleted, your data cannot be recovered.
 
 ### Export your data first
 
@@ -68,7 +68,7 @@ Type `DELETE` in the confirmation field and click **Permanently Delete Account**
 - **Within 30 days** — All personal data is permanently purged from our systems, including backups.
 - **After 30 days** — A confirmation email is sent to your registered email address.
 
-> **Changed your mind?** You have 30 days to contact support@yantra.ai to cancel the deletion and restore your account.
+**Changed your mind?** You have 30 days to contact support@yantra.app to cancel the deletion and restore your account.
 
 ---
 
@@ -78,4 +78,4 @@ If you're on a team plan, additional steps may apply:
 
 - **Team members** — Your admin will be notified of your departure. Your data within shared workspaces may be retained per the organization's data policy.
 - **Workspace owners** — You must transfer ownership or delete the workspace before deleting your personal account.
-- **Enterprise accounts** — Contact your account manager or email enterprise@yantra.ai for assisted deletion with compliance documentation.
+- **Enterprise accounts** — Contact your account manager or email support@yantra.app for assisted deletion with compliance documentation.

package/lib/templates/content/connectors/connector-triggers.md

@@ -0,0 +1,76 @@
+# Connector Triggers
+
+When events occur in connected apps — a new GitHub commit, a record created in Airtable, or a message received in Slack — connector triggers deliver that event data to your application as a structured payload.
+
+Yantra provides 969+ connector pods, many of which contribute one or more triggers. Each trigger type watches for a specific event on a user's connected account and notifies your endpoint when it fires.
+
+---
+
+## How Triggers Work
+
+1. **Inspect** — discover the trigger types available on an installed connector and their required configuration.
+2. **Create an instance** — bind a trigger type to a specific connected account so Yantra starts watching for events.
+3. **Receive events** — Yantra posts event payloads to your registered webhook endpoint when the trigger fires.
+4. **Manage** — list, update, or delete trigger instances as your needs change.
+
+### Trigger types vs. trigger instances
+
+| Concept              | What it is                                                                                                                                 |
+| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
+| **Trigger type**     | A template defined by the connector pod (e.g. `AIRTABLE_VIEW_CREATED_TRIGGER`). Specifies the `configSchema` and `payloadSchema`.          |
+| **Trigger instance** | An active subscription that binds a trigger type to a specific connected account. One type can have many instances for different accounts. |
+
+---
+
+## Delivery types
+
+| Type                | How it works                                                                                                        |
+| ------------------- | ------------------------------------------------------------------------------------------------------------------- |
+| **Webhook trigger** | The third-party app pushes events to Yantra in real time. Yantra forwards the payload to your endpoint immediately. |
+| **Polling trigger** | For apps that don't support outgoing webhooks. Yantra polls for new data on a schedule and delivers batched events. |
+
+---
+
+## Payload structure
+
+Every event payload delivered to your endpoint follows this structure:
+
+```json
+{
+    "id": "evt_abc123",
+    "type": "trigger_event",
+    "metadata": {
+        "trigger_slug": "AIRTABLE_VIEW_CREATED_TRIGGER",
+        "trigger_instance_id": "ti_xyz789",
+        "connected_account_id": "ca_def456",
+        "connector": "airtable"
+    },
+    "data": {
+        "record_id": "recXxx",
+        "view_id": "viwYyy",
+        "table_name": "Projects"
+    },
+    "timestamp": "2026-05-06T10:30:00Z"
+}
+```
+
+Use `metadata.trigger_slug` to route events to the right handler. Use `metadata.trigger_instance_id` to identify which specific subscription fired.
+
+---
+
+## Prerequisites
+
+Before working with triggers:
+
+1. **Install the connector** — `yantra connector install <name>`
+2. **Authenticate** — `yantra auth login`
+3. **Create a connected account** — OAuth or API-key flow via the Yantra dashboard
+4. **Register a webhook endpoint** — `yantra webhook create` (see [Subscribing to Connector Events](subscribing-to-connector-events))
+
+---
+
+## Next steps
+
+- [Creating Connector Triggers](creating-connector-triggers) — create trigger instances
+- [Subscribing to Connector Events](subscribing-to-connector-events) — receive events via webhooks
+- [Managing Connector Triggers](managing-connector-triggers) — list, update, and delete instances

package/lib/templates/content/connectors/creating-connector-triggers.md

@@ -0,0 +1,121 @@
+# Creating Connector Triggers
+
+A trigger instance binds a trigger type to a specific connected account so Yantra watches for events and delivers them to your endpoint. This guide walks through discovering available triggers and creating instances using the `yantra` CLI.
+
+---
+
+## Step 1 — Discover available triggers
+
+First, install the connector pod you want to monitor, then list its triggers:
+
+```bash
+# Install the connector
+yantra connector install airtable
+
+# List all triggers contributed by this connector
+yantra trigger list airtable
+```
+
+Output:
+
+```
+CONNECTOR    TRIGGER ID                            TITLE
+────────────────────────────────────────────────────────────────────────────────────────────────────────
+airtable     AIRTABLE_VIEW_CREATED_TRIGGER         New view created in a base
+airtable     AIRTABLE_RECORD_CREATED_TRIGGER       New record added to a table
+airtable     AIRTABLE_RECORD_UPDATED_TRIGGER       Record updated in a table
+
+Total: 3 triggers
+```
+
+To see every trigger across all installed connectors, run `yantra trigger list` without a filter.
+
+---
+
+## Step 2 — Inspect the trigger schema
+
+Before creating an instance, inspect the trigger's `configSchema` (what you need to provide) and `payloadSchema` (what the event will contain):
+
+```bash
+yantra trigger show AIRTABLE_RECORD_CREATED_TRIGGER
+```
+
+Output:
+
+```json
+{
+    "id": "AIRTABLE_RECORD_CREATED_TRIGGER",
+    "title": "New record added to a table",
+    "connector": "airtable",
+    "configSchema": {
+        "properties": {
+            "base_id": { "type": "string", "description": "Airtable base ID (app...)" },
+            "table_id": { "type": "string", "description": "Table ID or name" }
+        },
+        "required": ["base_id", "table_id"]
+    },
+    "payloadSchema": {
+        "properties": {
+            "record_id": { "type": "string" },
+            "fields": { "type": "object" },
+            "created_time": { "type": "string", "format": "date-time" }
+        }
+    }
+}
+```
+
+---
+
+## Step 3 — Create a trigger instance
+
+Use `yantra trigger instance upsert` to create (or update) a trigger instance for a specific connected account:
+
+```bash
+yantra trigger instance upsert \
+  --slug AIRTABLE_RECORD_CREATED_TRIGGER \
+  --account ca_def456 \
+  --config '{"base_id": "appXxxYyyZzz", "table_id": "Projects"}'
+```
+
+| Flag        | Required | Description                                                             |
+| ----------- | -------- | ----------------------------------------------------------------------- |
+| `--slug`    | Yes      | The trigger type ID (uppercase, e.g. `AIRTABLE_RECORD_CREATED_TRIGGER`) |
+| `--account` | Yes      | The `connectedAccountId` for the user whose events you want to capture  |
+| `--config`  | Depends  | JSON matching the trigger's `configSchema` required fields              |
+
+The command outputs the created instance details, including the `id` you'll use to manage it later.
+
+---
+
+## Finding the connected account ID
+
+List connected accounts for a connector to find the right `connectedAccountId`:
+
+```bash
+yantra connector accounts airtable
+```
+
+If the user has multiple connected accounts for the same connector, pass the specific one you want to watch.
+
+---
+
+## Multiple instances
+
+You can create multiple trigger instances for the same trigger type — one per connected account:
+
+```bash
+# Watch two different Airtable accounts
+yantra trigger instance upsert --slug AIRTABLE_RECORD_CREATED_TRIGGER \
+  --account ca_user1 --config '{"base_id": "appAAA", "table_id": "Tasks"}'
+
+yantra trigger instance upsert --slug AIRTABLE_RECORD_CREATED_TRIGGER \
+  --account ca_user2 --config '{"base_id": "appBBB", "table_id": "Leads"}'
+```
+
+---
+
+## What happens after creation
+
+Once a trigger instance exists, Yantra begins watching the connected account for the specified event. When the event fires, Yantra signs the payload and delivers it to your registered webhook endpoint.
+
+Make sure you have a webhook endpoint registered and an active subscription before creating trigger instances. See [Subscribing to Connector Events](subscribing-to-connector-events).

package/lib/templates/content/connectors/managing-connector-triggers.md

@@ -0,0 +1,125 @@
+# Managing Connector Triggers
+
+Once trigger instances are created, use the `yantra trigger instance` subcommands to list, update, and delete them.
+
+---
+
+## Listing trigger instances
+
+List all active trigger instances for your organization:
+
+```bash
+yantra trigger instance list
+```
+
+Filter by connected account:
+
+```bash
+yantra trigger instance list --account ca_def456
+```
+
+Filter by trigger type:
+
+```bash
+yantra trigger instance list --slug AIRTABLE_RECORD_CREATED_TRIGGER
+```
+
+Example output:
+
+```json
+[
+    {
+        "id": "ti_xyz789",
+        "triggerSlug": "AIRTABLE_RECORD_CREATED_TRIGGER",
+        "connectedAccountId": "ca_def456",
+        "config": { "base_id": "appXxxYyyZzz", "table_id": "Projects" },
+        "createdAt": "2026-05-01T12:00:00Z"
+    }
+]
+```
+
+---
+
+## Updating a trigger instance
+
+Use `upsert` to update the configuration of an existing trigger instance. Pass the same `--slug` and `--account` combination:
+
+```bash
+yantra trigger instance upsert \
+  --slug AIRTABLE_RECORD_CREATED_TRIGGER \
+  --account ca_def456 \
+  --config '{"base_id": "appXxxYyyZzz", "table_id": "NewTableName"}'
+```
+
+If no instance exists for that slug/account pair, a new one is created. If one already exists, it is updated.
+
+---
+
+## Deleting a trigger instance
+
+Permanently remove a trigger instance by its `id`:
+
+```bash
+yantra trigger instance delete ti_xyz789
+```
+
+> Deleting a trigger instance is permanent. Yantra will stop delivering events for that subscription immediately.
+
+If you only need to temporarily stop events, remove the instance and recreate it later when ready — or adjust your webhook handler to ignore events you don't currently want to process.
+
+---
+
+## Listing available trigger types
+
+To see all trigger types contributed by your installed connectors:
+
+```bash
+# All triggers across all installed connectors
+yantra trigger list
+
+# Triggers for a specific connector
+yantra trigger list github
+```
+
+To see the full schema for a specific trigger type:
+
+```bash
+yantra trigger show GITHUB_COMMIT_EVENT
+```
+
+---
+
+## Troubleshooting
+
+### No events received
+
+1. Confirm the trigger instance exists: `yantra trigger instance list`
+2. Verify your webhook endpoint is registered: `yantra webhook list`
+3. Check that the connected account is still authorized
+4. Simulate a test event to verify your handler is reachable:
+    ```bash
+    yantra trigger simulate -f fixture.json <TRIGGER_SLUG> \
+      --remote --endpoint we_abc123 --signing-secret your-secret
+    ```
+
+### Signature verification failures
+
+Ensure the `signingSecret` in your handler matches the value in the webhook endpoint's `setupData`. Rotate the signing secret via `yantra webhook update` if compromised.
+
+### Wrong trigger config
+
+Re-run `yantra trigger show <slug>` to confirm required fields, then upsert the instance with the corrected `--config` JSON.
+
+---
+
+## Quick reference
+
+| Command                                           | What it does                               |
+| ------------------------------------------------- | ------------------------------------------ |
+| `yantra trigger list [connector]`                 | List trigger types in installed connectors |
+| `yantra trigger show <slug>`                      | Show config + payload schema for a trigger |
+| `yantra trigger simulate -f <file> <slug>`        | Validate a fixture locally                 |
+| `yantra trigger simulate ... --remote`            | Sign and POST fixture to the ingress URL   |
+| `yantra trigger instance list`                    | List all active trigger instances          |
+| `yantra trigger instance upsert --slug --account` | Create or update a trigger instance        |
+| `yantra trigger instance delete <id>`             | Permanently delete a trigger instance      |

package/lib/templates/content/connectors/subscribing-to-connector-events.md

@@ -0,0 +1,162 @@
+# Subscribing to Connector Events
+
+Connector events are delivered to your application via a webhook endpoint. This guide covers registering an endpoint, verifying signatures, handling event payloads, and testing locally.
+
+---
+
+## Registering a webhook endpoint
+
+Create a webhook endpoint to tell Yantra where to deliver trigger events:
+
+```bash
+yantra webhook create \
+  --connector airtable \
+  --url https://your-app.example.com/webhook \
+  --setup '{"signingSecret": "your-secret-here"}'
+```
+
+The command returns an endpoint record including the `webhookEndpointId` (`we_*`) you'll reference in simulations and ingress URLs.
+
+To see the setup fields a connector requires:
+
+```bash
+yantra webhook schema airtable
+```
+
+List all registered endpoints:
+
+```bash
+yantra webhook list
+```
+
+---
+
+## Handling incoming events
+
+All trigger events arrive as HTTP POST requests at your endpoint. Route on `metadata.trigger_slug` to handle each event type:
+
+```javascript
+app.post('/webhook', async (req, res) => {
+    // Always verify the signature first (see below)
+    const signature = req.headers['x-cdebase-signature'];
+    if (!verifySignature(signature, req.rawBody, SIGNING_SECRET)) {
+        return res.status(401).send('Unauthorized');
+    }
+
+    const { metadata, data } = req.body;
+
+    switch (metadata.trigger_slug) {
+        case 'AIRTABLE_RECORD_CREATED_TRIGGER':
+            await handleNewRecord(data);
+            break;
+
+        case 'GITHUB_COMMIT_EVENT':
+            await handleCommit(data);
+            break;
+
+        default:
+            console.log('Unhandled trigger:', metadata.trigger_slug);
+    }
+
+    res.json({ status: 'ok' });
+});
+```
+
+---
+
+## Verifying webhook signatures
+
+Yantra signs every delivery with HMAC-SHA256 using the `signingSecret` you provided at endpoint creation. The signature is sent in the `X-CDEBase-Signature` header as a hex string.
+
+**Always verify signatures in production** to ensure payloads are authentic.
+
+```javascript
+import crypto from 'crypto';
+
+function verifySignature(signature, rawBody, secret) {
+    const expected = crypto.createHmac('sha256', secret).update(rawBody).digest('hex');
+    return crypto.timingSafeEqual(Buffer.from(signature, 'hex'), Buffer.from(expected, 'hex'));
+}
+```
+
+---
+
+## Identifying events
+
+Every payload includes a `metadata` object that tells you exactly where the event came from:
+
+| Field                           | Description                                                              |
+| ------------------------------- | ------------------------------------------------------------------------ |
+| `metadata.trigger_slug`         | The trigger type (e.g. `AIRTABLE_RECORD_CREATED_TRIGGER`)                |
+| `metadata.trigger_instance_id`  | Which trigger instance fired — use this to match a specific subscription |
+| `metadata.connected_account_id` | Which connected account the event belongs to                             |
+| `metadata.connector`            | The connector name (e.g. `airtable`)                                     |
+
+Use `trigger_slug` to handle all events of a given type. Use `trigger_instance_id` to match events to a specific user's subscription.
+
+---
+
+## Testing locally with simulate
+
+Use `yantra trigger simulate` to validate a fixture payload locally before deploying:
+
+```bash
+# 1. Create a fixture file matching the trigger's payloadSchema
+cat > fixture.json << 'EOF'
+{
+  "record_id": "recXxxYyyZzz",
+  "fields": { "Name": "Test record", "Status": "In progress" },
+  "created_time": "2026-05-06T10:30:00Z"
+}
+EOF
+
+# 2. Validate locally — no network call
+yantra trigger simulate -f fixture.json AIRTABLE_RECORD_CREATED_TRIGGER
+```
+
+Output:
+
+```
+✓ fixture validated against AIRTABLE_RECORD_CREATED_TRIGGER payload schema
+✓ local simulate complete (no remote dispatch). Use --remote to POST to the ingress URL.
+```
+
+### Test the full pipeline remotely
+
+To sign and POST the fixture to the actual webhook ingress:
+
+```bash
+yantra trigger simulate \
+  -f fixture.json \
+  AIRTABLE_RECORD_CREATED_TRIGGER \
+  --remote \
+  --endpoint we_abc123 \
+  --signing-secret your-secret-here
+```
+
+Output:
+
+```
+→ POST https://your-server.com/api/integration/webhook_ingress/airtable/we_abc123/trigger_event
+← 200
+{"status":"ok"}
+```
+
+---
+
+## Inspecting a trigger's payload schema
+
+Before writing your handler, check exactly what fields the `data` object will contain:
+
+```bash
+yantra trigger show AIRTABLE_RECORD_CREATED_TRIGGER
+```
+
+The `payloadSchema` field describes every property the trigger will deliver.
+
+---
+
+## Next steps
+
+- [Managing Connector Triggers](managing-connector-triggers) — list, enable, disable, and delete instances
+- [Creating Connector Triggers](creating-connector-triggers) — set up trigger instances