Overview
Connect MillionVerifier with Flows360
MillionVerifier is an email verifier service and API
Use the MillionVerifier 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 1 action and no declared triggers.
Available actions
- Verify Email
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: MillionVerifier
- Package:
@activepieces/piece-millionverifier@0.1.7 - Exact artifact digest:
sha256:8bb085c7e42fba5c1d5cd6d9138030d52da2f601ccba942bbe31770da3d99c66 - 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 email address using Million Verifier API 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
Authentication
Authentication method: custom
Authentication profiles
connection · custom
- MillionVerifier API Key Required · protected credential
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Verify Email | Yes | No | Verify email address using Million Verifier API |
Supported actions
Verify Email · Read
Verify email address using Million Verifier API
verify_email · Risk: low · Retry: safe
Inputs
email· string · Required, The email address to verifytimeout· number · Optional, Timeout in seconds (default: 10)
Setup
Setup
- Add the MillionVerifier connector to the workflow in the target Flows360 Studio instance.
- 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.
- Provide the connection fields declared by the pinned package:
- No provider credential fields are declared by the pinned package.
- Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
- Test the workflow in the appropriate environment before enabling production scheduling or event delivery.
Limitations
Limitations and operational notes
- This content describes
@activepieces/piece-millionverifier@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes. - Only the 1 action 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 MillionVerifier 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-millionverifier@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.