improvement(templates): make it top-level route and change management/editing process

[icecrasher321]

Summary

New system for Templates to be based on creator profiles and public accessibility.

Type of Change

• New feature

Testing

Tested manually.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Ready	Preview	Comment	Nov 8, 2025 1:57am

[greptile-apps]

Greptile Overview

Greptile Summary

This PR transforms templates from user-owned resources to a public marketplace with creator profiles and approval workflow.

Key Changes

• Database restructure: New template_creators table separates creator identity from templates, supporting both user and organization profiles. Templates table drops user ownership and category-based organization in favor of status-based approval workflow (pending, approved, rejected)

• Approval workflow: All new templates start as pending and require super user approval before becoming publicly visible. Super users can approve/reject templates through new API endpoints

• Creator profiles: Users and organizations can create branded profiles with social links, profile pictures, and descriptions. Templates are published under these profiles, enabling professional branding

• Credential extraction: New credential-extractor.ts utility identifies OAuth and secret requirements in workflows, sanitizes credentials from template state, and stores requirements separately for users to configure when using templates

• Public access: /templates route is now public (no auth required) for SEO and discovery. Middleware allows unauthenticated access, and pages handle both logged-in and anonymous users

• Template management: Templates can be "used" in two modes: (1) copy mode creates a new workflow with regenerated IDs, or (2) connect mode links the template to an editable workflow. Updates to connected workflows can sync back to templates via explicit "Update Template" action

• Super user system: New isSuperUser flag on users with superUserModeEnabled setting to toggle the mode on/off in UI

Issues Found

None - the implementation is thorough and well-structured.

Confidence Score: 4/5

• This PR is safe to merge with minimal risk - comprehensive refactor with proper authorization and data sanitization
• Score reflects a well-architected feature with strong security controls (super user approval, creator profile permissions, credential sanitization) and thorough implementation across database, API, and UI layers. The migration safely drops columns while adding new structures. Minor caution warranted due to: (1) large scope touching 53 files, (2) breaking schema changes requiring careful deployment coordination, and (3) complex workflow state manipulation logic that could have edge cases in production
• Pay close attention to packages/db/migrations/0107_silky_agent_brand.sql to ensure existing template data migration strategy is planned, and apps/sim/lib/workflows/credential-extractor.ts for edge cases in credential detection across different block types

Important Files Changed

File Analysis

Filename	Score	Overview
packages/db/schema.ts	4/5	Major restructure of templates table: removes user-based ownership, adds creator profiles, approval workflow, and credential tracking
packages/db/migrations/0107_silky_agent_brand.sql	4/5	Database migration creates template_creators table, drops old template columns, and restructures relationships
apps/sim/app/api/templates/route.ts	4/5	Major refactor: templates now require deployment, use creator profiles, extract/sanitize credentials, and start with pending status
apps/sim/app/api/templates/[id]/route.ts	4/5	Updated GET/PUT/DELETE with creator profile authorization, public access for approved templates, and state synchronization
apps/sim/app/api/creator-profiles/route.ts	5/5	New creator profile API with user/org permissions, duplicate prevention, and proper validation
apps/sim/lib/workflows/credential-extractor.ts	5/5	New utility for extracting credential requirements and sanitizing workflow state for sharing/templates
apps/sim/middleware.ts	5/5	Added public access to /templates route for SEO and unauthenticated viewing
apps/sim/app/templates/page.tsx	5/5	New top-level public template page with super user mode support and approval status filtering

Sequence Diagram

sequenceDiagram
participant User
participant Browser
participant Middleware
participant TemplatesPage
participant TemplateAPI
participant CreatorProfileAPI
participant DB
participant WorkflowAPI
Note over User,WorkflowAPI: Template Publishing Flow
User->>Browser: Navigate to Settings
Browser->>CreatorProfileAPI: GET /api/creator-profiles
CreatorProfileAPI->>DB: Query template_creators
DB-->>CreatorProfileAPI: Return profiles
CreatorProfileAPI-->>Browser: Creator profiles
User->>Browser: Create/Update Creator Profile
Browser->>CreatorProfileAPI: POST /api/creator-profiles
CreatorProfileAPI->>DB: Verify permissions (user/org membership)
CreatorProfileAPI->>DB: Insert/Update template_creators
DB-->>CreatorProfileAPI: Profile created
CreatorProfileAPI-->>Browser: Success
User->>Browser: Deploy Workflow as Template
Browser->>TemplateAPI: POST /api/templates
TemplateAPI->>DB: Verify workflow deployed
TemplateAPI->>DB: Verify creator profile permissions
TemplateAPI->>WorkflowAPI: GET active deployment version
WorkflowAPI-->>TemplateAPI: Workflow state
TemplateAPI->>TemplateAPI: Extract credentials (extractRequiredCredentials)
TemplateAPI->>TemplateAPI: Sanitize state (sanitizeCredentials)
TemplateAPI->>DB: Insert template (status: pending)
DB-->>TemplateAPI: Template created
TemplateAPI-->>Browser: Template submitted for approval
Note over User,WorkflowAPI: Super User Approval Flow
User->>Browser: View pending templates (super user mode)
Browser->>TemplatesPage: GET /templates?includeAllStatuses=true
TemplatesPage->>DB: Query templates (check isSuperUser)
DB-->>TemplatesPage: All templates
User->>Browser: Approve template
Browser->>TemplateAPI: POST /api/templates/{id}/approve
TemplateAPI->>DB: Verify user is super user
TemplateAPI->>DB: Update template status = approved
DB-->>TemplateAPI: Success
TemplateAPI-->>Browser: Template approved
Note over User,WorkflowAPI: Public Template Viewing Flow
User->>Browser: Navigate to /templates
Browser->>Middleware: Check authentication
Middleware-->>Browser: Allow (public route)
Browser->>TemplatesPage: GET /templates
TemplatesPage->>DB: Query approved templates only
DB-->>TemplatesPage: Approved templates with creators
TemplatesPage-->>Browser: Render template gallery
Note over User,WorkflowAPI: Template Usage Flow
User->>Browser: Click "Use Template"
Browser->>TemplateAPI: POST /api/templates/{id}/use
TemplateAPI->>DB: Get template state
TemplateAPI->>DB: Increment views counter
TemplateAPI->>TemplateAPI: Remap variable IDs
TemplateAPI->>DB: Create new workflow
TemplateAPI->>WorkflowAPI: PUT /api/workflows/{id}/state
WorkflowAPI->>DB: Save workflow state (normalized tables)
WorkflowAPI-->>TemplateAPI: Success
TemplateAPI->>DB: Create deployment version (if connected)
DB-->>TemplateAPI: Workflow created
TemplateAPI-->>Browser: Redirect to workflow editor

Loading

_{53 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}