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.

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

[Components] xverify #15237

Closed
pipedream-component-development opened this issue Jan 9, 2025 · 3 comments · Fixed by #15321
Closed

[Components] xverify #15237

pipedream-component-development opened this issue Jan 9, 2025 · 3 comments · Fixed by #15321
Assignees
Labels
triaged For maintainers: This issue has been triaged by a Pipedream employee

Comments

@pipedream-component-development
Copy link
Collaborator

pipedream-component-development commented Jan 9, 2025

xverify

URLs

Actions

verify-email

Prompt

Send an email verification request. Requires the email address to verify. Optionally specify additional metadata or configuration for the request.

verify-phone

Prompt

Send a phone verification request via SMS or call. Requires the phone number to verify. Optionally specify country code or message template.

verify-address

Prompt

Submit an address verification request. Requires details like street, city, state, and postal code. Optionally include additional metadata for the request.

@pipedream-component-development pipedream-component-development added the triaged For maintainers: This issue has been triaged by a Pipedream employee label Jan 9, 2025
@jcortes jcortes self-assigned this Jan 15, 2025
@jcortes jcortes moved this from To Do to Doing in Component (Source and Action) Backlog Jan 15, 2025
@jcortes jcortes moved this from Doing to Ready for PR Review in Component (Source and Action) Backlog Jan 16, 2025
@luancazarine luancazarine moved this from Ready for PR Review to In Review in Component (Source and Action) Backlog Jan 16, 2025
@luancazarine luancazarine moved this from In Review to Ready for QA in Component (Source and Action) Backlog Jan 16, 2025
@vunguyenhung vunguyenhung moved this from Ready for QA to In QA in Component (Source and Action) Backlog Jan 17, 2025
@vunguyenhung vunguyenhung moved this from In QA to Changes Required in Component (Source and Action) Backlog Jan 17, 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-xverify-17dbf548bb5e817c8c07fdd2ca142a96

@jcortes
Copy link
Collaborator

jcortes commented Jan 17, 2025

Hi @vunguyenhung

Verify Address - Failed

Required props - failed

The request failed with status code 400 it's because you are no setting either the zip code or city and state props according to the alert here
Image

So that's why you are getting an error from the endpoint

Verify Email - Failed

invalid_syntax when testing the action
I've made a few changes in the code
So now you are able to change the domain in the components, if what you want is to validate the email [email protected] you need to make sure the domain is added to the trusted domain list in XVerify. You can go there by clicking on Account

Image

and then set the domain as a prop and test. Let me know if that works otherwise there are a list of email status that you can check here https://apidocs.xverify.com/#email-lists-of-values

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

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

Test report
https://vunguyenhung.notion.site/Components-xverify-17dbf548bb5e817c8c07fdd2ca142a96

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triaged For maintainers: This issue has been triaged by a Pipedream employee
Development

Successfully merging a pull request may close this issue.

3 participants