PipedreamHQ/pipedream

Ortto triggers and actions

Open

#4,891 opened on Dec 6, 2022

View on GitHub
 (0 comments) (0 reactions) (2 assignees)JavaScript (7,438 stars) (5,305 forks)batch import
actionblockedenhancementgood first issuehelp wantedprioritizedtriaged

Description

Triggers:

Actions:

First reported by a customer here: https://github.com/PipedreamHQ/pipedream/issues/4889

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.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with Pipedream componentsOrtto API documentationJavaScript/Node.jsREST API basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Review the Ortto documentation for triggers (webhook setup) and actions (API endpoints). Understand Pipedream's component model by examining existing integrations in the repository, particularly those in 'components/ortto' directory if exists. The issue is a feature request to add triggers: 'New Activity' and 'New Event', and actions: 'Create Activity', 'Get People', 'Create or Update People', 'Get People Subscription Status'. Implementation should follow Pipedream's integration patterns.