Connect APIs, remarkably fast. Free for developers.
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 76%
Response Time: 2d
First Timer Success: 66%
PipedreamHQ/pipedream has a recorded first-timer success rate of 65.8%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in PipedreamHQ/pipedream respond to incoming external pull requests in approximately 49.7 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 64.7 places PipedreamHQ/pipedream in the A tier.
The external contributor pull request merge rate for PipedreamHQ/pipedream is 76.1%, based on public PR activity from non-core contributors.
PipedreamHQ/pipedream currently has 27 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Connect APIs, remarkably fast. Free for developers.
Highly welcoming maintainers in PipedreamHQ/pipedream. Prompt code reviews with positive guidance for new contributors.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/PipedreamHQ/pipedream?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~32 hours (95% approval). Large PRs (>500 lines) take ~239 hours (34% approval). Keep your diff compact for rapid review.
For Neople Is there a specific app this action is for? Gorgias (gorgias_oauth), actions Create Ticket Message (gorgias_oauth-create-ticket-message) and Send Public Reply (gorgias_oauth-send-public-reply). Request: add two optional props that are passed through to the message body: Integration ID → integration_id (integer): the Gorgias integration the reply is sent through (chat widget, Instagram account, Facebook page, WhatsApp number). Nice to have: async options from GET /api/integrations. Body Text → body_text: plain-text version of the message (or derive it from the HTML message). Please provide a link to the relevant API docs for the specific service / operation. https://developers.gorgias.com/reference/create-ticket-message (integration_id and body_text are request body fields) Is lack of support preventing you from moving forward, or do you have a workaround? It blocks us. Our AI agents reply to Gorgias tickets through this action. Email replies work, but replies on chat,
Describe the event source. What app is this for, and what event does the trigger correspond to? Please provide a link to the relevant API docs for the specific service / operation this trigger is tied to.
Please add tawk.to actions to the Pipedream MCP server. Requested actions include: List tawk.to properties and sites Retrieve conversations and chat history List and manage tickets Send messages or replies Retrieve agents and visitor information Relevant service: https://www.tawk.to/ Official API documentation: https://developer.tawk.to/ The requested MCP endpoint is: https://mcp.pipedream.net/v2 The Pipedream tawk.to page currently states that no actions are available for this app yet.
Is there a specific app this action is for? Create action component for below Harvest app. For Harvest, anything in the following: https://help.getharvest.com/api-v2/timesheets-api/timesheets/time-entries/ https://help.getharvest.com/api-v2/projects-api/projects/projects/ https://help.getharvest.com/api-v2/projects-api/projects/task-assignments/ https://help.getharvest.com/api-v2/projects-api/projects/user-assignments/ https://help.getharvest.com/api-v2/reports-api/reports/time-reports/ https://help.getharvest.com/api-v2/users-api/users/users/ Harvest: Reports Invoices
App: Rewardful (affiliate & referral platform) API docs: https://developers.rewardful.com/ Requesting the following actions to support end-to-end affiliate program management: Campaigns List campaigns Create campaign Get campaign details Update campaign settings Affiliates List affiliates (with filters: status, campaign, date joined) Create affiliate Get affiliate by ID Update affiliate Generate Magic Link (SSO login for affiliate) Affiliate Links List affiliate links Create affiliate link Get / update link Affiliate Coupons List coupons Create / update coupon Get coupon details Referrals List referrals (by affiliate, date range, status) Get referral details Commissions List commissions (by affiliate, status: pending/approved/paid) Get commission details Update commission value Delete commission Payouts List payouts Get payout details Mark payout as paid Use case: Managing an affiliate program directly from an AI assistant — tracking new signups, monitoring commissions
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to PipedreamHQ/pipedream, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of PipedreamHQ/pipedream acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 76.1% were successfully merged into the primary branch.
PipedreamHQ/pipedream has a recorded first-timer success rate of 65.8%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 64.7 places PipedreamHQ/pipedream in the Welcoming tier.
The external pull request merge rate is 76.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, PipedreamHQ/pipedream currently has 27 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for PipedreamHQ/pipedream are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.