Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Reachinbox

Reachinbox integration for Flows360 workflows.

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

Overview

Connect Reachinbox with Flows360

Reachinbox integration for Flows360 workflows.

Use the Reachinbox 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 13 actions and 7 triggers.

Available actions

  • Add Leads
  • Add Blocklist
  • Add Email
  • Enable Warmup
  • Get Campaign Analytics
  • Get Summary
  • Pause Campaign
  • Pause Warmup
  • Plus 5 additional declared actions.

Available triggers

  • Campaign Completed
  • Email Bounced
  • Email Opened
  • Email Sent
  • Lead Interested
  • Lead Not Interested
  • Plus 1 additional declared trigger.

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: Reachinbox
  • Package: @activepieces/piece-reachinbox@0.2.0
  • Exact artifact digest: sha256:e0e599a971777ac78e5ae4f24681912a6ba667bbe37ca37362623500412cf150
  • 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

  • Add Leads (addLeads), Add leads to campaigns dynamically by selecting a campaign, entering lead details, and including custom variables. Classification: read.
  • Add Blocklist (addBlocklist), Add email addresses, domains, and keywords to the blocklist. Classification: read.
  • Add Email (addEmail), Add an email to a specific account. Classification: read.
  • Enable Warmup (enableWarmup), Enable warmup for specific email accounts where it is currently disabled. Classification: read.
  • Get Campaign Analytics (getCampaignAnalytics), Fetch analytics data for a selected campaign based on a date range. Classification: read.
  • Get Summary (getSummary), Get a summary of campaign analytics within a date range. Classification: read.
  • Pause Campaign (pauseCampaign), Pause a selected campaign. Classification: read.
  • Pause Warmup (pauseWarmup), Pause warmup for selected email accounts. Classification: read.
  • Remove Email (removeEmail), Remove an email account from the system. Classification: read.
  • Set Schedule (setSchedule), Update the schedule for a specific Campaign Classification: read.
  • Start Campaign (startCampaign), Starts a Campaign Classification: read.
  • Update Lead (updateLead), Updates a Lead. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • Campaign Completed, webhook.
  • Email Bounced, webhook.
  • Email Opened, webhook.
  • Email Sent, webhook.
  • Lead Interested, webhook.
  • Lead Not Interested, webhook.
  • Reply Received, webhook.

Verification

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

Capability summary

Authenticationcustom
Supported objects20
Supported actionsNot published
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Add Leads Yes No Add leads to campaigns dynamically by selecting a campaign, entering lead details, and including custom variables.
Add Blocklist Yes No Add email addresses, domains, and keywords to the blocklist.
Add Email Yes No Add an email to a specific account.
Enable Warmup Yes No Enable warmup for specific email accounts where it is currently disabled.
Get Campaign Analytics Yes No Fetch analytics data for a selected campaign based on a date range.
Get Summary Yes No Get a summary of campaign analytics within a date range.
Pause Campaign Yes No Pause a selected campaign.
Pause Warmup Yes No Pause warmup for selected email accounts.
Remove Email Yes No Remove an email account from the system.
Set Schedule Yes No Update the schedule for a specific Campaign
Start Campaign Yes No Starts a Campaign
Update Lead Yes No Updates a Lead.
Custom API Call Yes No Make a custom API call to a specific endpoint
Campaign Completed Yes No webhook trigger declared by the pinned package.
Email Bounced Yes No webhook trigger declared by the pinned package.
Email Opened Yes No webhook trigger declared by the pinned package.
Email Sent Yes No webhook trigger declared by the pinned package.
Lead Interested Yes No webhook trigger declared by the pinned package.
Lead Not Interested Yes No webhook trigger declared by the pinned package.
Reply Received Yes No webhook trigger declared by the pinned package.

Setup

Setup

  1. Add the Reachinbox 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-reachinbox@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 13 actions and 7 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 Reachinbox 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-reachinbox@0.2.0 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