Deploy Vercel when website content changes
Publish approved site edits without leaving a small but important follow-up behind.
Trigger
Repository Content Changed
Triggers when the content of a file or directory in a GitHub repository changes. Monitors a specified path within a repository on a given branch or tag. For a single file, fires ``content_changed`` when the file is modified. For a directory, fires ``content_changed``, ``content_added``, or ``content_removed`` for modified, new, or deleted entries respectively. content.
Action
Create new deployment
Tool to create a new deployment. use when you need to deploy files or a git commit to a vercel project.
Why this helps
Content fixes can be committed successfully but still wait for someone to remember the deployment step.
- Speeds up small site updates
- Avoids forgotten publishing steps
- Protects focus for higher-value work
Setup
Build it in a few focused steps.
- 1Connect GitHub and Vercel through Notis once.
- 2Create a new automation and name it for website publishing.
- 3Write an instruction to create a Vercel deployment after the monitored content path changes, select the repository-content trigger, choose reports, and test a real content edit.
Questions about this workflow
Can I limit the workflow to a directory?
Yes. Describe the content path you want monitored.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Vercel. A trigger fires from one place; an action lands in another.
GitHub triggers
Vercel actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Environment Variable
Tool to add an environment variable to a vercel project. use after confirming the project exists and you need to configure secrets or configuration values across environments before deployment. example: "add api key=secret to production".
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Check Cache Artifact Exists
Tool to check if a cache artifact exists by its hash. use when verifying whether a cache artifact is already stored before upload.
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Check Domain Availability
Tool to check if a domain is available for registration. use when you need to verify domain availability before purchase.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Check Domain Price
Tool to check the price for a domain before purchase. use when evaluating cost and availability prior to domain registration.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Create Auth Token
Tool to create a new authentication token. use when you need to programmatically generate a new token after validating permissions. example: "create auth token named my-token"
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Create Edge Config
Tool to create a new edge config for a vercel project. use when you need to define edge caching settings before deploying your project across a specified repository.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
Create Edge Config Token
Tool to create a new token for a specific edge config. use when you need a read-only access token after provisioning your edge config.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Create new deployment
Tool to create a new deployment. use when you need to deploy files or a git commit to a vercel project.
Connect any two apps with Notis in the middle.
GitHub and Vercel, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Vercel.