Integration
Connect Omnisend to Neon Postgres
When New Contact fires in Omnisend, 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 Omnisend 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)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 Omnisend can start in Neon Postgres
When New Contact in Omnisend
then Add project in Neon Postgres
When Updated Contacts in Omnisend
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 Omnisend and Neon Postgres
Triggers and actions 2 triggers · 65 actions
Trigger
New ContactTriggers when a new contact is added to your Omnisend account, optionally limited to a subscription status, segment or tag.
Trigger
Updated ContactsTriggers when a contact is created or updated in Omnisend, newest changes first.
Action
Add email templateCreates a new email template in Omnisend with a name, general style settings and content sections.
Action
Add productCreates a product in your Omnisend catalog, with optional variants, images, categories and tags.
Action
Add product categoryCreates a new product category in your Omnisend store.
Action
Add segmentCreates a new contact segment in Omnisend from a name and a set of condition rules.
Action
Add tags to contactsAdds one or more tags to contacts chosen by contact ID, email, phone number or segment. Tagging happens in the background, so tags may take a moment to appear.
Action
Cancel CampaignCancels a scheduled or paused campaign (or a started email campaign) in Omnisend and marks it as canceled.
Action
Copy CampaignCreates a new draft copy of an existing campaign, including its content, audience and settings. The copy is named "Copy of: " followed by the original name.
Action
Create CampaignCreates a new draft campaign (email or SMS; regular, A/B test or booster) in Omnisend and returns the created campaign.
Action
Create SubscriberCreates a subscriber (contact) in Omnisend, or updates the existing contact with the same email address.
Action
Delete CampaignDeletes a campaign from your Omnisend account.
Action
Delete Email TemplateDeletes an email template from your Omnisend account by its ID.
Action
Delete ImageDeletes an image from the Omnisend image library by its ID.
Action
Delete productDeletes a product from the Omnisend product catalog by its ID.
Action
Delete SegmentPermanently deletes a segment in Omnisend.
Action
Find CampaignReturns a single Omnisend campaign by its ID, including its name, status, channel, audience, content and sending settings.
Action
Find CampaignsReturns campaigns whose name contains the given text, optionally filtered by status, channel, type and created/updated dates.
Action
Find Email TemplateReturns a single email template, including its name, layout sections and general settings, looked up by its ID.
Action
Find Email TemplatesReturns email templates whose names contain the given text.
Action
Find ImageReturns a single image from your Omnisend image library by its ID, including its URL, size and dimensions.
Action
Find ImagesReturns images in your Omnisend library whose names contain the search text.
Action
Find SegmentReturns an Omnisend segment by its ID, including its name, status and condition rules.
Action
Find SegmentsFinds segments whose name contains the given text.
Action
Get contactReturns a single Omnisend contact by its ID, including profile details, identifiers, tags, segments and custom properties.
Action
Get productReturns a single product from your Omnisend catalog by its ID, including its variants, images, categories and stock status.
Action
Get Segment StatisticsReturns statistics for a segment, including how many contacts it currently contains.
Action
Import Email TemplateCreates a new Omnisend email template by importing raw HTML. Returns the created template.
Action
List contactsReturns Omnisend contacts, optionally filtered by email, phone, subscription status, segment, tag or last-update time.
Action
Remove tags from contactsRemoves one or more tags from contacts chosen by contact ID, email, phone number or segment. Omnisend processes the removal in the background.
Action
Render Email TemplateRenders an email template and returns its full HTML body for preview.
Action
Send Customer EventSends a customer event (custom or recommended) to Omnisend for a contact, creating or updating the contact and triggering any automations based on that event.
Action
Update CampaignUpdates a draft campaign's name, language, content, audience, sending settings, booster or A/B test settings. Only campaigns still in draft can be updated.
Action
Update contactUpdates an existing Omnisend contact by its ID, changing only the fields you fill in, and returns the updated contact.
Action
Update email templateFully replaces an existing Omnisend email template's name, sections and general settings, and returns the updated template.
Action
Update productReplaces an existing product in your Omnisend catalog with the details you provide. Fields left blank are not kept from the previous version.
Action
Update segmentUpdates an existing segment's name and rules. The segment can't be updated while it is being built.
Action
Upload ImageUploads an image to your Omnisend image library from a publicly accessible URL and returns the stored image details.
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 Omnisend
Omnisend to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Omnisend to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Omnisend to StripeStripe is a payment processing platform for online businesses.
Omnisend to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Omnisend to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Omnisend to PipedrivePipedrive is a sales CRM and pipeline management tool.
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
Gmail to Neon PostgresGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Omnisend and Neon Postgres, answered
What can start an automation from Omnisend?
Any of Omnisend's 2 triggers in the catalog, including New Contact and Updated Contacts. 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 Omnisend?
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 Omnisend?
Neon Postgres has no triggers in the catalog today, so automations start in Omnisend. 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 Omnisend 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 Omnisend 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.