Integration
Connect Emma to Neon Api Keys
When New mailing fires in Emma, your agent runs Add project in Neon Api Keys. 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 Emma and Neon Api Keys 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)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 Emma can start in Neon Api Keys
When New mailing in Emma
then Add project in Neon Api Keys
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 Emma and Neon Api Keys
Triggers and actions 2 triggers · 25 actions
- New mailing
Polling trigger: fires when a new mailing (campaign) is created in the account.
- New subscriber
Polling trigger: fires when a new subscriber (member) is added to the account.
- Delete member
Delete a member by member ID (sets status to deleted).
- Get mailing
Get a single mailing by mailing ID.
- Get mailing members
Get the members a mailing was sent to.
- Get member
Get a single member by member ID.
- Get member by email
Look up a single member by email address.
- List fields
List the member data fields defined in the account.
- List groups
List all member groups in the account.
- List mailings
List mailings (campaigns) in the account.
- List members
List all members (subscribers) in the Emma account.
- List members in group
List the members belonging to a specific group.
- List signup forms
List the signup forms in the account.
- Opt out member
Opt a member out of all mailings by email address.
- Add API key
Creates a new personal Neon API key and returns its token.
- Add branch
Creates a branch in a Neon project. By default the branch is forked from the project's default branch with no compute, and Neon generates its name.
- 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 compute and any number of read-only computes.
- Add database
Creates a Postgres database in a branch of a Neon project.
- Add project
Creates a new Neon Postgres project, including its default branch, database, role and compute, and returns the project along with its connection details.
- Add role
Creates a Postgres role in the specified Neon project branch.
- Delete API key
Revokes (permanently deletes) a Neon API key. This cannot be undone.
- Delete branch
Deletes a branch from a Neon project. Compute endpoints on the branch go idle and existing connections are dropped.
- Delete database
Deletes the specified database from a branch of a Neon project.
- Delete project
Deletes a Neon project along with all of its branches, databases, roles and compute endpoints. Deleted projects can be recovered within 7 days.
- List API keys
Lists the API keys for your Neon account. Key tokens are not returned.
- List projects
List all Neon projects owned by the account.
- Update project
Updates an existing Neon project by ID: its name, history retention period, project settings (quotas, IP allowlist, maintenance window, and more) and default compute settings.
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 Emma
Emma to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Emma to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Emma to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Emma to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Emma to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Emma to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Neon Api Keys
Questions
Emma and Neon Api Keys, answered
What can start an automation from Emma?
Any of Emma's 2 triggers in the catalog, including New mailing and New subscriber. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Neon Api Keys when something happens in Emma?
Any of Neon Api Keys's 13 actions, including Update project, Add API key, Add branch and Add compute endpoint. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Neon Api Keys to Emma?
Neon Api Keys has no triggers in the catalog today, so automations start in Emma. If you need the other direction, ask: your agent reads Neon Api Keys's API documentation and adds it.
Do I have to build a connector for Emma or Neon Api Keys?
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 Emma and Neon Api Keys 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.