Appearance
Neon
Manage serverless Postgres projects, branches, databases, and endpoints with Neon.
| Detail | Value |
|---|---|
| Category | Database |
| Base URL | https://console.neon.tech/api/v2 |
| Authentication | Bearer Token |
| Endpoints | 8 |
| Connector key | neon |
Using Neon in a workflow
- Go to Connections and click New Connection.
- Pick Neon from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /projects | List projects |
POST /projects | Create a project |
GET /projects/{project_id} | Get project details |
DELETE /projects/{project_id} | Delete a project |
GET /projects/{project_id}/branches | List branches |
POST /projects/{project_id}/branches | Create a branch |
GET /projects/{project_id}/endpoints | List endpoints |
GET /projects/{project_id}/operations | List operations |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /projects
List projects
| Detail | Value |
|---|---|
| Operation ID | database.listProjects |
| Method | GET |
| Path | /projects |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Neon connection from the Connection dropdown.
- In the Operation dropdown, select
database.listProjects. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Neon API reference.
POST /projects
Create a project
| Detail | Value |
|---|---|
| Operation ID | database.createProject |
| Method | POST |
| Path | /projects |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Neon connection from the Connection dropdown.
- In the Operation dropdown, select
database.createProject. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Neon API reference.
GET /projects/{project_id}
Get project details
| Detail | Value |
|---|---|
| Operation ID | database.getProject |
| Method | GET |
| Path | /projects/{project_id} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Neon connection from the Connection dropdown.
- In the Operation dropdown, select
database.getProject. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Neon API reference.
DELETE /projects/{project_id}
Delete a project
| Detail | Value |
|---|---|
| Operation ID | database.deleteProject |
| Method | DELETE |
| Path | /projects/{project_id} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Neon connection from the Connection dropdown.
- In the Operation dropdown, select
database.deleteProject. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Neon API reference.
GET /projects/{project_id}/branches
List branches
| Detail | Value |
|---|---|
| Operation ID | database.listBranches |
| Method | GET |
| Path | /projects/{project_id}/branches |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Neon connection from the Connection dropdown.
- In the Operation dropdown, select
database.listBranches. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Neon API reference.
POST /projects/{project_id}/branches
Create a branch
| Detail | Value |
|---|---|
| Operation ID | database.createBranch |
| Method | POST |
| Path | /projects/{project_id}/branches |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Neon connection from the Connection dropdown.
- In the Operation dropdown, select
database.createBranch. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Neon API reference.
GET /projects/{project_id}/endpoints
List endpoints
| Detail | Value |
|---|---|
| Operation ID | database.listEndpoints |
| Method | GET |
| Path | /projects/{project_id}/endpoints |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Neon connection from the Connection dropdown.
- In the Operation dropdown, select
database.listEndpoints. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Neon API reference.
GET /projects/{project_id}/operations
List operations
| Detail | Value |
|---|---|
| Operation ID | database.listOperations |
| Method | GET |
| Path | /projects/{project_id}/operations |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Neon connection from the Connection dropdown.
- In the Operation dropdown, select
database.listOperations. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Neon API reference.