PipedreamHQ/pipedream

[ACTIONS, TRIGGERS] Tricount new components

Open

#3,964 opened on Aug 9, 2022

View on GitHub
 (4 comments) (0 reactions) (0 assignees)JavaScript (7,438 stars) (5,305 forks)batch import
actionblockedenhancementgood first issuehelp wantedtrigger / source

Description

Tricount

Actions:

Add an expense Modify an expense Delete an expense

Trigger:

New expense

https://www.tricount.com/en/api

Contributor guide

Tech stack
javascriptnodejsrest api
Domain
apibackend
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.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic JavaScriptPipedream component developmentREST API concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
First, explore the Tricount API documentation at the provided link to understand endpoints and authentication. Then, examine existing Pipedream components in the repository (e.g., under 'components/tricount' or similar apps) to follow the pattern for implementing actions (add expense, modify expense, delete expense) and a new expense trigger. Check the issue comments for any additional context from maintainers or contributors. The implementation should create separate .mjs files for each action and the trigger, following Pipedream's component structure.