• Product Introduction
  • Quick Start
    • Agent Development
    • Importing a Git Repository
    • Starting From a Template
    • Direct Upload
    • Start with AI
  • Framework Guide
    • Agent
    • Frontends
      • Vite
      • React
      • Vue
      • Hugo
      • Other Frameworks
    • Backends
    • Full-stack
      • Next.js
      • Nuxt
      • Astro
      • React Router
      • SvelteKit
      • TanStack Start
      • Vike
    • Custom 404 Page
  • Project Guide
    • Project Management
    • edgeone.json
    • Configuring Cache
    • Building Output Configuration
    • Error Codes
  • Build Guide
  • Deployment Guide
    • Overview
    • Create Deploys
    • Manage Deploys
    • Deploy Button
    • Using Github Actions
    • Using Gitlab CI/CD
    • Using CNB Plugin
    • Using IDE PlugIn
    • Using CodeBuddy IDE
  • Domain Management
    • Overview
    • Custom Domain
    • HTTPS Configuration
      • Overview
      • Apply for Free Certificate
      • Using Managed SSL Certificate
    • Configure DNS CNAME Record
  • Observability
    • Overview
    • Metric Analysis
    • Log Analysis
  • Functions
    • Overview
    • Edge Functions
    • Cloud Functions
      • Overview
      • Node.js
      • Python
      • Go
  • Agents
    • Overview
    • Quick Start
    • Conversation Storage
    • Observability
    • Sandbox Tool
      • Overview
      • Using the Agent Framework
      • Sandbox Atomic API
      • Network Search Tool
    • Agent Authentication
  • Models
    • Overview
    • Models and Vendors
      • Overview
      • Using Vendor Keys
        • OpenAI
        • Anthropic
        • Google AI Studio
        • DeepSeek
        • MiniMax
        • Hunyuan
        • Zhipu
        • MoonShot AI
    • FAQs
  • Storage
    • Overview
    • KV
    • Blob
  • Middleware
  • AI-Native Development
    • Skills
    • MCP
  • Copilot
    • Overview
    • Quick Start
  • API Token
  • EdgeOne CLI
  • Message Notification
  • Integration Guide
    • AI
      • Dialogue Large Models Integration
      • Large Models for Images Integration
    • Database
      • Supabase Integration
      • Pages KV Integration
    • Ecommerce
      • Shopify Integration
      • WooCommerce Integration
    • Payment
      • Stripe Integration
      • Integrating Paddle
    • CMS
      • WordPress Integration
      • Contentful Integration
      • Sanity Integration
      • Payload Integration
    • Authentication
      • Supabase Integration
      • Clerk Integration
  • Best Practices
    • Adding an AI Chat Assistant to a Website
    • AI Dialogue Deployment: Deploy Project with One Sentence Using Skill
    • Using General Large Model to Quickly Build AI Application
    • Use the DeepSeek model to quickly build a conversational AI site
    • Building an Ecommerce Platform with Shopify
    • Building a SaaS Site Using Supabase and Stripe
    • Building a Company Brand Site Quickly
    • How to Quickly Build a Blog Site
  • Migration Guides
    • Migrating from Vercel to EdgeOne Makers
    • Migrating from Cloudflare Pages to EdgeOne Makers
    • Migrating from Netlify to EdgeOne Makers
  • Troubleshooting
  • FAQs
  • Limits
  • Pricing
  • Contact Us
  • Release Notes

Create Deploys

This section describes several different ways to trigger the deployment of Makers projects.

Git Auto-Trigger Deployment

After you associate a Makers project with a Git repository, the system automatically listens for push events and triggers deployments. Currently, by default, only commits to the main branch automatically trigger deployments.

Manual Triggering Deployment

In the Makers console, you can manually trigger deployment in the following ways:
Click Redeploy in the Project List to rebuild the latest deployment configuration.
Select a specific deployment record from the deployment record for redeployment.

Webhook

In addition to the methods above, you can also trigger deployments via webhooks. Each trigger event is a unique URL that initiates a new deployment through an HTTP POST request. This feature enables you to integrate Makers into your workflow.
Use cases:
Automatically build and deploy when the content in the headless CMS changes.
Implement a fully custom CI/CD process and deploy only when specific conditions are met.
Set a scheduled task to update the website at a fixed time.
Trigger deployment through a third-party service, such as auto-update after payment is successful.
Directions:
1. Enter the console, open the project settings page, and find the "Webhook" module.
2. Click Create a new webhook, enter the name, select the branch, and then click Confirm.
3. After creation, you can call the API via a POST request within the project to trigger the deployment of the corresponding branch.
Warning:
Webhook are uniquely associated with your project and do not require additional authentication. Please ensure these URLs are properly protected to avoid leakage. If unauthorized usage is suspected, immediately delete and regenerate the hooks.

Integrating Webhook with Common CMS Platforms

The integration methods vary for each CMS provider. Following is a step-by-step guide using Ghost as an example.
You can configure your Ghost site to trigger EdgeOne Makers deployments by creating a new custom integration. In your Ghost site's settings, go to the Integrations page and create a new custom integration.



Each custom integration can have multiple webhooks attached. Select "Add Webhook" and set the event to "Post Published". Then, paste your unique deployment hook URL into the target URL field. After this webhook is created, the EdgeOne Makers application will automatically redeploy whenever your Ghost site publishes an article.







ai-agent
You can ask me like
How to Get Started with EdgeOne Makers?