Integration
Connect OneSignal and Swiftype
When New Notification Created fires in OneSignal, your agent runs Create Document in Swiftype, or New Document in Swiftype to Send email in OneSignal. 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 OneSignal and Swiftype 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 OneSignal and Swiftype can do together
From OneSignal to Swiftype
When New Notification Created in OneSignal
then Create Document in Swiftype
When New Notification Created in OneSignal
then Update document in Swiftype
From Swiftype to OneSignal
When New Document in Swiftype
then Send email in OneSignal
When New Document in Swiftype
then Add custom event in OneSignal
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 OneSignal and Swiftype
Triggers and actions 2 triggers · 31 actions
Trigger
New Notification CreatedTriggers when a new message (push, email or SMS) is created in your OneSignal app.
Action
Add custom eventRecords a custom event, such as a purchase or milestone, against a OneSignal user identified by External ID or OneSignal ID.
Action
Add segmentCreates a segment in your OneSignal app from a set of audience filters.
Action
Add subscriptionAdds a new email, SMS or push subscription to an existing OneSignal user, found by one of the user's aliases such as their External ID.
Action
Add userCreates a OneSignal user identified by an External ID, with optional tags, profile properties and subscriptions. If the External ID already exists, the user's subscriptions are updated instead.
Action
Delete notificationCancels a scheduled or currently sending OneSignal message so it stops going out.
Action
Delete segmentDeletes a segment from your OneSignal app. The users and subscriptions in the segment are not deleted.
Action
Delete userDeletes a OneSignal user along with all of their properties, subscriptions and identity aliases.
Action
Get notificationReturns the details of a single OneSignal message, including its content, delivery statistics and outcomes.
Action
Get userReturns a OneSignal user, including their aliases, properties (tags, country, activity dates) and subscriptions.
Action
List notificationsReturns the push, email and SMS messages sent from your OneSignal app, newest first, with their content and delivery stats.
Action
List segmentsReturns all segments in your OneSignal app, with each segment's name, description, status and dates.
Action
List templatesReturns the message templates in your OneSignal app, optionally filtered to push, email or SMS templates.
Action
Send Advanced Push NotificationSends a push notification with OneSignal's full set of options: audience targeting by users, subscriptions, segments or filters, plus images, icons, buttons, sounds, badges, platform selection, scheduling and throttling.
Action
Send emailSends an email message through OneSignal to email addresses, users, subscriptions or segments, using your own content or a saved template.
Action
Send Push NotificationSends a push notification to your OneSignal app's subscribers, chosen by segment, filters, user alias or subscription ID. Returns the ID of the notification that was created.
Action
Send SMSSends an SMS or MMS text message through OneSignal to phone numbers, users, subscriptions or segments, and returns the new message's ID.
Action
Update userUpdates a OneSignal user's properties, such as tags, language, timezone, location and country, and records session activity and purchases.
Trigger
New DocumentTriggers when a new Document is created.
Action
Add domainAdd a crawler domain to an Engine.
Action
Add engineCreate a new Engine (index).
Action
Create DocumentCreates a new Document.
Action
Delete documentDelete a document by document_id from a document type.
Action
Delete domainRemove a crawler domain from an Engine.
Action
Delete engineDelete an Engine by id.
Action
Get documentRetrieve a single document by external_id from a document type.
Action
Get engineRetrieve a single Engine by id or name.
Action
List documentsList documents within a document type/engine.
Action
List domainsList crawler domains configured on an Engine.
Action
List enginesList all Engines for the account.
Action
Recrawl domainTrigger a recrawl of a domain's crawled content.
Action
Search documentsPerform full-text search over documents within an Engine.
Action
Update documentUpdate fields on an existing document.
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 OneSignal
OneSignal to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
OneSignal to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
OneSignal to StripeStripe is a payment processing platform for online businesses.
OneSignal to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
OneSignal to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
OneSignal to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Swiftype
HubSpot to SwiftypeHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SwiftypeSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to SwiftypeSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to SwiftypeGoogle Sheets
Gmail to SwiftypeGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SwiftypeGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
OneSignal and Swiftype, answered
What can start an automation from OneSignal?
Any of OneSignal's 1 trigger in the catalog, including New Notification Created. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Swiftype when something happens in OneSignal?
Any of Swiftype's 14 actions, including Create Document, Update document, Add domain and Add engine. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Swiftype to OneSignal?
Yes. When something happens in Swiftype, your agent can act in OneSignal too. This page covers both directions: Swiftype's triggers and OneSignal's actions are listed here as well.
Do I have to build a connector for OneSignal or Swiftype?
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 OneSignal and Swiftype 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.