Neon Integration & Workflow Automation
Run Neon on autopilot. Keep the veto.
110 actions
Database branches and snapshots fire off inside Neon before you've had a chance to review them. Rills proposes each action, you approve before anything changes.
Interactive. No signup. 14 days free · approvals always free.
Most automation fires first, asks later. Rills shows you the change before it ships.
Every consequential communication action from Neon arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.
Queue 3
Delete 3 stale project branches from last sprint?
3 branches untouched for 18+ days
Snapshot confirmed present for each branch
Same pattern approved in previous cleanup run
Free to wait. Free to think.
Approvals and logic don't cost a credit. Pause a workflow for three hours or three weeks. The price is the same: zero. You only pay when something real happens: an AI call, an outbound action.
Approve from your phone in five seconds.
Swipe right when you're sure. Decline when you're not. Between meetings, mid-coffee, on the train. No dashboard to babysit, no inbox triage, and no surprise send you find out about after it's already out the door.
Routine cases graduate themselves.
Every approval feeds a confidence score for that exact workflow shape. The obvious cases (the ones you've green-lit fifty times) start running on their own. The judgment calls still come to you.
About Neon automation
Database state changes in Neon are quiet. A branch gets created, a snapshot gets deleted, an endpoint gets suspended, and by the time you notice something is wrong, the change has already gone through.
When Neon runs unsupervised
The operations that feel routine are the ones that cause problems. A script runs, a branch gets created or removed, and nobody catches it until something downstream breaks.
- Delete project branch by id fires without confirmation, removing work that may still be in use by another process.
- Delete project snapshot removes a restore point before anyone has verified the branch it covers is stable.
- Suspend project endpoint by id cuts off a live connection, which shows up as an outage before you see the ticket.
- Create anonymized branch goes out with default settings if no one reviews the schema against the source branch first.
- Update project compute endpoint settings changes resource allocation in ways that only surface as cost or performance problems later.
What Rills does inside Neon
Rills watches for proposed Neon automation actions, including branch creation, snapshot deletion, and endpoint suspension, and queues each one for your review before it runs. You see what the AI intends to do, the scope of the change, and any risk signals it surfaced.
The branch still gets created; you just see it before it ships.
Why Neon has no triggers and how Rills fills the gap
Neon does not emit events that can start a workflow on their own, so Rills uses scheduled checks and upstream signals to decide when to propose an action. That means you can still approve Neon changes on a schedule without polling the dashboard yourself.
- Rills checks consumption history for projects on a set schedule and proposes a snapshot or branch cleanup when usage crosses a threshold you define.
- Rills monitors schema state via get schema for project branch and proposes anonymization when a branch matches a pattern you've flagged.
- Rills queues a create branch snapshot proposal before any destructive operation runs, so you always have a restore point to approve first.
- An upstream communication event, such as a support ticket or status alert, can trigger Rills to propose a suspend project endpoint action for your review rather than firing it automatically.
What Rills can do in Neon
6 of 110 actions across reads, writes, and updates.
- 01
Create New API Key
Generate a new API key for your Neon account to enable programmatic access to your database services across different applications and environments. Store the returned key securely immediately after creation as it won't be shown again.
- 02
Create new project branch
Create an isolated copy of your database for testing and development without affecting your live data. Each branch is a complete snapshot that you can modify independently, then easily discard or merge back.
- 03
Get project connection uri
Retrieves the connection URI needed to access a specific Neon project's database, enabling you to connect applications and tools to your project's data resources.
- 04
Get consumption history projects
Retrieves detailed consumption metrics for all projects in your Neon organization, including compute time, storage usage, and data written. Use this to understand resource usage patterns and optimize your database infrastructure costs.
- 05
Create branch database
Creates a new database within a Neon project branch, enabling you to set up isolated database instances for different environments or applications. This is essential for organizing your data infrastructure as your projects grow or when you need separate databases for testing, staging, and production environments.
- 06
Create compute endpoint
Sets up a new database compute instance for your Neon project branch with customizable performance settings, autoscaling, and connection pooling to match your application's needs.
Common questions about Neon automation
How do I automate Neon branch deletion without breaking production?
Rills proposes the branch deletion before anything executes. You review the branch ID, confirm it is not tied to a live environment, and approve from your phone. Nothing deletes until you say so. Neon automation with a veto at every step means a misfire is a notification, not an outage.
Can I get mobile approvals before a Neon project branch is anonymized?
Yes. When Rills queues a branch anonymization, it sends the proposed action to your mobile approval queue. You see which branch is targeted and approve or reject from your phone before it starts. No dashboard required, no guessing after the fact.
How do I automate Neon snapshot deletion across multiple projects?
Rills can queue snapshot deletions across your Neon projects and hold each one for your review. You see exactly which snapshot is proposed for deletion and approve individually or in bulk. Nothing ships until you clear it, so a wrong project ID does not cost you a restore point.
Can Rills automatically suspend a Neon endpoint when usage spikes?
Rills can propose a suspend action against a specific endpoint ID when your defined conditions are met. It waits for your approval before the suspend fires. You stay in control of which endpoints get paused, and the action only executes after you confirm it is the right call.
How do I manage Neon org API key deletion without an accidental lockout?
Rills queues the deletion and surfaces the key details for your review before anything is removed. You approve from your phone, or you reject and nothing changes. Accidental lockouts happen when automation moves faster than review; Rills does not move until you approve.
How is Rills different from Zapier for Neon automation?
Zapier executes when the trigger fires. Rills proposes the action and waits for your approval before it executes. For Neon operations like branch deletion, endpoint suspension, or API key removal, that pause is the entire point. You get Neon automation without giving up the veto.
Does Rills support Neon scheduled or recurring actions?
Rills can run Neon automation on a schedule, such as pulling consumption history or listing branches at regular intervals. Each proposed action still enters your approval queue unless you have explicitly set a workflow to run autonomously. Confidence scoring learns over time, so routine actions can graduate to autonomous as trust builds.
How much does Rills cost for Neon automation?
Approvals and all workflow logic are free. You only pay when Rills executes a real action, such as an AI call or an external API operation against your Neon projects. Reviewing, rejecting, and managing your approval queue never costs anything.