Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Vapi

AI voice agent platform. Create outbound calls, manage assistants, and retrieve call details.

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

Overview

Connect Vapi with Flows360

AI voice agent platform. Create outbound calls, manage assistants, and retrieve call details.

Use the Vapi 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 no declared triggers.

Available actions

  • Create Call
  • Get Call
  • Update Assistant
  • Custom API Call

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: Vapi
  • Package: @activepieces/piece-vapi@0.1.0
  • Exact artifact digest: sha256:97d335fe3f29953c8c0085d5c5290784762e011e256521b1b9fb134a96486324
  • 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 Call (create_call), Create an outbound phone call using a Vapi assistant. Classification: read.
  • Get Call (get_call), Retrieve the details of a specific call by its ID. Classification: read.
  • Update Assistant (update_assistant), Update an existing Vapi assistant configuration (name, model, first message, etc.). 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

Authenticationcustom
Supported objects4
Supported actions4
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Call Yes No Create an outbound phone call using a Vapi assistant.
Get Call Yes No Retrieve the details of a specific call by its ID.
Update Assistant Yes No Update an existing Vapi assistant configuration (name, model, first message, etc.).
Custom API Call Yes No Make a custom API call to a specific endpoint

Supported actions

Create Call · Read

Create an outbound phone call using a Vapi assistant.

create_call · Risk: low · Retry: safe

Inputs

  • assistantId · string · Required, The ID of the Vapi assistant that will handle the call. Get this from your Vapi Dashboard.
  • phoneNumberId · string · Required, The ID of the phone number to make the call from. Must be a number registered in your Vapi account.
  • customerNumber · string · Required, The phone number to call, in E.164 format (e.g. +14155551234).
  • name · string · Optional, An optional name for this call for identification.
  • assistantOverrides · object · Optional, Optional JSON object with assistant configuration overrides for this call (e.g. first message, model settings).
Get Call · Read

Retrieve the details of a specific call by its ID.

get_call · Risk: low · Retry: safe

Inputs

  • callId · string · Required, The unique identifier of the call to retrieve.
Update Assistant · Read

Update an existing Vapi assistant configuration (name, model, first message, etc.).

update_assistant · Risk: low · Retry: safe

Inputs

  • assistantId · string · Required, The unique identifier of the assistant to update.
  • name · string · Optional, A new name for the assistant.
  • firstMessage · string · Optional, The first message the assistant will say when a call starts.
  • instructions · string · Optional, Optional system prompt. Vapi does not expose a standalone top-level instructions field on UpdateAssistantDto, so if you provide this you must also provide both Model and Provider so the system prompt can be applied via model.messages without discarding your input silently.
  • model · string · Optional, Optional model name (e.g. gpt-4o). Required if updating model config.
  • provider · string · Optional, Optional model provider (e.g. openai). Required if updating model config.
  • endCallMessage · string · Optional, The message the assistant says before ending the call.
  • overrides · object · Optional, Optional JSON object with additional UpdateAssistantDTO fields (e.g. model, voice, transcriber settings).
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.

Setup

Setup

  1. Add the Vapi 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-vapi@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 4 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

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Vapi 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-vapi@0.1.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.

github.com