PipedreamHQ / PipedreamHQ/pipedream

Lazyweb

Open
#21,810 0 comments 0 reactions 0 assignees View on GitHub
actions app trigger / source user request
Dominant language
JavaScript
Stars
11.7k
Forks
5.8k
Avg merge
3d 10h
Merged PRs (30d)
102

Description

### App
Lazyweb
https://www.lazyweb.com/claude.md

### Sources
Polling triggers: (1) New Growth Report completed, (2) Proposal decision recorded (human approved/rejected a UI-change proposal), (3) New Growth Backlog spec added. All pollable via existing authenticated endpoints.

### Actions
Actions: (1) Search App Screens (281k+ real product screens; filters for category/company/pattern), (2) Search Mobile A/B Tests (real experiments with outcomes), (3) Add Growth Backlog Spec (idempotency-keyed write). First-party request by the Lazyweb founder under your App Partner program. Auth: OAuth 2.1, Dynamic Client Registration + PKCE S256, RFC 8414 metadata at https://www.lazyweb.com/.well-known/oauth-authorization-server. Hosted MCP (Streamable HTTP): https://www.lazyweb.com/mcp. MFA-free test account ready on request. Ref: GitHub issue PipedreamHQ/pipedream#21809. Contact: ali@lazyweb.com

Contributor guide

Open the contributing guide

Research direction

No repository files, tests, or entry points are named. Start by reviewing the related PipedreamHQ/pipedream#21809 issue and the Lazyweb OAuth authorization-server and MCP endpoints; done would cover the three polling triggers and three actions described here.

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
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.