Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Components] engage #13410

Open
pipedream-component-development opened this issue Aug 8, 2024 · 2 comments · May be fixed by #15656
Open

[Components] engage #13410

pipedream-component-development opened this issue Aug 8, 2024 · 2 comments · May be fixed by #15656
Assignees
@lcaresia
Labels
triaged For maintainers: This issue has been triaged by a Pipedream employee

Comments

@pipedream-component-development
Copy link
Collaborator

engage

URLs

Actions

add-event

Prompt

Send a specific action or event to Engage. The required prop here is 'event', which should include the details of the action or event to be sent.

update-create-customer

Prompt

This dual-purpose action allows the user to either create a new customer or update an existing one in Engage platform. The required props for this action are 'customer-id' which is the ID of an existing customer and 'customer-data', which includes the information about the new customer or the updates for existing one. If 'customer-id' is not provided, a new customer will be created.
@vunguyenhung vunguyenhung added the triaged For maintainers: This issue has been triaged by a Pipedream employee label Sep 19, 2024
@lcaresia lcaresia self-assigned this Feb 17, 2025
@lcaresia lcaresia moved this from To Do to Doing in Component (Source and Action) Backlog Feb 18, 2025
@lcaresia lcaresia linked a pull request Feb 18, 2025 that will close this issue
[Components] engage #13410 #15656
Open
@lcaresia lcaresia moved this from Doing to Ready for PR Review in Component (Source and Action) Backlog Feb 18, 2025
@luancazarine luancazarine moved this from Ready for PR Review to In Review in Component (Source and Action) Backlog Feb 18, 2025
@luancazarine luancazarine moved this from In Review to Ready for QA in Component (Source and Action) Backlog Feb 18, 2025
@vunguyenhung vunguyenhung moved this from Ready for QA to Changes Required in Component (Source and Action) Backlog Feb 19, 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/Components-engage-19ebf548bb5e81fbaf2fc879c85f2033

@lcaresia lcaresia moved this from Changes Required to Ready for PR Review in Component (Source and Action) Backlog Feb 24, 2025
@luancazarine luancazarine moved this from Ready for PR Review to In Review in Component (Source and Action) Backlog Feb 24, 2025
@luancazarine luancazarine moved this from In Review to Changes Required in Component (Source and Action) Backlog Feb 24, 2025
@lcaresia lcaresia moved this from Changes Required to Ready for PR Review in Component (Source and Action) Backlog Feb 25, 2025
@lcaresia lcaresia moved this from Ready for PR Review to Ready for QA in Component (Source and Action) Backlog Feb 27, 2025
@vunguyenhung vunguyenhung moved this from Ready for QA to In QA in Component (Source and Action) Backlog Feb 28, 2025
@vunguyenhung vunguyenhung moved this from In QA to Ready for Release in Component (Source and Action) Backlog Feb 28, 2025
@vunguyenhung
Copy link
Collaborator

Hi everyone, all test cases are passed! Ready for release!

Test report
https://vunguyenhung.notion.site/Components-engage-19ebf548bb5e81fbaf2fc879c85f2033

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lcaresia lcaresia

Labels
triaged For maintainers: This issue has been triaged by a Pipedream employee
Projects
Component (Source and Action) Backlog
Status: Ready for Release
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Components] engage #13410 PipedreamHQ/pipedream
3 participants
@lcaresia @vunguyenhung @pipedream-component-development