Reply.io

Overview

Connect Reply.io with Flows360

Sales engagement platform for contacts, campaigns, and outbound outreach workflows.

Use the Reply.io 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 10 actions and no declared triggers.

Available actions

• Get Contact
• Create or Update Contact
• Delete Contact
• Add Contact to Campaign
• Push Contact to Campaign
• Remove Contact from Campaign
• Remove Contact from All Campaigns
• Mark Contact as Replied
• Plus 2 additional declared actions.

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: Reply.io
• Package: @activepieces/piece-reply-io@0.2.0
• Exact artifact digest: sha256:6a3854903c711c3336c585f7da5e073110ff609d57b88033b16db5a919441708
• 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

• Get Contact (get_contact), Look up a contact in Reply.io by their email address and retrieve their details. Classification: read.
• Create or Update Contact (create_or_update_contact), Add a new contact to Reply.io, or update their details if a contact with that email already exists. Classification: read.
• Delete Contact (delete_contact), Permanently delete a contact from Reply.io by their email address. This cannot be undone. Classification: read.
• Add Contact to Campaign (create_and_push_to_campaign), Create a new contact (or update an existing one) and immediately enrol them in a campaign so they start receiving outreach emails. Classification: read.
• Push Contact to Campaign (push_to_campaign), Enrol an existing contact in a campaign so they start receiving outreach emails. Enable "Force Push" to move the contact even if they are already active in another campaign. Classification: read.
• Remove Contact from Campaign (remove_from_campaign), Stop a contact from receiving further emails in a specific campaign. The contact's record is kept in Reply.io. Classification: read.
• Remove Contact from All Campaigns (remove_from_all_campaigns), Remove a contact from every campaign they are enrolled in. No further emails will be sent to them. Their contact record is kept in Reply.io. Classification: read.
• Mark Contact as Replied (mark_replied), Record that a contact has replied to your outreach. This stops further follow-up emails to that contact across all active campaigns. Classification: read.
• Mark Contact as Finished (mark_finished), Mark a contact as finished so they no longer receive emails in any campaign. Use this when you have completed all outreach to that contact. Classification: read.
• Custom API Call (custom_api_call), Make a custom API call to a specific endpoint 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

Setup

Setup

1. Add the Reply.io 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-reply-io@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
• Only the 10 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

Related documentation