SSWConsulting / SSWConsulting/SSW.Tiger

✨ Email Ingestion - Send meeting link to Tiger via email to generate dashboard

Open
#136 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

YakShaver
Dominant language
JavaScript
Stars
1
Forks
1
Avg merge
2d 12h
Merged PRs (30d)
2

Description

Cc: @adamcogan, @suiyangqiu, @calumjs, @joshbermanssw, @yaqi-lyu
Hi Team!

🟥 Watch the video (1 min 1 sec)

Pain

Tiger currently requires meeting processing to be triggered via existing mechanisms (e.g. webhook/Teams automation), which makes it hard for users to kick off dashboard generation for a meeting recording by simply emailing a meeting link. Users want a low-friction way to send a meeting link/recording link to Tiger and receive the generated dashboard back, without needing portal access.

Acceptance Criteria
  1. A dedicated “SSW.Tiger” inbound email address exists for users to send meeting links.
  2. Only authorized senders are allowed to trigger processing from email.
  3. When an authorized email is received with a meeting link, Tiger creates a meeting-processing request.
  4. The request records processing progress with a clear status (e.g., queued, processing, completed, failed).
  5. When processing completes successfully, Tiger sends the generated dashboard link back to the original requester.
  6. If processing fails, Tiger sends a failure notification to the original requester with a human-readable reason.
  7. The system validates and rejects emails without a usable meeting link.

Thanks!

Contributor guide

No contributing guide indexed for this repository

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

Start by locating the existing webhook or Teams automation entry points mentioned in the issue and trace how meeting-processing requests are created and reported. Define the email intake, sender authorization, meeting-link validation, progress statuses, and success or failure replies against the seven acceptance criteria. Done means authorized valid emails produce a tracked request and an appropriate response, while invalid or failed requests receive clear notifications.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.