New Components - verifly

[james-sib]

Verifly

Adds a new app component for Verifly, an agent-native email verification API.

What's included

• verifly.app.mjs — app definition with Bearer API-key auth (Authorization: Bearer <key>), a _baseUrl() of https://verifly.email/api/v1, shared _makeRequest helper, and methods (verifyEmail, createBulkJob, getJob, getCredits) plus reusable prop definitions.
• Action: Verify Email (verifly-verify-email) — verifies a single address (GET /api/v1/verify) returning deliverability, syntax, MX, SMTP, disposable, role, catch-all and free-provider signals.
• Action: Create Bulk Job (verifly-create-bulk-job) — submits a list for asynchronous bulk verification (POST /api/v1/verify/bulk) and returns a job to poll for results.
• package.json.

Notes

• API reference: https://verifly.email/openapi.json
• Both actions were run end-to-end against the live API and return successfully.
• Server-side managed auth for the verifly app will need to be stood up on the Pipedream side.

Summary by CodeRabbit

• New Features
  • Added Verifly support with a new app connection and API-backed actions.
  • You can now verify a single email or create a bulk verification job.
  • Added options to provide bulk email lists, output filenames, and webhook URLs.
  • Included access to job status and remaining credit information through the Verifly integration.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
pipedream-docs-redirect-do-not-edit	Ignored		Jun 28, 2026 8:27am

[pipedream-component-development]

Thank you so much for submitting this! We've added it to our backlog to review, and our team has been notified.

[pipedream-component-development]

Thanks for submitting this PR! When we review PRs, we follow the Pipedream component guidelines. If you're not familiar, here's a quick checklist:

• Create components to address specific use cases whenever possible
• Component keys should follow the format app_name_slug-slugified-component-name
• Components should follow the standard directory structure
• Prefer Node.js client libraries to REST APIs
• When making API requests, handle pagination to ensure all data / events are processed
• Use secret props to capture sensitive data
• Props and methods should be defined in app files whenever possible
• Document methods with JS Docs
• Use optional props whenever possible, and set a default value where you can
• Use async options to accept user input wherever possible

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a new Verifly integration for Pipedream: a shared app module with axios-based API methods (verifyEmail, createBulkJob, getJob, getCredits), a package manifest, and two actions—"Verify Email" and "Create Bulk Job"—that wire app props and return API responses.

Changes

Verifly Integration

Layer / File(s)	Summary
App module and package config components/verifly/package.json, components/verifly/verifly.app.mjs	Defines the Verifly Pipedream app with prop definitions (email, emails, filename, webhookUrl), an axios-based _makeRequest wrapper using Authorization: Bearer from $auth.api_key, and four API methods targeting https://verifly.email/api/v1. Package metadata sets public publishing and a @pipedream/platform dependency.
Verify Email and Create Bulk Job actions components/verifly/actions/verify-email/verify-email.mjs, components/verifly/actions/create-bulk-job/create-bulk-job.mjs	Two action modules wiring app props; verify-email calls app.verifyEmail and exports a $summary with the returned result; create-bulk-job calls app.createBulkJob with emails, filename, and webhook_url, conditionally including job_id in the $summary.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested reviewers

• michelle0927

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description covers the summary but omits the required checklist items for versioning, app integration, and CodeRabbit review.	Add the checklist section and explicitly address version updates, app integration status, and CodeRabbit comments.
Title check	❓ Inconclusive	The title is vague and doesn't clearly summarize the new Verifly app and actions.	Rename it to mention the Verifly app and actions, e.g. "Add Verifly app and email verification actions".

✅ Passed checks (3 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@components/verifly/verifly.app.mjs`:
- Around line 12-16: The shared prop definition for emails needs a clearer
description because the current text does not show the expected array format,
which can lead users or agents to pass a comma-delimited string instead of a
list. Update the emails prop’s description in verifly.app.mjs to explicitly
describe that it expects an array of strings and include a concrete inline
example like ["lead@example.com", "sales@example.com"] so the bulk-job action
usage is unambiguous.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: d42b46e6-8bbb-47e5-9565-a0d1c19ec5f5

📥 Commits

Reviewing files that changed from the base of the PR and between c49e5f6 and bd9a189.

📒 Files selected for processing (4)

• components/verifly/actions/create-bulk-job/create-bulk-job.mjs
• components/verifly/actions/verify-email/verify-email.mjs
• components/verifly/package.json
• components/verifly/verifly.app.mjs

[coderabbitai]

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Add a concrete example for the emails array prop.

This shared prop is reused by the bulk-job action, but the description never shows the expected array shape. In practice that makes it easy for agents/users to pass a single comma-delimited string instead of an actual list. Something like ["lead@example.com", "sales@example.com"] would remove the ambiguity.

As per coding guidelines, prop descriptions must be explicit about formats and examples. As per path instructions, prop description fields must be written for AI agent consumption and include concrete inline examples for non-obvious formats.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@components/verifly/verifly.app.mjs` around lines 12 - 16, The shared prop
definition for emails needs a clearer description because the current text does
not show the expected array format, which can lead users or agents to pass a
comma-delimited string instead of a list. Update the emails prop’s description
in verifly.app.mjs to explicitly describe that it expects an array of strings
and include a concrete inline example like ["lead@example.com",
"sales@example.com"] so the bulk-job action usage is unambiguous.

Sources: Coding guidelines, Path instructions