Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Reoon Email Verifier

Email validation service that cleans invalid, temporary & unsafe email addresses.

CategoryMarketing
Authenticationcustom
Version0.1.7
Published scopes0 published scopes
Last updatedSeptember 23, 2026

Overview

Connect Reoon Email Verifier with Flows360

Email validation service that cleans invalid, temporary & unsafe email addresses.

Use the Reoon Email Verifier connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 6 actions and no declared triggers.

Available actions

  • Verify Email
  • Create Bulk Email Verification
  • Get Bulk Verification Result
  • Verify Email Address
  • Create Bulk Email Verification
  • Get Bulk Email Verification Result

Available triggers

  • No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Reoon Email Verifier
  • Package: @activepieces/piece-reoon-verifier@0.1.7
  • Exact artifact digest: sha256:f5c925f59ff4e5ecaf0200ad15d1c7e73a77e7b93a888a9af2353c612db8aae1
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Verify Email (verifyEmail), Verify a single email Classification: read.
  • Create Bulk Email Verification (bulkEmailVerificationTask), Creates bulk email verification task. Classification: read.
  • Get Bulk Verification Result (bulkVerificationResult), Retrieves result of bulk verification email by task ID. Classification: read.
  • Verify Email Address (verify_email_address), Verify a single email address synchronously. Classification: read.
  • Create Bulk Email Verification (create_bulk_email_verification), Creates an asynchronous bulk email verification task. Classification: read.
  • Get Bulk Email Verification Result (get_bulk_email_verification_result), Reads the status and results of a bulk verification task. Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects6
Supported actions6
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Verify Email Yes No Verify a single email
Create Bulk Email Verification Yes No Creates bulk email verification task.
Get Bulk Verification Result Yes No Retrieves result of bulk verification email by task ID.
Verify Email Address Yes No Verify a single email address synchronously.
Create Bulk Email Verification Yes No Creates an asynchronous bulk email verification task.
Get Bulk Email Verification Result Yes No Reads the status and results of a bulk verification task.

Supported actions

Verify Email · Read

Verify a single email

verify_email · Risk: low · Retry: safe

Inputs

  • email · string · Required, Email to verify
  • mode · string · Required, Verification mode (Power mode is more accurate but a bit slower)
Create Bulk Email Verification · Read

Creates bulk email verification task.

bulk_email_verification_task · Risk: low · Retry: safe

Inputs

  • taskName · string · Required, Name of the verification task
  • emails · array · Required, Emails to verify (You can also provide multiple emails separated by comma)
Get Bulk Verification Result · Read

Retrieves result of bulk verification email by task ID.

bulk_verification_result · Risk: low · Retry: safe

Inputs

  • task_id · string · Required, Provide the task ID for the bulk verification task. You can fetch this from the `Create Bulk Email Verification` action.
Verify Email Address · Read

Verify a single email address synchronously.

verify_email_address · Risk: low · Retry: safe

Inputs

  • email · string · Required, Email to verify
  • mode · string · Required, Verification mode (Power mode is more accurate but a bit slower)
Create Bulk Email Verification · Read

Creates an asynchronous bulk email verification task.

create_bulk_email_verification · Risk: low · Retry: safe

Inputs

  • taskName · string · Required, Name of the verification task
  • emails · array · Required, Emails to verify (You can also provide multiple emails separated by comma)
Get Bulk Email Verification Result · Read

Reads the status and results of a bulk verification task.

get_bulk_email_verification_result · Risk: low · Retry: safe

Inputs

  • task_id · string · Required, Provide the task ID for the bulk verification task. You can fetch this from the `Create Bulk Email Verification` action.

Setup

Setup

  1. Add the Reoon Email Verifier connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-reoon-verifier@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 0 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Reoon Email Verifier connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-reoon-verifier@0.1.7 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com