Integration
Connect Knorish to Neon Postgres
When New Signup fires in Knorish, your agent runs Add project in Neon Postgres. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Knorish and Neon Postgres to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
Setup guide (opens in a new tab)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)Example flows
What Knorish can start in Neon Postgres
When New Signup in Knorish
then Add project in Neon Postgres
When Bundle Purchased in Knorish
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 Knorish and Neon Postgres
Triggers and actions 3 triggers · 56 actions
Trigger
Bundle PurchasedTriggers when a user is newly enrolled in the chosen bundle, such as after purchasing it.
Trigger
Course PurchasedTriggers when a user purchases or is enrolled in the selected Knorish course.
Trigger
New SignupTriggers when a new user signs up on your Knorish site.
Action
Add User to BundleGives a user access to a bundle.
Action
Add User to CourseEnrolls a user in a course.
Action
Create UserCreates a learner account on your Knorish site and returns its id.
Action
Delete BundleRemoves a bundle from your Knorish site.
Action
Delete CourseRemoves a course from your Knorish site.
Action
Delete UserRemoves a user from your Knorish site.
Action
Get BundleReturns a bundle's details by bundle id.
Action
Get CourseReturns a course's details by course id.
Action
Get UserReturns a user's profile by user id.
Action
Get User Course ProgressReturns how far a user has progressed in a course and their average assessment score.
Action
List Bundle CoursesReturns the courses included in a bundle.
Action
List BundlesReturns a page of bundles on your Knorish site.
Action
List Bundle UsersReturns the users who have a bundle, optionally filtered by date range.
Action
List Course AssessmentsReturns a course's assessments with their duration, attempts and pass marks.
Action
List Course Live SessionsReturns a course's live sessions with start/end times and host/join links.
Action
List CoursesReturns a page of courses on your Knorish site.
Action
List Course SectionsReturns a course's sections, including their drip-release settings.
Action
List Course UsersReturns the users enrolled in a course, optionally filtered by enrollment date range.
Action
List Section ChaptersReturns the chapters (lectures) in a course section.
Action
List User BundlesReturns the bundles a user has purchased or been given.
Action
List User CoursesReturns the courses a user is enrolled in, with the date each was assigned.
Action
List User Live SessionsReturns the live sessions available to a user, with start/end times and join links.
Action
List UsersReturns a page of users on your Knorish site, optionally filtered by search text or signup date range.
Action
Remove User From BundleRemoves a user's access to a bundle.
Action
Remove User From CourseRemoves a user's access to a course.
Action
Reply to ContactSends a reply to a contact form submission on your Knorish site.
Action
Update UserUpdates a user's name, email or password.
Action
Add branchCreate a new branch in a Neon project.
Action
Add compute endpointCreates 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 databaseCreates a new Postgres database in a Neon project branch, owned by an existing role.
Action
Add projectCreates a new Neon Postgres project with its default branch, database, role and compute, and returns the project along with its connection details.
Action
Add roleCreates a Postgres role in the specified Neon project branch. Connections to the branch's active compute are dropped while the change applies.
Action
Delete branchDelete a branch by project_id and branch_id.
Action
Delete compute endpointDeletes 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 databaseDeletes the specified database from a branch of a Neon project.
Action
Delete projectDeletes a Neon project and all its branches, compute endpoints, databases and roles. The project can be recovered within 7 days.
Action
Delete roleDeletes the specified Postgres role from a Neon branch.
Action
Get branchRetrieves details of a branch in a Neon project.
Action
Get compute endpointRetrieve details about a compute endpoint.
Action
Get connection URIRetrieve a Postgres connection URI for a database/role/branch/endpoint combination.
Action
Get databaseRetrieves details of a database on a Neon project branch.
Action
Get projectRetrieves the details of a Neon project, including its settings, compute configuration, history retention, owner and current usage metrics.
Action
Get roleRetrieves details about a Postgres role (user) on a Neon branch.
Action
Get role passwordRetrieves the password for a Postgres role on a Neon branch.
Action
List branchesRetrieve a list of branches for a Neon project.
Action
List compute endpointsLists the compute endpoints (Neon compute instances) in a project.
Action
List databasesLists the databases on a branch of a Neon project.
Action
List operationsLists 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 projectsLists the Neon projects accessible to the connected account, optionally filtered by name/ID or organization.
Action
List rolesLists the Postgres roles on a Neon project branch.
Action
Start compute endpointStart (resume) a suspended compute endpoint.
Action
Suspend compute endpointSuspends the specified Neon compute endpoint (scales it to zero).
Action
Update branchUpdate a branch's properties (e.g. name, protected) by project_id and branch_id.
Action
Update compute endpointUpdates an existing compute endpoint in a Neon project by ID.
Action
Update databaseUpdates the name or owner of a database on a Neon project branch.
Action
Update projectUpdate settings for a Neon project by project_id.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Knorish
Knorish to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Knorish to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Knorish to MailchimpMailchimp marketing automation and email platform.
Knorish to StripeStripe is a payment processing platform for online businesses.
Knorish to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Knorish to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Neon Postgres
Vimeo OTT to Neon PostgresVimeo OTT (formerly VHX) is an over-the-top video monetization platform for launching subscription and...
HubSpot to Neon PostgresHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Neon PostgresSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Neon PostgresSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Neon PostgresGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Neon PostgresGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Knorish and Neon Postgres, answered
What can start an automation from Knorish?
Any of Knorish's 3 triggers in the catalog, including New Signup, Bundle Purchased and Course Purchased. 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 Knorish?
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 Knorish?
Neon Postgres has no triggers in the catalog today, so automations start in Knorish. 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 Knorish 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 Knorish 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.