obsei-teams
Posts matching feedback to a Microsoft Teams channel as an Adaptive Card, through a Power Automate Workflows webhook (Microsoft retired the Office 365 connector incoming webhooks).
Install it from Git (a PyPI package is coming):
pip install "obsei-teams @ git+https://github.com/obsei/obsei#subdirectory=plugins/obsei-teams"
In Teams, open the channel's Workflows and choose the template Post to a channel when a
webhook request is received. Copy the URL it creates into an environment variable; it carries
a signature, so treat it as a secret and never put it in obsei.yaml.
plugins: [teams]
egress:
mode: private
allowed_hosts: [logic.azure.com, environment.api.powerplatform.com]
pipelines:
- name: alerts
sources:
- key: ios
type: appstore
config: {app_id: "284882215"}
enrichers:
- type: classify
config: {llm: default}
sinks:
- type: teams
config:
title: Negative app reviews
when: {classify.sentiment: [negative]}
max_rating: 2
| Field | Default | Meaning |
|---|---|---|
webhook_url_env |
TEAMS_WEBHOOK_URL |
Environment variable holding the Workflows URL. |
title |
New customer feedback |
Card heading. |
when |
all records | Routing conditions to match (values, is, min_confidence, gte/lte, review), as in the slack sink. |
max_rating |
none | Only records rated at or below this. |
max_records |
10 | Records per card (up to 25); the card counts the rest. |
max_text |
600 | Characters of feedback shown per record. |
Each batch becomes at most one message. A record shows its source, rating, sentiment and intent
(when the classify enricher ran), its redacted text as plain text (customer text cannot add
links or formatting) and an Open button for http(s) links. Authors are never sent.
The webhook hosts are public (*.logic.azure.com, or *.environment.api.powerplatform.com for
newer workflows), so obsei's default air-gapped egress policy blocks them. Allow them with
OBSEI_EGRESS_MODE=private and OBSEI_EGRESS_ALLOW=logic.azure.com,environment.api.powerplatform.com
or the egress block above. Every request, redirects included, is checked against the policy.
Metadata
Release files for obsei-teams 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| obsei_teams-0.1.0.tar.gz | 7.3 kB | With provenance | Details for obsei_teams-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| obsei_teams-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for obsei_teams-0.1.0-py3-none-any.whl |
Total release size: 12.1 kB
Release files / obsei_teams-0.1.0.tar.gz
| Download URL | obsei_teams-0.1.0.tar.gz |
|---|---|
| Size | 7.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
db54c25725bf51c8372668c5f23d35927cf8391e03cf2f2a30cbcca15299e4e7
|
|
BLAKE2b-256 checksum How to use checksums |
7e264ce1b9392af9bd6af8bc9ac328342a0f2faf53479942e63ec32e29cc745a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 15, 2026.
Transparency logRelease files / obsei_teams-0.1.0-py3-none-any.whl
| Download URL | obsei_teams-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aa1deafb7ba1333da7e3a4fddbd40182ba56a8a8cba95d4b038e1f1ad198f80b
|
|
BLAKE2b-256 checksum How to use checksums |
cd6e5bdf877ef566e758ce84ebc6238a4507a35f00aa4d2ffa16dbf0702c9cb0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 15, 2026.
Transparency logSecurity for obsei-teams 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for obsei_teams-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 15, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.