@adminide-stack/yantra-help-browser 12.0.16-alpha.2 → 12.0.16-alpha.21

package/lib/templates/content/integrations/github-integration.md

@@ -0,0 +1,95 @@
+# GitHub Integration
+
+The GitHub integration enables your Yantra AI employee to monitor repositories, track deployments, correlate code changes with issues, and maintain engineering context.
+
+## Setup
+
+### Connecting GitHub
+
+1. Navigate to **Integrations → GitHub** in your Yantra dashboard
+2. Click **Connect GitHub**
+3. Authorize via GitHub OAuth
+4. Select the organization and repositories to monitor
+5. Configure webhook events for real-time monitoring
+
+### Permissions Requested
+
+- Read access to repositories, commits, and pull requests
+- Read access to deployments and workflow runs
+- Write access to issues and comments (for ticket creation)
+- Webhook access for real-time event processing
+
+## Capabilities
+
+### Repository Monitoring
+
+Your AI employee tracks activity across connected repositories:
+
+- **Pull requests**: New PRs, reviews, approvals, and merges
+- **Commits**: Commit messages, changed files, and authors
+- **Deployments**: Deployment events, success/failure status, and environment targets
+- **Issues**: New issues, status changes, and assignments
+- **Releases**: New releases and changelog entries
+
+### Deployment Correlation
+
+When errors spike or customer reports come in, your AI employee:
+
+- Identifies recent deployments to the affected service
+- Links specific commits and PRs to the deployment
+- Surfaces the authors and reviewers of related changes
+- Provides direct links to code diffs for rapid investigation
+
+### Code Ownership Mapping
+
+Over time, the AI employee builds a code ownership map:
+
+- Which engineers work on which modules
+- Who has expertise in specific areas
+- Historical contribution patterns
+- Suggested reviewers for PRs based on code familiarity
+
+### Automated Issue Creation
+
+When the AI employee identifies a new bug or task, it can create GitHub Issues with:
+
+- Detailed description with all correlated context
+- Links to related Sentry errors, Slack conversations, and CRM records
+- Appropriate labels and assignees based on affected code areas
+- Priority classification based on customer impact
+
+## Configuration
+
+### Repository Selection
+
+Choose which repositories to monitor:
+
+- All repositories in the organization
+- Specific repositories by team or service
+- Exclude archived or experimental repos
+
+### Event Filters
+
+Configure which events trigger AI employee attention:
+
+- All pushes to main/production branches
+- PR events (opened, reviewed, merged)
+- Deployment events (started, succeeded, failed)
+- Issue events (created, labeled, closed)
+
+### Deployment Tracking
+
+Map deployment environments to monitoring:
+
+- Production deployments → highest monitoring priority
+- Staging deployments → standard monitoring
+- Development/preview → optional monitoring
+
+## Integration with Other Tools
+
+The GitHub integration becomes powerful in combination with:
+
+- **Sentry**: Error-to-deploy correlation
+- **Linear/Jira**: PR-to-ticket linking
+- **Slack**: Context sharing in engineering channels
+- **PagerDuty**: Deploy-triggered incident correlation

package/lib/templates/content/integrations/integrations-overview.md

@@ -0,0 +1,142 @@
+# Integrations Overview
+
+Yantra AI employees connect to the tools your team already uses through secure one-click OAuth setup. No coding, no command-line configuration, no DevOps required.
+
+## How Integrations Work
+
+### Connection Process
+
+1. Navigate to **Integrations** in your Yantra dashboard
+2. Click the tool you want to connect
+3. Complete the OAuth authorization flow (same as adding any app)
+4. Select specific resources to monitor (channels, repos, projects)
+5. Your AI employee begins processing events immediately
+
+### Access Model
+
+Your AI employee receives the same level of access as a regular team member:
+
+- **Read access**: Monitor messages, events, and data across connected tools
+- **Write access**: Create records, update fields, send messages, and take actions
+- **Scoped permissions**: Only the minimum permissions required for your use case are requested
+
+All access is granted through standard OAuth 2.0 flows and can be revoked at any time.
+
+## Supported Integrations
+
+### Communication
+
+| Tool                | Read Capabilities                         | Write Capabilities                   |
+| ------------------- | ----------------------------------------- | ------------------------------------ |
+| **Slack**           | Monitor channels, threads, DMs, reactions | Send messages, create threads, react |
+| **Microsoft Teams** | Monitor channels and conversations        | Send messages, create posts          |
+| **Gmail**           | Read emails and threads                   | Draft and send emails                |
+
+### Development
+
+| Tool          | Read Capabilities                       | Write Capabilities            |
+| ------------- | --------------------------------------- | ----------------------------- |
+| **GitHub**    | Track PRs, commits, deployments, issues | Create issues, comment on PRs |
+| **GitLab**    | Track merge requests, pipelines, issues | Create issues, comment on MRs |
+| **Bitbucket** | Track PRs, commits, pipelines           | Create issues, comment on PRs |
+
+### Error Monitoring
+
+| Tool          | Read Capabilities                               | Write Capabilities                 |
+| ------------- | ----------------------------------------------- | ---------------------------------- |
+| **Sentry**    | Monitor errors, read stack traces, track trends | Update issue status, assign issues |
+| **Datadog**   | Read metrics, anomalies, APM data               | Create monitors, add comments      |
+| **PagerDuty** | Read incidents, on-call schedules               | Acknowledge, resolve incidents     |
+
+### Project Management
+
+| Tool       | Read Capabilities                 | Write Capabilities            |
+| ---------- | --------------------------------- | ----------------------------- |
+| **Linear** | Track issues, projects, cycles    | Create issues, update status  |
+| **Jira**   | Track tickets, sprints, boards    | Create tickets, update fields |
+| **Asana**  | Track tasks, projects, milestones | Create tasks, update status   |
+
+### CRM
+
+| Tool           | Read Capabilities                        | Write Capabilities                            |
+| -------------- | ---------------------------------------- | --------------------------------------------- |
+| **HubSpot**    | Read contacts, deals, activities         | Update deals, log activities, create contacts |
+| **Salesforce** | Read accounts, opportunities, activities | Update opportunities, log activities          |
+
+### Documentation
+
+| Tool           | Read Capabilities          | Write Capabilities           |
+| -------------- | -------------------------- | ---------------------------- |
+| **Notion**     | Search pages, read content | Update pages, create entries |
+| **Confluence** | Search spaces, read pages  | Update pages, add comments   |
+
+### Social Media
+
+| Tool          | Read Capabilities                | Write Capabilities               |
+| ------------- | -------------------------------- | -------------------------------- |
+| **LinkedIn**  | Read posts, comments, engagement | Draft posts, schedule publishing |
+| **X/Twitter** | Read tweets, mentions, threads   | Draft tweets, schedule threads   |
+
+### Calendars and Meetings
+
+| Tool                | Read Capabilities                 | Write Capabilities |
+| ------------------- | --------------------------------- | ------------------ |
+| **Google Calendar** | Read events, attendees            | — (read-only)      |
+| **Calendly**        | Read bookings, availability       | — (read-only)      |
+| **Zoom**            | Access recordings, transcriptions | — (read-only)      |
+
+### Additional Integrations
+
+- **Salesforce** — Enterprise CRM
+- **Mixpanel** — Product analytics
+- **Intercom** — Customer messaging
+- **Zendesk** — Customer support
+- **Freshdesk** — Help desk
+- **Stripe** — Payment events
+
+**40+ total integrations** with new ones added regularly.
+
+## Managing Integrations
+
+### Viewing Connected Tools
+
+The Integrations page shows:
+
+- All connected tools and their status (active, paused, error)
+- Permissions granted to each tool
+- Event volume processed from each integration
+- Last activity timestamp
+
+### Pausing and Reconnecting
+
+- **Pause**: Temporarily stop event processing without disconnecting
+- **Reconnect**: Re-authorize if credentials expire
+- **Disconnect**: Fully remove integration and revoke access
+
+### Monitoring Integration Health
+
+Your AI employee reports on integration status:
+
+- Connection health across all tools
+- API rate limit usage for each integration
+- Event processing latency
+- Error rates and connectivity issues
+
+## Security
+
+All integrations follow security best practices:
+
+- OAuth 2.0 authentication — your credentials are never stored
+- API keys managed through encrypted secret storage
+- Minimum required scopes — only permissions needed for requested functionality
+- All data encrypted in transit (TLS 1.2+) and at rest (AES-256)
+
+For detailed security information, see [Security Overview](/help-center/security-compliance/security-overview).
+
+## Requesting New Integrations
+
+If your team uses a tool that isn't currently supported:
+
+1. Contact support with the tool name and your use case
+2. We evaluate based on API availability and customer demand
+3. New integrations are typically added within 2-4 weeks

package/lib/templates/content/integrations/monitoring-integrations.md

@@ -0,0 +1,109 @@
+# Monitoring Tool Integrations (Sentry, Datadog, PagerDuty)
+
+Yantra integrates with monitoring and observability tools to enable intelligent error triage, deploy correlation, and smart alerting.
+
+## Sentry Integration
+
+### Setup
+
+1. Navigate to **Integrations → Sentry** in your Yantra dashboard
+2. Authorize via Sentry OAuth
+3. Select projects to monitor
+4. Configure error threshold rules
+
+### Capabilities
+
+- **Error monitoring**: Track new and recurring exceptions across projects
+- **Trend analysis**: Detect error frequency changes and pattern shifts
+- **Stack trace access**: Read full error details for root cause analysis
+- **Issue management**: Update issue status and assignments
+- **Release correlation**: Link errors to specific releases and commits
+
+### How Yantra Uses Sentry Data
+
+When errors occur, your AI employee:
+
+1. Reads the error type, message, and stack trace
+2. Checks occurrence frequency and trend direction
+3. Identifies affected users and tenants
+4. Correlates the error timing with recent deployments (via GitHub integration)
+5. Searches for existing Linear/Jira tickets for this error
+6. Delivers a complete triage summary
+
+## Datadog Integration
+
+### Setup
+
+1. Navigate to **Integrations → Datadog**
+2. Provide your Datadog API and Application keys
+3. Select metrics, monitors, and services to track
+4. Configure anomaly detection thresholds
+
+### Capabilities
+
+- **Metric monitoring**: Track custom and system metrics
+- **APM data**: Read distributed traces and service performance
+- **Anomaly detection**: Surface anomalies in tracked metrics
+- **Log access**: Search and correlate log data
+- **Monitor status**: Track existing Datadog monitors and their alerts
+
+### How Yantra Uses Datadog Data
+
+Your AI employee correlates Datadog metrics with operational events:
+
+- Latency spikes linked to specific deployments or traffic patterns
+- Error rate changes correlated with infrastructure events
+- Performance regressions detected after code changes
+- Capacity and resource utilization trends
+
+## PagerDuty Integration
+
+### Setup
+
+1. Navigate to **Integrations → PagerDuty**
+2. Authorize via PagerDuty OAuth
+3. Select services and escalation policies to monitor
+4. Configure smart escalation rules
+
+### Capabilities
+
+- **Incident monitoring**: Track active incidents and their status
+- **On-call awareness**: Know who's currently on-call for each service
+- **Incident acknowledgment**: Acknowledge and resolve incidents
+- **Escalation management**: Work with existing escalation policies
+- **Post-incident data**: Access incident timelines and metrics
+
+### Smart Alerting with PagerDuty
+
+Your AI employee enhances PagerDuty's alerting by:
+
+- **Deduplication**: Grouping related alerts before they trigger pages
+- **Context enrichment**: Adding correlated data from other tools to each incident
+- **Intelligent routing**: Recommending the right responder based on the issue type
+- **Pre-triage**: Providing a root cause hypothesis before the on-call engineer investigates
+
+## Cross-Tool Correlation
+
+The real power of monitoring integrations comes from cross-tool correlation:
+
+| Sentry Event   | + GitHub Data             | + Slack Context                | = Action                               |
+| -------------- | ------------------------- | ------------------------------ | -------------------------------------- |
+| New error type | Recent deploy identified  | Customer reported in #support  | Triage summary with full context       |
+| Error spike    | Commit that introduced it | Team discussion found          | Assignee and resolution path suggested |
+| Regression     | Reverted fix identified   | Previous resolution discussion | Exact fix steps provided               |
+
+## Configuration Best Practices
+
+### Error Thresholds
+
+- P0: 100+ errors/hour → Immediate critical escalation
+- P1: 25-100 errors/hour → Prompt notification
+- P2: 5-25 errors/hour → Batched notification
+- P3: Below 5/hour → Daily summary only
+
+### Noise Reduction
+
+- Filter out known intermittent errors
+- Set minimum occurrence thresholds before alerting
+- Group related errors by root cause before escalating
+- Suppress duplicate alerts for the same issue

package/lib/templates/content/integrations/productivity-integrations.md

@@ -0,0 +1,129 @@
+# Productivity Tool Integrations
+
+Yantra integrates with productivity and collaboration tools including Notion, Confluence, Google Calendar, Calendly, and Zoom to provide comprehensive context for your AI employees.
+
+## Notion Integration
+
+### Setup
+
+1. Navigate to **Integrations → Notion**
+2. Authorize via Notion OAuth
+3. Select workspaces and pages to index
+
+### Capabilities
+
+- **Document search**: Search across all connected Notion pages and databases
+- **Content indexing**: Index documentation, wikis, and knowledge bases
+- **Page updates**: Update existing pages with new information
+- **Database queries**: Read and filter Notion database records
+
+### Use Cases
+
+- AI employee references architecture docs when triaging bugs
+- Runbooks and procedures surfaced during incident response
+- Marketing content ideas pulled from internal strategy documents
+- Onboarding materials linked when new team members ask questions
+
+## Confluence Integration
+
+### Setup
+
+1. Navigate to **Integrations → Confluence**
+2. Authorize via Atlassian OAuth
+3. Select spaces to index
+
+### Capabilities
+
+- **Space search**: Search across connected Confluence spaces
+- **Page reading**: Read page content, comments, and attachments
+- **Comment creation**: Add comments to pages for collaboration
+- **Version tracking**: Detect page updates and content changes
+
+### Use Cases
+
+- Technical specifications referenced during code reviews
+- Past post-mortem reports surfaced during incident response
+- Product requirements linked to customer requests
+- Meeting notes and decision records searchable by the AI employee
+
+## Google Calendar Integration
+
+### Setup
+
+1. Navigate to **Integrations → Google Calendar**
+2. Authorize via Google OAuth
+3. Select calendars to monitor
+
+### Capabilities (Read-Only)
+
+- **Event monitoring**: Track upcoming meetings and events
+- **Attendee information**: Read who's attending each meeting
+- **Meeting prep**: Trigger pre-meeting context briefs
+- **Schedule awareness**: AI employee respects quiet hours and meeting times
+
+### Use Cases
+
+- Automatic pre-call briefs 30 minutes before meetings
+- Context about attendees pulled from CRM and communication history
+- Follow-up task creation after meetings based on calendar events
+- Conflict detection when scheduling follow-ups
+
+## Calendly Integration
+
+### Setup
+
+1. Navigate to **Integrations → Calendly**
+2. Authorize via Calendly OAuth
+3. Select event types to monitor
+
+### Capabilities (Read-Only)
+
+- **Booking detection**: Know when new meetings are scheduled
+- **Prospect identification**: Link Calendly bookings to CRM contacts
+- **Pre-meeting prep**: Trigger context briefs for newly booked meetings
+
+### Use Cases
+
+- Sales: Prep briefs generated automatically for every booked demo
+- Support: Customer context loaded before scheduled support calls
+- Recruiting: Candidate information compiled before interviews
+
+## Zoom Integration
+
+### Setup
+
+1. Navigate to **Integrations → Zoom**
+2. Authorize via Zoom OAuth
+3. Enable recording transcription access
+
+### Capabilities (Read-Only)
+
+- **Recording access**: Read meeting recordings and transcriptions
+- **Transcript processing**: Extract key points, action items, and decisions
+- **Participant tracking**: Know who was on each call
+
+### Use Cases
+
+- Sales: Automatic call note extraction and CRM updates after Zoom calls
+- Engineering: Meeting decisions and action items captured and tracked
+- All teams: Searchable record of every meeting's key points
+
+## Cross-Tool Context
+
+Productivity integrations enrich your AI employee's understanding:
+
+| Tool                  | Provides              | Enhances                                         |
+| --------------------- | --------------------- | ------------------------------------------------ |
+| **Notion/Confluence** | Documentation context | Bug triage, onboarding, decision context         |
+| **Google Calendar**   | Meeting schedules     | Pre-call preparation, follow-up tracking         |
+| **Calendly**          | Booking events        | Sales pipeline updates, prospect engagement      |
+| **Zoom**              | Call content          | CRM notes, action tracking, institutional memory |
+
+## Privacy Considerations
+
+- Calendar integrations are read-only — your AI employee cannot create or modify events
+- Zoom transcriptions are processed for key points only — full recordings are not stored
+- Document access respects the same permission model as your Notion/Confluence setup
+- All data from productivity tools is encrypted and follows the same security standards as other integrations
+
+See [Security Overview](/help-center/security-compliance/security-overview) for full details.

package/lib/templates/content/integrations/slack-integration.md

@@ -0,0 +1,79 @@
+# Slack Integration
+
+Slack is the most commonly connected tool for Yantra AI employees. This guide covers setup, capabilities, and configuration for the Slack integration.
+
+## Setup
+
+### Connecting Slack
+
+1. Navigate to **Integrations → Slack** in your Yantra dashboard
+2. Click **Connect Slack**
+3. Select the Slack workspace to connect
+4. Authorize the requested permissions
+5. Select channels for your AI employee to monitor
+
+### Permissions Requested
+
+- Read messages in selected channels
+- Post messages and create threads
+- React to messages
+- Access user profiles for context
+- Send direct messages (for notifications and briefs)
+
+## Capabilities
+
+### Monitoring
+
+Your AI employee monitors selected Slack channels for:
+
+- Customer reports, questions, and feedback
+- Engineering discussions about bugs, deployments, and architecture
+- Sales mentions of deals, prospects, and competitive intelligence
+- Marketing-relevant discussions and content opportunities
+- Cross-functional requests and coordination needs
+
+### Posting
+
+Your AI employee can post to Slack:
+
+- Morning briefings and daily summaries
+- Alert notifications with full context
+- Action drafts for approval ("I'd like to update HubSpot with these notes. Approve?")
+- Thread responses with correlated data from other tools
+- Proactive updates about monitored issues
+
+### Interacting
+
+Communicate with your AI employee directly in Slack:
+
+- Ask questions about any customer, project, or topic
+- Request context briefs before meetings
+- Trigger specific actions ("Update the deal stage for Acme Corp")
+- Provide feedback on alert quality and action accuracy
+
+## Channel Configuration
+
+### Monitored Channels
+
+Select which channels your AI employee should actively monitor:
+
+- **Support channels**: Customer-facing channels for issue detection
+- **Engineering channels**: Development, deployment, and incident channels
+- **Sales channels**: Deal discussions and pipeline conversations
+- **General channels**: Company-wide announcements and updates
+
+### Notification Channels
+
+Designate where the AI employee sends different types of communication:
+
+- **Daily briefings**: Sent to your DM or a dedicated briefing channel
+- **Alerts**: Sent to the relevant team channel or DM based on urgency
+- **Action requests**: Sent to DM for personal approval workflows
+
+## Best Practices
+
+1. **Start with key channels**: Connect your most important 3-5 channels first
+2. **Create a dedicated channel**: Consider a #yantra-ai channel for AI employee updates
+3. **Thread etiquette**: Configure the AI employee to respond in threads to keep channels clean
+4. **DM for approvals**: Route action approval requests to DMs to avoid channel noise
+5. **Gradual expansion**: Add more channels as you tune the AI employee's behavior