Create a Neon preview branch for every pull request
Open a pull request and get a matching database environment without stopping to configure one.
Trigger
New Pull Request Created
Fires when a new pull request is created in GitHub.
Action
Create new project branch
Why this helps
Creating and naming preview databases manually breaks focus and often gets skipped during fast-moving work.
- Removes repetitive preview-environment setup
- Keeps pull-request testing isolated
- Creates a predictable branch for collaborators
Setup
Build it in a few focused steps.
- 1Connect GitHub and Neon to Notis once through the portal.
- 2Create an automation in the portal or ask Notis in plain language to create a Neon branch for each new pull request, using the repository and pull-request context.
- 3Select the GitHub New Pull Request Created trigger and choose where Notis should report runs.
- 4Test it with one real pull request and confirm the Neon branch is created.
Questions about this workflow
Does this run for every pull request?
Yes, unless you describe a narrower rule in the plain-language instruction, such as only pull requests targeting a particular branch.
Where does Notis report the result?
You choose a reporting channel when creating the automation, and Notis posts the branch result there.
When this happens · Trigger
Fires when a new pull request is created in GitHub.
Do this · Action
Accepting a transfer irreversibly changes project ownership and consumes the request; confirm the destination first.
Conditions and details
The project moves to the authenticated account or the specified organization. Confirm the destination before accepting. Do not retry after an ambiguous failure because the transfer may already have completed.
Supported Triggers and Actions
Notis builds workflows that link GitHub to Neon. A trigger fires from one place; an action lands in another.
GitHub triggers
Neon actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept project transfer request
Accepting a transfer irreversibly changes project ownership and consumes the request; confirm the destination first.
Conditions and details
The project moves to the authenticated account or the specified organization. Confirm the destination before accepting. Do not retry after an ambiguous failure because the transfer may already have completed.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create API key
Create a personal API key; its secret is shown once, so store it securely when created.
New Workflow Artifact Created
Fires when a new GitHub Actions workflow artifact is created in a repository.
Create api key for organization
Create an organization API key; its value is shown once and cannot be retrieved later.
Branch Changed
Fires when a branch’s commits or protection status or settings change.
Create branch database
Create a database within a project branch.
New Branch Created
Fires when a new branch is created in a GitHub repository.
Count project branches
Counts branches in a project, optionally matching a branch name.
Check Run Status / Conclusion Changed
Fires when a GitHub check run’s status or conclusion changes.
Create compute endpoint
Create a compute endpoint to connect to a branch or add a read replica.
Check Suite Status / Conclusion Changed
Fires when a GitHub check suite changes status or conclusion for a reference.
Create Auth Provider SDK Keys
Generates SDK or API keys for authentication providers.
New Code Scanning Alert Created
Fires when a new code scanning alert is created in a repository.
Create auth user
Creates a Neon Auth user on a branch where Neon Auth is configured.
Connect any two apps with Notis in the middle.
GitHub and Neon, or any other combination from 1,500+ 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 Neon.