Netlify
Askel connects to your customer's Netlify account and lets your product trigger deploys, read build status, and manage site configuration in the hosting platform their frontend teams use.
What you can do
Trigger deploys on a specific site
Use the Netlify deploys endpoint to start a new build-and-deploy on any site the API token can access, with an optional clear cache flag.
Poll deploy status to completion
Fetch the deploy state (building, processing, ready, error) using the deploy ID and poll until the deploy reaches a terminal state, returning the deploy URL on success.
List sites and their deploy history
Enumerate all sites in the account and fetch recent deploy history for a given site, useful for showing deployment activity in your product's dashboard.
Read and update site environment variables
Fetch and write environment variables on a Netlify site using the environment variables API, useful for propagating credentials or config values from your product.
Create deploy previews from branches
Trigger a deploy from a specific git branch by passing the branch name in the deploy request, producing a preview URL without touching the production deployment.
Read build logs
Fetch the deploy log messages for a specific deploy ID so your product can surface build errors without requiring the customer to open the Netlify dashboard.
Triggering a Netlify deploy when a customer's content is approved
You sell a headless CMS platform. Silverleaf Agency publishes all content through Netlify. When a content editor approves a piece of content in your product, a new Netlify deploy should start automatically and your product should report the live deploy URL once the build completes.
- 1
Generate an access token
Silverleaf's admin navigates to app.netlify.com, opens User Settings, then Applications, and creates a New access token. They paste it into your product's integration settings.
- 2
Identify the target site
Askel calls the Netlify sites endpoint to list all sites the token can access. Your onboarding team picks the customer's production site and stores its site ID.
- 3
Content approval triggers deploy
When a content editor clicks Approve in your product, the workflow fires. Askel calls the Netlify deploys endpoint with the production site ID and a clear-cache flag.
- 4
Poll for build completion
Askel polls the deploy status every 15 seconds until the state is ready or error. Build log messages are streamed back to your product for display.
- 5
Report the deploy URL
Once the deploy reaches ready, Askel returns the deploy URL to your product. The content editor sees a confirmation with a link to the live page.
API token
The customer's Netlify user navigates to app.netlify.com/user/applications and creates a Personal access token by clicking New access token. Askel stores the token and uses it for all API calls. Personal access tokens have the same permissions as the creating user and can be revoked from the same settings page.
How Askel sits between your product and the customer's system
FAQ for Netlify
Which Netlify plans include API access?+
Can we deploy a specific git commit rather than the latest branch tip?+
What happens if a deploy fails?+
Can we manage multiple Netlify sites for the same customer?+
catching drift before it breaks, and hitting go-live dates.
© 2025 Askel.ai. All rights reserved.