Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

ConnectUC

ConnectUC integration for Flows360 workflows.

CategoryOther
AuthenticationOAuth 2.0
Version0.0.11
Published scopes1 published scope
Last updatedSeptember 19, 2026

Overview

Connect ConnectUC with Flows360

ConnectUC integration for Flows360 workflows.

Use the ConnectUC 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 6 actions and 8 triggers.

Available actions

  • Create Contact
  • Set Do Not Disturb
  • Find CDR
  • Initiate Call
  • Send SMS
  • Update CDR

Available triggers

  • New Recording
  • New Call Transcription
  • New Call Summary
  • New CDR
  • New Incoming Call
  • New Outgoing Call
  • Plus 2 additional declared triggers.

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: ConnectUC
  • Package: @activepieces/piece-connectuc@0.0.11
  • Exact artifact digest: sha256:4fbdd1a13424a3a5b99dfb418d671bd8fe8ff25c7cf96c3fd2de3335d6ee7362
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2. 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 (create-contact), Create a new contact in ConnectUC Classification: read.
  • Set Do Not Disturb (do-not-disturb), Enable or disable Do Not Disturb status for a user in ConnectUC Classification: read.
  • Find CDR (find-cdr), Find a Call Detail Record (CDR) by original call ID Classification: read.
  • Initiate Call (initiate-call), Initiate an outbound call from a ConnectUC extension Classification: read.
  • Send SMS (send-sms), Send an SMS message through ConnectUC Classification: read.
  • Update CDR (update-cdr), Update a Call Detail Record (CDR) in ConnectUC Classification: read.

Trigger contracts

  • New Recording, webhook.
  • New Call Transcription, webhook.
  • New Call Summary, webhook.
  • New CDR, webhook.
  • New Incoming Call, webhook.
  • New Outgoing Call, webhook.
  • New Voicemail, webhook.
  • New SMS, webhook.

Verification

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

Capability summary

AuthenticationOAuth 2.0
Supported objects14
Supported actions6
Triggers8

Authentication

Authentication method: OAuth 2.0

Required scopes

offline_access

Authentication profiles

connection · oauth2

OAuth scopes: offline_access

Supported objects

ObjectReadWriteNotes
Create Contact Yes No Create a new contact in ConnectUC
Set Do Not Disturb Yes No Enable or disable Do Not Disturb status for a user in ConnectUC
Find CDR Yes No Find a Call Detail Record (CDR) by original call ID
Initiate Call Yes No Initiate an outbound call from a ConnectUC extension
Send SMS Yes No Send an SMS message through ConnectUC
Update CDR Yes No Update a Call Detail Record (CDR) in ConnectUC
New Recording Yes No webhook trigger declared by the pinned package.
New Call Transcription Yes No webhook trigger declared by the pinned package.
New Call Summary Yes No webhook trigger declared by the pinned package.
New CDR Yes No webhook trigger declared by the pinned package.
New Incoming Call Yes No webhook trigger declared by the pinned package.
New Outgoing Call Yes No webhook trigger declared by the pinned package.
New Voicemail Yes No webhook trigger declared by the pinned package.
New SMS Yes No webhook trigger declared by the pinned package.

Supported actions

Create Contact · Read

Create a new contact in ConnectUC

create_contact · Risk: low · Retry: safe

Inputs

  • domain · string · Optional, Select domain to which this trigger applies
  • user · string · Required, Select the user who owns this contact
  • first_name · string · Required, The first name of the contact
  • last_name · string · Required, The last name of the contact
  • email · string · Optional, The email address of the contact
  • phones · array · Required, The phone numbers of the contact
  • company · string · Optional, The company of the contact
  • tags · array · Optional, The tags of the contact
Set Do Not Disturb · Read

Enable or disable Do Not Disturb status for a user in ConnectUC

do_not_disturb · Risk: low · Retry: safe

Inputs

  • domain · string · Optional, Select domain to which this trigger applies
  • user · string · Required, Select the user who owns this contact
  • dnd · boolean · Required, Enable or disable Do Not Disturb status
Find CDR · Read

Find a Call Detail Record (CDR) by original call ID

find_cdr · Risk: low · Retry: safe

Inputs

  • origCallid · string · Required, The original call ID (origCallid) to search for
Initiate Call · Read

Initiate an outbound call from a ConnectUC extension

initiate_call · Risk: low · Retry: safe

Inputs

  • domain · string · Optional, Select domain to which this trigger applies
  • user · string · Required, Select the user who owns this contact
  • device · string · Required, Select the device to use for the call
  • toNumber · string · Required, The destination number of the call
Send SMS · Read

Send an SMS message through ConnectUC

send_sms · Risk: low · Retry: safe

Inputs

  • recipients · array · Required, The phone number to send the SMS to
  • content · string · Required, The SMS message content
  • sender · string · Required, Select the SMS sender number
  • attachment_urls · array · Optional, The media attachment urls for the SMS message
Update CDR · Read

Update a Call Detail Record (CDR) in ConnectUC

update_cdr · Risk: low · Retry: safe

Inputs

  • cdrId · string · Required, The ID of the CDR to update
  • note · string · Required, Note about the call
  • disposition · string · Optional, The call disposition or outcome
  • reason · string · Optional, The reason for the call outcome

Triggers

New Recording · Webhook

Triggers when a new call recording is available

Inputs

  • domain · string
  • users · array
New Call Transcription · Webhook

Triggers when a new call transcription is created

Inputs

  • domain · string
  • users · array
New Call Summary · Webhook

Triggers when a new call summary is created

Inputs

  • domain · string
  • users · array
New CDR · Webhook

Triggers when a new Call Detail Record (CDR) is created

Inputs

  • domain · string
  • users · array
New Incoming Call · Webhook

Triggers when a new incoming call is received

Inputs

  • domain · string
  • users · array
  • status · string
New Outgoing Call · Webhook

Triggers when a new outgoing call is initiated

Inputs

  • domain · string
  • users · array
New Voicemail · Webhook

Triggers when a new voicemail is received

Inputs

  • domain · string
  • users · array
New SMS · Webhook

Triggers when a new SMS message is received or sent

Inputs

  • domain · string
  • users · string
  • recipients · array
  • direction · string

Setup

Setup

  1. Add the ConnectUC 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.

OAuth scopes

  • offline_access
  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-connectuc@0.0.11; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 8 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 ConnectUC 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-connectuc@0.0.11 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