--- title: "Connect COR to Neon Postgres - APIANT.ai" description: "When \"Create Brand\" fires in COR, your agent runs \"Add project\" in Neon Postgres." canonical: "https://apiant.ai/connect/cor-to-neon-postgres" --- # Connect COR to Neon Postgres When **Create Brand** fires in [COR](https://apiant.ai/connections/cor), 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. COR **12** triggers COR **24** 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 COR 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 COR can start in Neon Postgres - When **Create Brand** in COR then **Add project** in Neon Postgres - When **Create Client** in COR 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 COR and Neon Postgres ## Triggers and actions 12 triggers · 53 actions - Trigger **Create Brand** Triggers when a new brand is created in COR. - Trigger **Create Client** Triggers when a new client is created in COR. - Trigger **Create Hour** Triggers when a new time entry is logged in COR. - Trigger **Create Invoice** Triggers when a new transaction is recorded in COR. COR has no separate invoice record, so this watches all transactions, invoices included; use the type field to tell them apart. - Trigger **Create Product** Triggers when a new product is created in COR. - Trigger **Create Project** Triggers when a new project is created in COR. - Trigger **Create Task** Triggers when a new task is created in COR. Returns the new task's details. - Trigger **Create User** Triggers when a new user is created in COR. - Trigger **Updated Client** Triggers when an existing client is changed in COR. - Trigger **Updated Project** Triggers when an existing project is updated in COR. - Trigger **Updated Task** Triggers when a task is changed, such as a new title, status, priority or deadline. Also fires when a new task appears. - Trigger **Updated User** Triggers when a user in COR is created or changed, such as their name, email, role, position or labels. - Action **Add brand** Creates a new brand under a client in COR. - Action **Add team** Creates a new team in COR with a name and, optionally, a description and workspace. Returns the team that was created. - Action **Create Client** Creates a new client in COR with its company details and primary contact, and returns the new client's id. - Action **Create Fee** Creates a fee for a client in COR, with its name, estimate and work order, and optional details such as dates, status and currency. Returns the new fee. - Action **Create Hour** Logs a time entry against a task in COR and returns the new entry's id. - Action **Create Invoice** Creates an invoice (a COR transaction) for the given date, total and currency, optionally linked to a client, and returns the new transaction. - Action **Create Project** Creates a new project for a client in COR and returns the created project. - Action **Create Task** Creates a new task in COR, optionally within a project, and returns the created task. - Action **Delete Project** Deletes a project in COR by its ID. - Action **Delete task** Deletes a task in COR by its ID. - Action **Find clients by name** Returns the clients whose name matches the specified name. - Action **Find projects by name** Returns the COR projects whose name matches the name you search for, including each project's client, project manager, status and budget details. - Action **Get client** Returns a single COR client by its id, including its business name, contact details, website and description. - Action **Get project** Returns a single COR project by its id, including its client, project manager, dates, status, budget figures and assigned labels. An error occurs if the project is not found. - Action **Get task** Returns a single COR task by its id, including its title, project, deadline, status and priority. - Action **List clients** Returns all clients in the COR account, optionally narrowed by filter criteria. - Action **List fees** Returns the fees in the COR account, including each fee's name, estimate, status and dates. - Action **List hours** Returns the time entries logged in the COR account, optionally narrowed by date range, client, project, user, label or team, and sorted as you choose. - Action **List products** Returns all products in the COR account, each with its name, client and brand. - Action **List projects** Returns the company's projects, optionally narrowed by client, team, user, brand, product, dates, status, health or archived state. - Action **List tasks** Returns the tasks in your COR account, optionally narrowed by project, project manager, status and other criteria, and sorted the way you choose. - Action **List teams** Returns the teams in the COR workspace, including each team's name and description. - Action **Update Project** Updates an existing project in COR, changing only the fields you fill in, and returns the updated project. - Action **Update Task** Updates an existing task by its id, changing its title, project, description, deadline, status, priority or archived state, and returns the updated task. - 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 - [ **COR** COR is the all-in-one management solution for creative agencies that automate timesheets, through AI, to...](https://apiant.ai/connections/cor) - [ **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 COR - [ **COR to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/cor-to-hubspot) - [ **COR to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/cor-to-salesforce) - [ **COR to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/cor-to-slack) - [ **COR to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/cor-to-google-sheets) - [ **COR to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/cor-to-gmail) - [ **COR to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/cor-to-google-calendar) ## 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 ## COR and Neon Postgres, answered ### ### What can start an automation from COR? Any of COR's 12 triggers in the catalog, including Create Brand, Create Client, Create Hour and Create Invoice. 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 COR? 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 COR? Neon Postgres has no triggers in the catalog today, so automations start in COR. 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 COR 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 COR 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.