PostHog / PostHog/posthog

Workflows: Support Microsoft Graph API For Teams Support

Open
#46,703 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature/workflows team/workflows
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
6h 51m
Merged PRs (30d)
232

Description

Feature request

Is your feature request related to a problem?

The current method requires setting up a webhook, which is great for engineers but not optimal for end users. See this ticket. They'd like to essentially set up the ability for their end users to enable notifications in Teams from within their app.

Describe the solution you'd like

Supporting the Microsoft Graph API would be a much easier process for end users of other services provided by our customers.

Describe alternatives you've considered

Additional context

Debug info
- [x] 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]

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.

Research direction

The issue describes replacing or complementing the existing webhook-based workflow with Microsoft Graph API support for Teams, but names no files, tests, or entry points. Start by locating the current workflow webhook implementation and reviewing the Microsoft Graph requirements. Done would mean a defined, working Teams integration that lets end users enable notifications from customer applications.

Written by the indexing model from the issue text.

Assessment

Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.