Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Echowin

Echowin integration for Flows360 workflows.

CategoryArtificial Intelligence
Authenticationcustom
Version0.1.7
Published scopes0 published scopes
Last updatedSeptember 29, 2026

Overview

Connect Echowin with Flows360

Echowin integration for Flows360 workflows.

Use the Echowin 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 3 actions and 1 trigger.

Available actions

  • Create Contact
  • Delete Contact
  • Find Contact

Available triggers

  • New Contact

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: Echowin
  • Package: @activepieces/piece-echowin@0.1.7
  • Exact artifact digest: sha256:87988f448ef878633b2143aafbb94c94396ee289105a132db7a993e0771f8eb9
  • 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

  • Create Contact (createContact), Create a new contact with optional tags, custom fields, notes, and board assignments Classification: read.
  • Delete Contact (deleteContact), Delete a contact by ID Classification: read.
  • Find Contact (findContactByName), Get a paginated list of contacts and search by name, email, or phone number Classification: read.

Trigger contracts

  • New Contact, polling.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects4
Supported actions3
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Echowin API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Contact Yes No Create a new contact with optional tags, custom fields, notes, and board assignments
Delete Contact Yes No Delete a contact by ID
Find Contact Yes No Get a paginated list of contacts and search by name, email, or phone number
New Contact Yes No polling trigger declared by the pinned package.

Supported actions

Create Contact · Read

Create a new contact with optional tags, custom fields, notes, and board assignments

create_contact · Risk: low · Retry: safe

Inputs

  • firstName · string · Optional, Contact's first name
  • lastName · string · Optional, Contact's last name
  • email · string · Optional, Contact's email address
  • number · string · Required, Contact phone number (will be automatically cleaned)
  • carrier · string · Optional, Phone carrier name
Delete Contact · Read

Delete a contact by ID

delete_contact · Risk: low · Retry: safe

Inputs

  • contactId · string · Required, The unique identifier of the contact to delete
Find Contact · Read

Get a paginated list of contacts and search by name, email, or phone number

find_contact_by_name · Risk: low · Retry: safe

Inputs

  • search · string · Optional, Search contacts by name, email, or phone number

Triggers

New Contact · Poll

Trigger when a new contact is created in Echowin

Setup

Setup

  1. Add the Echowin 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-echowin@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 3 actions and 1 trigger 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.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Echowin 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-echowin@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