PipedreamHQ/pipedream

[TRIGGER] Pipedream Data Store - New Key in Data Store, Updated key in Data Store

Open

#9,408 opened on Dec 21, 2023

View on GitHub
 (3 comments) (1 reaction) (1 assignee)JavaScript (5,305 forks)batch import
blockedenhancementgood first issuehelp wantedtriagedtrigger / source

Repository metrics

Stars
 (7,438 stars)
PR merge metrics
 (Avg merge 9d 7h) (131 merged PRs in 30d)

Description

Describe the event source. What app is this for, and what event does the trigger correspond to? App: Pipedream Data Store

Triggers: I think this might need some development effort from the Pipedream internal team to develop subscription/webhook for datastore. Though, inittially it can be a polling source.

  • New Key in Data Store: emit event when there is a new key in a Data store. The event data should have key and value of the record in Data store
  • Updated key in Data Store: emit event when there the speicified key is updated in a Data store. The event data should have key, new value and old value of the record in Data store
  • Deleted Key in Data Store: emit event when a key deleted from a Data store. The event data should have key and value of the record in Data store

Please provide a link to the relevant API docs for the specific service / operation this trigger is tied to. https://pipedream.com/docs/data-stores/

Context Requested by a Business customer here: https://pipedream-users.slack.com/archives/CN1BUB92B/p1703118948881209

Contributor guide

Research direction
Study existing Pipedream event source components for patterns, then implement a polling mechanism to detect new/updated/deleted keys in a Data Store.
Tech stack
javascript
Domain
backend
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65