Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

@AnkitSharmaOnGithub Please provide a video demonstrating the changes in this PR.

Sure @kishanprmr.
I am already working on testing the piece. I have started the recording for it. Will be done by EOD.

I have already mentioned it in the issue - #7606 (comment)

Update -
I have made the PR description as per the standards required by Active Pieces. Tried to make it the best possible PR description possible.

Also, adding videos for the demo. Please check link attached in the PR description.

Update -
I have finished the testing for the piece.

@kishanprmr @ashrafsamhouri I have completed this piece. I have also recorded very detailed demo vide for the actions & triggers.

Please find the link in the PR description. Thanks.

@AnkitSharmaOnGithub I will review it soon. Thanks!

@kishanprmr Please let me know, if I can be of any help to close this down sooner.

please revisit the webhook trigger as fireflies doesn't have webhook endpoint.

please revisit the webhook trigger as fireflies doesn't have webhook endpoint.

@kishanprmr Please correct me, if I am wrong here.

The fireflies API does support web-hooks. Please check the docs here - https://docs.fireflies.ai/graphql-api/webhooks. Also, please check the attached images.

I have also about it in the demo video.
Attaching link here again. Also, shared with you on DM- https://ankit-sh.notion.site/Copy-AI-Active-Pieces-Demo-Video-1ed488928533808280e6f878c5b710c5?pvs=4

@kishanprmr Please let me know, if any changes are required. For the trigger, please check the above comment.
Thanks.

@AnkitSharmaOnGithub

Thanks for the update. Since there is no webhook endpoint, but the PR contains a /webhook call inside the trigger, could you please revisit that? I believe it might throw an error. You can refer to the Moxie CRM piece trigger, where the user has to manually enter the webhookURL in the software. I assume it's the same case here.

@AnkitSharmaOnGithub

Thanks for the update. Since there is no webhook endpoint, but the PR contains a /webhook call inside the trigger, could you please revisit that? I believe it might throw an error. You can refer to the Moxie CRM piece trigger, where the user has to manually enter the webhookURL in the software. I assume it's the same case here.

@kishanprmr I have updated the code as per the above comment. Request you to please review.

@kishanprmr Request you to please review this PR.

Please use your email address to access the demo videos. I have shared access to you & ash.
Sharing link here again - https://drive.google.com/drive/folders/1jCvfxSAwTZVNOqwIs2-yumrjd4Ebsgnw?usp=sharing

View your CI Pipeline Execution ↗ for commit 8513bed.

☁️ Nx Cloud last updated this comment at 2025-05-15 06:14:55 UTC

@AnkitSharmaOnGithub ,

Thank you for your awesome contribution! 🎉
The bounty reward will be processed and forwarded within 2–3 days.If you have any questions or need further assistance, feel free to reach out.

Thanks @kishanprmr for the review. Awesome as always.
Hope this PR will help more people in the community.

I have noticed the same kind of errors by the same contributor on other PRs where some endpoints are hallucinated entirely. Endpoints which do not even exist on the docs but somehow he has implemented them in his PR.

That should obviously be a giveaway that it was written with AI and not properly reviewed by him the author.

Even in this PR, he originally used a non-existing webhook endpoint and published that as his final response.
That should tell you that he does not even care enough about the quality of his PR.

I am not clamoring to be the winner. Just saying that other people who want to contribute and see that the bar for acceptance is so low will not put in a better quality of code and may not even consider contributing for fear of investing too much and having a lower quality PR accepted.

I thought I was the only one that noticed what @AnkitSharmaOnGithub was doing lol :)

If you read the code, you'll see hallucinated endpoints, even if quality isn't the goal, shouldn't functionality be?

@kishanprmr you need to take a look at this thread

Thanks @kishanprmr for the review. Awesome as always.

Hope this PR will help more people in the community.

How are you confidently saying this @AnkitSharmaOnGithub

@iambenkay ,

I really appreciate you taking the time to share your thoughts — it’s clear that you care about the quality and future of Activepieces, and that means a lot.

To clarify, we don’t merge PRs based on who submits them first. Every PR, especially those related to new actions or triggers, goes through a review process where we test the functionality, verify endpoints, and assess code quality. If any fake or incorrect endpoints are used, the PR simply won’t be merged. Regarding the webhook endpoint in the PR: you're right that it wasn’t listed in the official Fireflies API docs. I’ve already asked the contributor to remove it. FIreflies requires user to manually enter the webhook endpoint, that's why it has markdown description.

Thanks again for pointing this out and for contributing to the project with both your code and your feedback. We hope you continue to be a part of Activepieces — your input is genuinely appreciated.