PipedreamHQ/pipedream

[TRIGGER] Refactor Basin source to use webhooks instead of polling

Open

#5,225 opened on Jan 18, 2023

View on GitHub
 (3 comments) (0 reactions) (1 assignee)JavaScript (7,438 stars) (5,305 forks)batch import
enhancementgood first issuehelp wantedtriagedtrigger / source

Description

They support RESTHooks, which I am not familiar with -- can we support this approach in Pipedream?

Contributor guide

Tech stack
javascriptnodejsrest api
Domain
backendapi
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
needs maintainer response
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Pipedream event sourcesRESTHooks protocolNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Examine the current Basin source in the Pipedream repository (likely under components/basin/) to understand the polling implementation. Research RESTHooks specification and determine if the Basin API supports it. Then propose a refactor to replace polling with webhook registration.