Integration
Connect Omnisend to Pylon
When New Contact fires in Omnisend, your agent runs Update contact in Pylon. 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 Pylon 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 Pylon
When New Contact in Omnisend
then Update contact in Pylon
When Updated Contacts in Omnisend
then Add internal note to issue in Pylon
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 Pylon
Triggers and actions 2 triggers · 61 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 internal note to issueAdds an internal note to a Pylon issue. Internal notes are not visible to the requester.
Action
Add tagCreates a new tag in Pylon that can be applied to accounts, articles or issues.
Action
Add taskCreates a task in Pylon with a title and optional details such as assignee, due date, account, project and status. Returns the new task.
Action
Create AccountCreates a new customer account in Pylon with its name, domains, owner, tags and other details.
Action
Create Account ActivityCreates a custom activity on a Pylon account's timeline.
Action
Create Call RecordingCreates a call recording in Pylon from your own call recorder, including its transcript, and returns the new recording. Requires the Custom Call Recorder integration to be enabled in Pylon.
Action
Delete accountPermanently deletes a Pylon account by its ID or external ID.
Action
Delete issuePermanently deletes an issue in Pylon.
Action
Find Account by NameFinds Pylon accounts by name, by exact or partial match, returning the matching accounts.
Action
Find contacts by criteriaReturns the contacts that match the specified search text and/or filter.
Action
Find issues by criteriaReturns Pylon issues matching a text search and/or a filter on fields such as state, assignee, account, tags or dates.
Action
Get accountReturns a single Pylon account by its ID or external ID, including its domains, owner, tags, channels and custom fields.
Action
Get contactReturns a single contact, including its emails, phone numbers, account and custom field values, by its ID or external ID.
Action
Get issueReturns a single Pylon issue by its ID or issue number, including its custom field values. An error occurs if the issue is not found.
Action
Get userReturns a single Pylon team member by ID, including their name, email addresses, status, and assigned roles.
Action
Get UsersReturns the users in your Pylon organization, optionally including deactivated users.
Action
List accountsReturns all accounts in your Pylon organization, including their domains, owner, tags and custom field values.
Action
List contactsReturns all contacts in the Pylon organization, including their emails, phone numbers, account and custom field values.
Action
List tagsReturns all tags in the Pylon organization, with each tag's name, color and the type of object it applies to.
Action
List teamsReturns all teams in the Pylon organization, with their members, how each team assigns issues, and any recurring assignment schedule.
Action
Reply to issueSends a customer-facing reply on a Pylon issue, continuing an existing conversation or thread. Returns the ID of the new message and its issue.
Action
Update AccountUpdates an existing Pylon account. Only the fields you fill in are changed.
Action
Update contactUpdates an existing Pylon contact by its ID or external ID. Only the fields you fill in are changed.
Action
Update issueUpdates an existing Pylon issue — its title, state, assignee, team, account, requester, tags, type, portal visibility and custom fields. Only the fields you fill in are changed.
Action
Update Issue FollowersAdds or removes users and contacts as followers of a Pylon issue, and returns the issue's resulting followers.
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 Pylon
HubSpot to PylonHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to PylonSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to PylonSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to PylonGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to PylonGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PylonGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Omnisend and Pylon, 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 Pylon when something happens in Omnisend?
Any of Pylon's 25 actions, including Create Account, Create Account Activity, Create Call Recording and Update Account. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Pylon to Omnisend?
Pylon has no triggers in the catalog today, so automations start in Omnisend. If you need the other direction, ask: your agent reads Pylon's API documentation and adds it.
Do I have to build a connector for Omnisend or Pylon?
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 Pylon 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.