Integration
Connect Consent Kit to Neon Postgres
When Consent Updated fires in Consent Kit, 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 Consent Kit 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 Consent Kit can start in Neon Postgres
When Consent Updated in Consent Kit
then Add project in Neon Postgres
When New Consent in Consent Kit
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 Consent Kit and Neon Postgres
Triggers and actions 6 triggers · 47 actions
Trigger
Consent AgreedTriggers when a participant agrees to a consent in Consent Kit.
Trigger
Consent DeclinedTriggers when a participant refuses a consent in Consent Kit.
Trigger
Consent UpdatedTriggers when a Consent Kit consent is created or updated.
Trigger
Data LinkedTriggers when new data is linked to a Consent Kit participant.
Trigger
New ConsentTriggers when a participant agrees to or refuses a consent in Consent Kit.
Trigger
Participant CreatedTriggers when a participant is added to a Consent Kit study, with their email and first name.
Action
Create Data LinkLinks data stored at a URL (a recording, notes, a file) to a Consent Kit participant.
Action
Create ParticipantAdds a participant to a Consent Kit study; Consent Kit uses the email to send them the consent form.
Action
Create StudyCreates a new study inside a Consent Kit project.
Action
Delete Data LinkDeletes (unlinks) a data link from its Consent Kit participant.
Action
Delete StudyDeletes a Consent Kit study.
Action
Get ConsentReturns one Consent Kit consent by ID: whether it was agreed or refused, the permissions given, and the participant.
Action
Get PanelReturns one Consent Kit panel by its ID, including how many panellists it has.
Action
Get ParticipantReturns one Consent Kit participant by ID, optionally with their email and first name.
Action
Get ProjectReturns one Consent Kit project by its ID.
Action
Get StudyReturns one Consent Kit study by its ID.
Action
List ConsentsReturns a page of consents in your Consent Kit organisation, optionally only agreed or only refused ones.
Action
List Data LinksReturns a page of the data links in your Consent Kit organisation.
Action
List FieldsReturns the custom field definitions configured for your Consent Kit organisation, used to read panellist properties.
Action
List Panel PanellistsReturns the opted-in panellists of a Consent Kit panel, optionally with their email, name and custom field values.
Action
List PanelsReturns a page of your organisation's Consent Kit panels.
Action
List ParticipantsReturns a page of your organisation's Consent Kit participants, optionally with their email and first name.
Action
List ProjectsReturns a page of your organisation's Consent Kit projects, newest first.
Action
List StudiesReturns a page of your organisation's Consent Kit studies.
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 Consent Kit
Consent Kit to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Consent Kit to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Consent Kit to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Consent Kit to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Consent Kit to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Consent Kit to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
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
Consent Kit and Neon Postgres, answered
What can start an automation from Consent Kit?
Any of Consent Kit's 6 triggers in the catalog, including Consent Updated, New Consent, Participant Created and Consent Agreed. 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 Consent Kit?
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 Consent Kit?
Neon Postgres has no triggers in the catalog today, so automations start in Consent Kit. 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 Consent Kit 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 Consent Kit 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.