Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

ZeroBounce

ZeroBounce is an email validation service that helps you reduce bounces, improve email deliverability and increase email marketing ROI.

CategoryOther
Authenticationcustom
Version0.1.7
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect ZeroBounce with Flows360

ZeroBounce is an email validation service that helps you reduce bounces, improve email deliverability and increase email marketing ROI.

Use the ZeroBounce 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

  • Validate 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: ZeroBounce
  • Package: @activepieces/piece-zerobounce@0.1.7
  • Exact artifact digest: sha256:13252f1cbc36f36c57d4a222092cf3194cda4caa9079d45d1f3ef47e7a8dcf02
  • 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

  • Validate Email (validateEmail), Declared by the pinned package. 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 objects1
Supported actions1
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Validate Email Yes No Declared action `validateEmail` in the pinned package.

Supported actions

Validate Email · Read

validate_email · Risk: low · Retry: safe

Inputs

  • email · string · Required
  • cacheResponse · boolean · Optional, Store the response in the project store for future use.

Setup

Setup

  1. Add the ZeroBounce 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-zerobounce@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 ZeroBounce 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-zerobounce@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