--- title: "Connect incident.io to Neon Postgres - APIANT.ai" description: "When \"New Incident\" fires in incident.io, your agent runs \"Add project\" in Neon Postgres." canonical: "https://apiant.ai/connect/incident-io-to-neon-postgres" --- # Connect incident.io to Neon Postgres When **New Incident** fires in [incident.io](https://apiant.ai/connections/incident-io), your agent runs **Add project** in [Neon Postgres](https://apiant.ai/connections/neon-postgres). Describe the whole flow and it is built, tested on every scenario and kept running. incident.io **1** trigger incident.io **10** actions Neon Postgres **29** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want incident.io and Neon Postgres to do together? Give your AI client this address. `https://mcp.apiant.ai` One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser. ### Set it up in your client ### Claude Code Run this in the directory you want to work in. `claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### Claude, web and desktop Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Cursor Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Codex and the ChatGPT desktop app Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Any other MCP client Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) Example flows ## What incident.io can start in Neon Postgres - When **New Incident** in incident.io then **Add project** in Neon Postgres - When **New Incident** in incident.io then **Add branch** in Neon Postgres Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships. Everything your agent can do with incident.io and Neon Postgres ## Triggers and actions 1 trigger · 39 actions - Trigger **New Incident** Triggers when a new incident is declared in incident.io, optionally limited to a status, severity, incident type or mode. - Action **Add follow-up** Creates a follow-up on an incident, with an optional description, assignee, team, category, priority and labels. - Action **Add incident update** Shares an update on an incident: a message, a move to a new status, a new severity, or any combination. - Action **Create Incident** Creates a new incident in incident.io, optionally setting its severity, type, status, roles, timestamps and custom fields. - Action **Find Users On-Call** Finds the users on-call for a schedule over a window of time (or right now), returning each effective shift with its user after overrides are applied. - Action **Get incident** Returns a single incident, including its status, severity, role assignments, timestamps and custom field values. - Action **Get Schedule** Returns a single on-call schedule, including its rotations, time zone and current shifts. - Action **List actions** Returns the actions recorded on incidents in your incident.io organisation, optionally filtered by incident, incident mode, or created/updated date. - Action **List schedules** Returns every on-call schedule configured in your incident.io account, including its rotations and who is currently on shift. - Action **List severities** Returns every incident severity configured for your incident.io organisation. - Action **List users** Returns the users in your incident.io account, optionally filtered by email address or Slack user ID. - Action **Add branch** Create a new branch in a Neon project. - Action **Add compute endpoint** Creates a compute endpoint (a Neon compute instance) on a branch of a Neon project. A branch can have one read-write endpoint and multiple read-only endpoints. - Action **Add database** Creates a new Postgres database in a Neon project branch, owned by an existing role. - Action **Add project** Creates a new Neon Postgres project with its default branch, database, role and compute, and returns the project along with its connection details. - Action **Add role** Creates a Postgres role in the specified Neon project branch. Connections to the branch's active compute are dropped while the change applies. - Action **Delete branch** Delete a branch by project_id and branch_id. - Action **Delete compute endpoint** Deletes a compute endpoint from a Neon project. Existing connections to the compute are dropped. If the compute does not exist or was already deleted, the step still succeeds with an empty result. - Action **Delete database** Deletes the specified database from a branch of a Neon project. - Action **Delete project** Deletes a Neon project and all its branches, compute endpoints, databases and roles. The project can be recovered within 7 days. - Action **Delete role** Deletes the specified Postgres role from a Neon branch. - Action **Get branch** Retrieves details of a branch in a Neon project. - Action **Get compute endpoint** Retrieve details about a compute endpoint. - Action **Get connection URI** Retrieve a Postgres connection URI for a database/role/branch/endpoint combination. - Action **Get database** Retrieves details of a database on a Neon project branch. - Action **Get project** Retrieves the details of a Neon project, including its settings, compute configuration, history retention, owner and current usage metrics. - Action **Get role** Retrieves details about a Postgres role (user) on a Neon branch. - Action **Get role password** Retrieves the password for a Postgres role on a Neon branch. - Action **List branches** Retrieve a list of branches for a Neon project. - Action **List compute endpoints** Lists the compute endpoints (Neon compute instances) in a project. - Action **List databases** Lists the databases on a branch of a Neon project. - Action **List operations** Lists the operations (asynchronous actions such as starting a compute or creating a branch) Neon performed on a project. Operations older than 6 months may no longer be available. - Action **List projects** Lists the Neon projects accessible to the connected account, optionally filtered by name/ID or organization. - Action **List roles** Lists the Postgres roles on a Neon project branch. - Action **Start compute endpoint** Start (resume) a suspended compute endpoint. - Action **Suspend compute endpoint** Suspends the specified Neon compute endpoint (scales it to zero). - Action **Update branch** Update a branch's properties (e.g. name, protected) by project_id and branch_id. - Action **Update compute endpoint** Updates an existing compute endpoint in a Neon project by ID. - Action **Update database** Updates the name or owner of a database on a Neon project branch. - Action **Update project** Update settings for a Neon project by project_id. ## Each app on its own - [ **incident.io** incident.io is an incident management platform, designed for your entire organisation.](https://apiant.ai/connections/incident-io) - [ **Neon Postgres** Serverless PostgreSQL database platform offering instant branching, autoscaling, and an auto-generated REST...](https://apiant.ai/connections/neon-postgres) Reviews ## What our customers say ## More from incident.io - [ **incident.io to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/incident-io-to-salesforce) - [ **incident.io to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/incident-io-to-slack) - [ **incident.io to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/incident-io-to-mailchimp) - [ **incident.io to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/incident-io-to-stripe) - [ **incident.io to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/incident-io-to-shopify) - [ **incident.io to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/incident-io-to-quickbooks-online) ## More into Neon Postgres - [ **Vimeo OTT to Neon Postgres** Vimeo OTT (formerly VHX) is an over-the-top video monetization platform for launching subscription and...](https://apiant.ai/connect/vimeo-ott-to-neon-postgres) - [ **HubSpot to Neon Postgres** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-neon-postgres) - [ **Salesforce to Neon Postgres** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-neon-postgres) - [ **Slack to Neon Postgres** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-neon-postgres) - [ **Google Sheets to Neon Postgres** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-neon-postgres) - [ **Gmail to Neon Postgres** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-neon-postgres) Questions ## incident.io and Neon Postgres, answered ### ### What can start an automation from incident.io? Any of incident.io's 1 trigger in the catalog, including New Incident. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Neon Postgres when something happens in incident.io? Any of Neon Postgres's 29 actions, including Update branch, Update compute endpoint, Update database and Update project. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Neon Postgres to incident.io? Neon Postgres has no triggers in the catalog today, so automations start in incident.io. If you need the other direction, ask: your agent reads Neon Postgres's API documentation and adds it. ### ### Do I have to build a connector for incident.io or Neon Postgres? No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running. ### ### Can my AI client use incident.io and Neon Postgres without building an automation? Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both. ### ### What happens when something fails? Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships. ### ### Is there a free plan? Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.