Skip to content
← Back to documentation
Technical Reference

VoIPstudio

VoIPstudio is a complete business phone system and scalable call center

CategoryCommunication
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect VoIPstudio with Flows360

VoIPstudio is a complete business phone system and scalable call center

Use the VoIPstudio 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 7 triggers.

Available actions

  • Create Contact
  • Make a Call to Lead
  • Make a Call
  • Make a Webcall
  • Send SMS
  • Custom API Call

Available triggers

  • Call Connected
  • Call Ended
  • Call Tracking
  • DTMF Received
  • Missed Call
  • New Call Recording
  • 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: VoIPstudio
  • Package: @activepieces/piece-voipstudio@0.2.0
  • Exact artifact digest: sha256:6ba86fe17c0079ee12eb8304762dae50a98a46646e4b7ebc35fd743124eeba3c
  • 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), Creates a new Contact resource Classification: read.
  • Make a Call to Lead (makeACallToLead), Make a leadcall from user to e164 number Classification: read.
  • Make a Call (makeACall), Make a call to a number in e164 format Classification: read.
  • Make a Webcall (makeAWebcall), Make a webcall from e164 number to other e164 number or extension Classification: read.
  • Send SMS (sendSms), Send new SMS resource Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • Call Connected, webhook.
  • Call Ended, webhook.
  • Call Tracking, polling.
  • DTMF Received, webhook.
  • Missed Call, webhook.
  • New Call Recording, webhook.
  • SMS 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 objects13
Supported actions6
Triggers7

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Contact Yes No Creates a new Contact resource
Make a Call to Lead Yes No Make a leadcall from user to e164 number
Make a Call Yes No Make a call to a number in e164 format
Make a Webcall Yes No Make a webcall from e164 number to other e164 number or extension
Send SMS Yes No Send new SMS resource
Custom API Call Yes No Make a custom API call to a specific endpoint
Call Connected Yes No webhook trigger declared by the pinned package.
Call Ended Yes No webhook trigger declared by the pinned package.
Call Tracking Yes No polling trigger declared by the pinned package.
DTMF Received Yes No webhook trigger declared by the pinned package.
Missed Call Yes No webhook trigger declared by the pinned package.
New Call Recording Yes No webhook trigger declared by the pinned package.
SMS Received Yes No webhook trigger declared by the pinned package.

Supported actions

Create Contact · Read

Creates a new Contact resource

create_contact · Risk: low · Retry: safe

Inputs

  • type · string · Optional, Contact type
  • dialler_source_id · number · Optional, Dialler source ID
  • outcome_id · number · Optional, Outcome ID
  • group_name · string · Optional, Group name
  • first_name · string · Optional, Contact first name
  • last_name · string · Optional, Contact last name
  • email · string · Optional, Contact email address
  • company · string · Optional, Company name
  • tel · string · Optional, Primary telephone number
  • tel_1 · string · Optional, Secondary telephone number
  • tel_2 · string · Optional, Tertiary telephone number
  • speed_dial_phone · string · Optional, Primary speed dial phone number
  • speed_dial_phone_1 · string · Optional, Secondary speed dial phone number
  • speed_dial_phone_2 · string · Optional, Tertiary speed dial phone number
  • mobile · string · Optional, Primary mobile number
  • mobile_1 · string · Optional, Secondary mobile number
  • mobile_2 · string · Optional, Tertiary mobile number
  • speed_dial_mobile · string · Optional, Primary speed dial mobile number
  • speed_dial_mobile_1 · string · Optional, Secondary speed dial mobile number
  • speed_dial_mobile_2 · string · Optional, Tertiary speed dial mobile number
  • notes · string · Optional, Contact notes
  • labels · array · Optional, Contact labels
  • groups · array · Optional, Contact groups
  • transfer_list · boolean · Optional, Whether to add to transfer list
  • user_id · number · Optional, User ID
Make a Call to Lead · Read

Make a leadcall from user to e164 number

make_acall_to_lead · Risk: low · Retry: safe

Inputs

  • caller_id · string · Required, Caller ID
  • to · string · Required, Destination number in e164 format or extension
  • tts · string · Required, Text to speech content
Make a Call · Read

Make a call to a number in e164 format

make_acall · Risk: low · Retry: safe

Inputs

  • to · string · Required, Destination number in e164 format
  • from · string · Optional, User ID from which call should originate
  • caller_id · string · Optional, Caller ID to use for the call. E164 number or 'anonymous'
Make a Webcall · Read

Make a webcall from e164 number to other e164 number or extension

make_awebcall · Risk: low · Retry: safe

Inputs

  • from · string · Required, Source number in e164 format
  • to · string · Required, Destination number in e164 format or extension
Send SMS · Read

Send new SMS resource

send_sms · Risk: low · Retry: safe

Inputs

  • from · string · Optional, From number in e164 format
  • to · string · Required, Destination number in e164 format
  • message · string · Required, Message to send
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

Call Connected · Webhook

Triggered when a call is connected

Inputs

  • instruction · string
Call Ended · Webhook

Triggered when a call ends or is terminated

Inputs

  • instruction · string
Call Tracking · Poll

Triggers when call associated with Call Tracking campaign visits is finished.

DTMF Received · Webhook

Triggered when a DTMF (Dual-Tone Multi-Frequency) tone is received during a call

Inputs

  • instruction · string
Missed Call · Webhook

Triggered when an incoming call is not answered (missed call)

Inputs

  • instruction · string
New Call Recording · Webhook

Triggers when a new call recording is ready for a completed call.

Inputs

  • instruction · string
SMS Received · Webhook

Triggers when an SMS message is received in VoipStudio.

Inputs

  • instruction · string

Setup

Setup

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