---
title: "Connect OneSignal and Sorry - APIANT.ai"
description: "When \"New Notification Created\" fires in OneSignal, your agent runs \"Update status page\" in Sorry, or \"New notice\" in Sorry to \"Send email\" in OneSignal."
canonical: "https://apiant.ai/connect/onesignal-to-sorry"
---

# Connect OneSignal and Sorry

When **New Notification Created** fires in [OneSignal](https://apiant.ai/connections/onesignal), your agent runs **Update status page** in [Sorry](https://apiant.ai/connections/sorry), or **New notice** in Sorry to **Send email** in OneSignal. Describe the whole flow and it is built, tested on every scenario and kept running.

OneSignal **1** trigger OneSignal **17** actions Sorry **1** trigger Sorry **16** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want OneSignal and Sorry to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One 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.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

Example flows

## What OneSignal and Sorry can do together

### From OneSignal to Sorry

- When **New Notification Created** in OneSignal then **Update status page** in Sorry
- When **New Notification Created** in OneSignal then **Add component** in Sorry

### From Sorry to OneSignal

- When **New notice** in Sorry then **Send email** in OneSignal
- When **New notice** in Sorry 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 Sorry

## Triggers and actions 2 triggers · 33 actions

- Trigger

**New Notification Created**

Triggers when a new message (push, email or SMS) is created in your OneSignal app.

- Action

**Add custom event**

Records a custom event, such as a purchase or milestone, against a OneSignal user identified by External ID or OneSignal ID.

- Action

**Add segment**

Creates a segment in your OneSignal app from a set of audience filters.

- Action

**Add subscription**

Adds 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 user**

Creates 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 notification**

Cancels a scheduled or currently sending OneSignal message so it stops going out.

- Action

**Delete segment**

Deletes a segment from your OneSignal app. The users and subscriptions in the segment are not deleted.

- Action

**Delete user**

Deletes a OneSignal user along with all of their properties, subscriptions and identity aliases.

- Action

**Get notification**

Returns the details of a single OneSignal message, including its content, delivery statistics and outcomes.

- Action

**Get user**

Returns a OneSignal user, including their aliases, properties (tags, country, activity dates) and subscriptions.

- Action

**List notifications**

Returns the push, email and SMS messages sent from your OneSignal app, newest first, with their content and delivery stats.

- Action

**List segments**

Returns all segments in your OneSignal app, with each segment's name, description, status and dates.

- Action

**List templates**

Returns the message templates in your OneSignal app, optionally filtered to push, email or SMS templates.

- Action

**Send Advanced Push Notification**

Sends 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 email**

Sends an email message through OneSignal to email addresses, users, subscriptions or segments, using your own content or a saved template.

- Action

**Send Push Notification**

Sends 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 SMS**

Sends an SMS or MMS text message through OneSignal to phone numbers, users, subscriptions or segments, and returns the new message's ID.

- Action

**Update user**

Updates a OneSignal user's properties, such as tags, language, timezone, location and country, and records session activity and purchases.

- Trigger

**New notice**

Triggers when a new notice (incident, maintenance or general announcement) is created on the selected Sorry status page.

- Action

**Add component**

Creates a new component on a Sorry status page, optionally nested under a parent component.

- Action

**Add notice**

Creates a new incident, maintenance or general notice on a Sorry status page, optionally linking affected components and publishing it to subscribers.

- Action

**Add notice update**

Posts a new update on an existing notice on a Sorry status page, optionally publishing it to your configured integrations.

- Action

**Add subscriber**

Adds an email or SMS subscriber to a status page, optionally limited to specific components, so they receive status notices.

- Action

**Delete notice**

Deletes a notice (incident, maintenance or general) from a Sorry status page.

- Action

**Delete subscriber**

Permanently removes a subscriber from a status page.

- Action

**Get notice**

Returns a single notice from a status page, including its type, state, subject, synopsis and link.

- Action

**Get status page**

Returns a single Sorry status page with its name, state, timezone, support details and notification settings, optionally including related brand, components, notices and more.

- Action

**List components**

Returns all components (the services or infrastructure elements) shown on a Sorry status page, with their current state.

- Action

**List notices**

Returns the notices (incidents, maintenance and general notices) posted on a Sorry status page, optionally filtered by type, state, subject or creation date.

- Action

**List notice updates**

Returns all updates posted on a notice on one of your Sorry status pages, optionally filtered by creation date or content.

- Action

**List status pages**

Returns all status pages in your Sorry account, optionally filtered by name or creation date.

- Action

**List subscribers**

Returns the subscribers on a status page, optionally only those who receive notices for a specific component.

- Action

**Update component**

Updates a component on a Sorry status page, such as its name, description, position or parent component.

- Action

**Update notice**

Updates an existing notice on a Sorry status page — change its subject or state, add a comment, set affected components or reschedule planned maintenance.

- Action

**Update status page**

Updates a status page's settings, such as its name, timezone, support contact details, search visibility and language.

## Each app on its own

- [ **OneSignal** OneSignal is a simple and smart service that send push notifications across all platforms.](https://apiant.ai/connections/onesignal)
- [ **Sorry** Status page and incident communication platform for notifying customers about downtime.](https://apiant.ai/connections/sorry)

Reviews

## What our customers say

## More from OneSignal

- [ **OneSignal to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/onesignal-to-salesforce)
- [ **OneSignal to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/onesignal-to-slack)
- [ **OneSignal to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/onesignal-to-stripe)
- [ **OneSignal to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/onesignal-to-shopify)
- [ **OneSignal to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/onesignal-to-quickbooks-online)
- [ **OneSignal to Pipedrive** Pipedrive is a sales CRM and pipeline management tool.](https://apiant.ai/connect/onesignal-to-pipedrive)

## More into Sorry

- [ **HubSpot to Sorry** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-sorry)
- [ **Salesforce to Sorry** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-sorry)
- [ **Slack to Sorry** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-sorry)
- [ **Google Sheets to Sorry** Google Sheets](https://apiant.ai/connect/google-sheets-to-sorry)
- [ **Gmail to Sorry** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-sorry)
- [ **Google Calendar to Sorry** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-sorry)

Questions

## OneSignal and Sorry, 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 Sorry when something happens in OneSignal?

Any of Sorry's 16 actions, including Update component, Update notice, Update status page and Add component. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Sorry to OneSignal?

Yes. When something happens in Sorry, your agent can act in OneSignal too. This page covers both directions: Sorry's triggers and OneSignal's actions are listed here as well.

###

### Do I have to build a connector for OneSignal or Sorry?

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 Sorry 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.
