OneSignal stores every push, email, SMS, and in-app notification as a campaign with a delivery status, an audience segment, a channel, and stats for delivered, clicked, and failed counts. The OneSignal dashboard surfaces these as a long list filtered by date, which works for ad-hoc lookups but makes it hard to see how many drafts are sitting unsent, how many are scheduled for the week, and how many failed silently overnight.

SleekView Kanban authenticates with the OneSignal REST API using your app ID and REST API key and pulls every notification along with its delivery status, audience segment, channel, scheduled time, and last status update. It groups the records into columns by the delivery status field, so Draft, Scheduled, Sent, and Failed each get a swimlane, and any custom tag on a notification can be used as an additional filter on the board.

Dragging a card between columns writes the new state through the OneSignal API. Promoting a draft to scheduled lets you set a send time inline, scheduling a sent notification cancels future delivery, and moving a failed notification back to draft prepares it for a retry after fixing the audience or template. SleekView only changes status and metadata, so notification content stays intact and the audit trail in the OneSignal dashboard records every action correctly.

Notification programs are noisy. Marketing, lifecycle, product, and support all push campaigns through the same OneSignal account, and the default dashboard shows them as a chronological list. That list answers the question of what was sent recently but not the question of what is sitting in draft, what is scheduled for the week, and what failed silently and needs a retry.

A kanban view turns the campaign pipeline into a visible layout. Drafts collect on the left as the work that is being prepared, Scheduled is the runway with real send times on every card, Sent is the published archive, and Failed is the most important column for many teams because it represents notifications that did not reach the audience and need attention. The shape of the board tells a story, like a Failed column that grew overnight because of a template breakage, or a Draft column that has not moved in two weeks because the team is overcommitted.

Drag and drop matters because scheduling and retrying are common actions that should not require opening the full campaign editor for each one.