Skip to content

Help Scout: add triggers for conversation thread events (e.g. convo.customer.reply.created, convo.agent.reply.created, convo.note.created) #16372

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
RoyMingelers opened this issue Apr 19, 2025 · 3 comments · Fixed by #16444
Assignees
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed triaged For maintainers: This issue has been triaged by a Pipedream employee trigger / source New trigger / source request

Comments

@RoyMingelers
Copy link

RoyMingelers commented Apr 19, 2025

Describe the event source. What app is this for, and what event does the trigger correspond to?
This is for the Help Scout integration in Pipedream. We need new, native Pipedream triggers for Help Scout conversation‑thread events—specifically the webhooks fired when a customer reply (convo.customer.reply.created), agent reply (convo.agent.reply.created), or internal note (convo.note.created) is added to an existing conversation.

Please provide a link to the relevant API docs for the specific service / operation this trigger is tied to.
Help Scout Webhooks / Subscriptions API:
https://developer.helpscout.com/subscriptions/webhooks-reference/

@RoyMingelers RoyMingelers added enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed trigger / source New trigger / source request labels Apr 19, 2025
@vunguyenhung vunguyenhung added the triaged For maintainers: This issue has been triaged by a Pipedream employee label Apr 23, 2025
@jcortes jcortes self-assigned this Apr 24, 2025
@jcortes jcortes moved this from Prioritized to Doing in Component (Source and Action) Backlog Apr 24, 2025
@jcortes jcortes moved this from Doing to Ready for PR Review in Component (Source and Action) Backlog Apr 24, 2025
@luancazarine luancazarine moved this from Ready for PR Review to In Review in Component (Source and Action) Backlog Apr 28, 2025
@luancazarine luancazarine moved this from In Review to Ready for QA in Component (Source and Action) Backlog Apr 28, 2025
@vunguyenhung vunguyenhung moved this from Ready for QA to In QA in Component (Source and Action) Backlog Apr 29, 2025
@vunguyenhung vunguyenhung moved this from In QA to Ready for QA in Component (Source and Action) Backlog Apr 29, 2025
@vunguyenhung vunguyenhung moved this from Ready for QA to In QA in Component (Source and Action) Backlog Apr 29, 2025
@vunguyenhung vunguyenhung moved this from In QA to Ready for QA in Component (Source and Action) Backlog Apr 29, 2025
@vunguyenhung vunguyenhung moved this from Ready for QA to Changes Required in Component (Source and Action) Backlog Apr 29, 2025
@vunguyenhung
Copy link
Collaborator

Hello everyone, I have tested this PR and there're some test cases failed or needed improvement.

Please check the test report below for more information
https://vunguyenhung.notion.site/Help-Scout-add-triggers-for-conversation-thread-events-e-g-convo-customer-reply-created-convo-a-1e3bf548bb5e81fb8c9ad1bcf598b875

@jcortes
Copy link
Collaborator

jcortes commented Apr 29, 2025

Hi @vunguyenhung please try again with latest push, Thanks in advance!

@jcortes jcortes moved this from Changes Required to Ready for QA in Component (Source and Action) Backlog Apr 29, 2025
@vunguyenhung vunguyenhung moved this from Ready for QA to In QA in Component (Source and Action) Backlog Apr 30, 2025
@vunguyenhung vunguyenhung moved this from In QA to Ready for QA in Component (Source and Action) Backlog Apr 30, 2025
@vunguyenhung vunguyenhung moved this from Ready for QA to In QA in Component (Source and Action) Backlog Apr 30, 2025
@vunguyenhung vunguyenhung moved this from In QA to Ready for Release in Component (Source and Action) Backlog Apr 30, 2025
@vunguyenhung
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed triaged For maintainers: This issue has been triaged by a Pipedream employee trigger / source New trigger / source request
Development

Successfully merging a pull request may close this issue.

3 participants