Feature request: Support for push notifications / In-app messages in workflows

Open
#40,545 8 comments 23 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Domain
backend, mobile

Research direction

No implementation files or tests are named. Start by reviewing the related issue #44444 and the workflow product area, then clarify the first supported notification and in-app message scope, triggering paths, SDK responsibilities, preview behavior, and acceptance criteria.

Written by the indexing model from the issue text.

Description

enhancement feature/libraries feature/messaging feature/mobile feature/workflows team/cdp
Feature request

Is your feature request related to a problem?

For mobile products, the most effective engagement happens through push notifications and in-app messages, not email.

Describe the solution you'd like

Extend Workflows product to support mobile push notifications and in**-app messages** steps. Ideally:

  • Uses the same Workflows UI to set up
  • Can be triggered on a schedule (to support "campaigns")
  • Can be triggered through our server-side sdks
  • In-app messages are lightweight modals, banners, or toasts rendered and styled by the SDK
  • Provides a preview for the notification / message
  • We can start with basic support, then add more advanced options like media attachments, user actions on notifications etc

This will allow to run complex product activation and retention loops directly through PostHog

Describe alternatives you've considered

People likely use:

  • Other 3rd party
  • Use feature flags to trigger custom in-app messages

Questions for the Community:

  • Would this be useful to you and your use case?
  • Would this replace an existing tool you are already using? If so, which one?
  • What additional features would be critical for your needs?

Please leave a 👍 or ❤️ reaction on this post to vote for it. You votes and feedback help us prioritize what to work on next!

Debug info
- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]

See also https://github.com/PostHog/posthog/issues/44444

Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
7h 27m
Merged PRs (30d)
222

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PostHog/posthog

All issues in PostHog/posthog

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.