Skip to content

Automate Neon

Look after your Neon projects without logging in every day: usage per project, storage creeping toward a limit, failed operations, stale preview branches and nightly backup branches. Some automations only report, others create or delete branches on a schedule you set. Explain the job to your AI assistant, read through what it plans to change, and it carries on after you close the chat.

Try asking

Create a ClickRuntime automation: every Monday at 9am, email me the compute hours and storage used by each of my Neon projects over the last week.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Build your own

Build any Neon automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Neon should do in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.
  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Every night, run a query on my Neon Postgres database for accounts with no logins in 30 days and email me the list.

Every morning, run my daily signups query on Neon and post the number to Slack.

Every Monday, run my weekly metrics queries on Neon, write the results to Google Sheets, and email the team a short AI summary of what changed.

Beyond chat

Have Neon work when you're not in the chat

Connecting Neon to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect Neon

Neon connects with an API key you create in the Neon Console. A project-scoped key is the safest choice, since it can only touch the one project it belongs to.

Neon

Developer / Database (serverless Postgres)

  1. In the Neon Console, open Account settings and then API keys. For an organization key, use Organization settings and API keys instead (admins only); project-scoped keys are also available.
  2. Click Create, give the key a name, and copy it straight away, because Neon shows it only once.
  3. In the ClickRuntime dashboard, open Connections & secrets and save the key as a secret for Neon.

Good to know

Neon limits that affect automations

  • The API key manages projects, branches and operations. Running SQL against your database needs a separate Postgres connection string.
  • Revoking a key takes effect at once and cannot be undone, so any automation using it stops until you add a new key.
  • Detailed consumption history is only available on some Neon plans; on others the usage report uses the per-project figures from the project list.
  • Branches count toward your plan's branch and storage limits, which is why the backup automation deletes older backup- branches.

FAQ

Questions about automating Neon

Can ClickRuntime delete my Neon branches?
Only if you ask for it and the key allows it. The clean-up and backup automations delete branches by age and name, and the backup one only touches branches starting with `backup-`. A dry run that lists what would go is a sensible first step.
Which kind of Neon API key should I use?
A project-scoped key if the automation works on one project, since it limits what the key can reach. Use a personal or organization key when a report needs to cover every project.
Can it query the tables in my database?
Not with the API key alone. Queries need a Postgres connection string, which is separate from the key used for these automations.
How quickly does a failed operation show up?
The check looks at recent operations every 15 minutes and only reports ones it has not seen before, so you get each failure once.
Do I have to bring an AI key for Neon automations?
No. The ready automations do not use AI at all, and anything that does runs on the AI that every ClickRuntime plan includes.
Is this a Neon connector for ChatGPT or Claude?
Not for chatting with Neon data. A chat connector lets your assistant read and change Neon while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each Neon event.

Tell your assistant what Neon should do

Free plan. No credit card.