OpenPhone

Overview

Connect OpenPhone with Flows360

OpenPhone integration for Flows360 workflows.

Use the OpenPhone 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 4 actions and 5 triggers.

Available actions

• Send Message
• Create Contact
• Update Contact
• Get Call Summary

Available triggers

• Call Recording Completed
• Outgoing Message Delivered
• Outgoing Call Completed
• Incoming Call Completed
• Incoming Message Received

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: OpenPhone
• Package: @activepieces/piece-open-phone@0.1.7
• Exact artifact digest: sha256:f18841e40def5465754d92caa979cf97faa4c53e390d4303e8f2cefeffc5277f
• 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

• Send Message (send_message), Send SMS/MMS from your OpenPhone number to a recipient Classification: read.
• Create Contact (create_contact), Create a new contact in your OpenPhone workspace Classification: read.
• Update Contact (update_contact), Update an existing contact in your OpenPhone workspace Classification: read.
• Get Call Summary (get_call_summary), Retrieve an AI-generated summary of a specific call by ID. Call summaries are only available on OpenPhone Business plan. Classification: read.

Trigger contracts

• Call Recording Completed, webhook.
• Outgoing Message Delivered, webhook.
• Outgoing Call Completed, webhook.
• Incoming Call Completed, webhook.
• Incoming Message Received, webhook.

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

Supported objects

Triggers

Setup

Setup

1. Add the OpenPhone 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-open-phone@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
• Only the 4 actions and 5 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