Hey Team, since yesterday I had requested 3 PRs, pls approve/merge them - thx ! PR# 13245, 13247 and 13256 😉

Hey, we have a channel for self promotion ☺️

@simonhcd is there any eta when you guys onto approve the next lot...? would be great @kishanprmr

@everyone Hey mods, could someone please review this PR when you get a chance? https://github.com/activepieces/activepieces/pull/13433

Hi @Abdul (Viva-Palestina)💔 @ash and team , would like to know if VDP is still OPEN and being processed exactly as stated here? https://github.com/activepieces/activepieces/blob/main/SECURITY.md cause seems like no one replied to my email regarding newly discovered security issue and its past the SLA defined there. thanks

Hey @everyone /mods please review this PR. Its AgentLine's Piece which is the telephony infrastructure for AI agents by giving them a phone number of their own. Merge this PR to allow the builders using ActivePieces to give their workflow/agents all the telephony services required.. https://github.com/activepieces/activepieces/pull/13670

we're already live on smithery, Mcpuse, flowise and about to be listed on mastra as well.

Hey team have a PR to add some actions to the YouTube piece https://github.com/activepieces/activepieces/pull/13754 cheers

Thanks for the PR ! Team will review it.

Hey team I've submitted a fix for #13928 Triggers Health page always showing "No trigger data available".Please review it PR: https://github.com/activepieces/activepieces/pull/13948

Hi team I have raised a pr for bug fix #13849 Prevention of cross-project subflows from failing paused parent runs PR:https://github.com/activepieces/activepieces/pull/13949

@ash Hey Activepieces team, I have raised a PR for merging AgentLine piece into Activepieces a month ago and still the PR isn't merged. What's the problem with the PR? Are you facing some issues with it? I can fix them so that the merge of AgentLine piece into Activepieces could be successful. More than a thousand developers are using AgentLine every day to create agents who can call. https://github.com/activepieces/activepieces/pull/13670

HEy guys @kishanprmr can anyone have a look into it and merge it with the codebase? Just waiting for around 3-4 weeks now. would be great. https://github.com/activepieces/activepieces/pull/13691

Hey guys It's my first time contributing, whts the process to get this PR reviewed https://github.com/activepieces/activepieces/pull/14048

Hey everyone! 👋 I'm Rolan. I specialize in workflow automation with n8n, Make.com, Zapier, API integrations, and CRM automation. Excited to learn from the community, contribute where I can, and connect with other builders.

Hi! I recently implemented a feature/fix for Activepieces and opened a PR, but I saw the repository is currently not accepting unsolicited PRs. I really enjoyed working on the project and would love to contribute. Is there another way I can help, or is there a process for getting approval before working on a change?

Is anyone connected to Claude with LinkedIn Lemlist automation and has created an AI SDR to reply to messages?

Hey team! 👋 I submitted a new community piece for Figranium: PR #14756 (https://github.com/activepieces/activepieces/pull/14756). It was auto-closed by the bot, but: • Greptile AI review passed with a 5/5 confidence score • CLA is signed and all required PR description checkboxes are updated • Fully tested locally Could a maintainer please add the

keep-open

label to #14756 so it can be reviewed and merged? Thanks!

Hey @User! Just dropping a quick ping regarding PR #14756 for the Figranium piece. It passed Greptile with 5/5 and is fully tested. Whenever you get a chance, could you drop a

keep-open

label on it? Thanks!

Are you looking for someone to help with that?

Can you do this, I've been looking for something like this?

Sent you a DM, please check

yes

https://github.com/activepieces/activepieces/issues/15133 @majestic_gull_31897 please assign me this issue, would like to work on this

@Activepieces please assign me this issue, thanks!

Hi everyone — I investigated and reproduced Activepieces issue #14654 (piece-bundle downloads using the public API URL in split APP/WORKER deployments). I have a clean, tested fix on my fork, but PR #15305 was automatically closed by the current unsolicited-PR policy. The technical analysis, reproduction, and proposed fix are documented on the issue: https://github.com/activepieces/activepieces/issues/14654 Fork branch: https://github.com/jhapriyavart10/activepieces/tree/fix/internal-api-url-for-piece-bundles Could someone let me know the preferred process for getting this contribution reviewed / having the

keep-open

exemption applied?

Hi........I investigated and reproduced Activepieces issue #14654 (piece-bundle downloads using the public API URL in split APP/WORKER deployments). I have a clean, tested fix on my fork. PR #15305 was automatically closed by the current unsolicited-PR policy, so I wanted to ask for the preferred process for getting this contribution reviewed / having the

keep-open

exemption applied. The technical analysis and reproduction are documented on #14654: https://github.com/activepieces/activepieces/issues/14654 The fix branch has since been rebased onto the latest upstream/main: https://github.com/jhapriyavart10/activepieces/tree/fix/internal-api-url-for-piece-bundles

Hey everyone! 👋 I've built a complete Sent.dm Piece for Activepieces and would like to contribute it through the official Activepieces repository. It's currently at: - 8 actions - 2 triggers - 81 automated tests passing - 17 live API checks passing - HMAC webhook verification - idempotency and replay protection - webhook lifecycle handling - dynamic sender profiles/templates - Custom API Call Before opening the PR, I'd just like to confirm the preferred path for contributing a new official Piece. Should I submit it directly under packages/pieces/community/sent in the main Activepieces repository, or is there anything you'd like me to coordinate with a maintainer first? Happy to share the implementation and QA results. Thanks! 🙌

Hi team, Could you please add the keep-open label to this PR, or otherwise prevent it from being automatically closed? https://github.com/activepieces/activepieces/pull/15551 We’d like to contribute a new community piece for Kickcall AI, which will allow users to connect their Kickcall voice agents with Activepieces and perform various telephony and workflow actions. We’re happy to address any feedback or suggestions and make the necessary changes. Thank you for your help and support!

Hi! I'm Ric, co-founder of cloro (cloro.dev). We built a cloro piece for live search data: Search Google, Search Google News, and Get AI Answer, which returns what Google AI Mode, the Google AI Overview, Bing AI Mode, ChatGPT or Gemini answer to a prompt, with the sources they cite. The PR is https://github.com/activepieces/activepieces/pull/17318. The bot closed it as an outside PR. The CLA is signed, every action carries audience, aiMetadata and classification, and there are 17 vitest tests. We will maintain the piece. Could someone from the pieces team (Kishan Parmar?) add the keep-open label and reopen it? Thanks!