Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Autocalls

Automate phone calls using our AI calling platform.

CategoryOther
Authenticationcustom
Version0.1.7
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Autocalls with Flows360

Automate phone calls using our AI calling platform.

Use the Autocalls 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 5 actions and 3 triggers.

Available actions

  • Add lead to a campaign
  • Send SMS to Customer
  • Start/Stop Campaign
  • Make Phone Call
  • Delete Lead

Available triggers

  • Phone Call Ended
  • Updated Assistant
  • Inbound Call

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: Autocalls
  • Package: @activepieces/piece-autocalls@0.1.7
  • Exact artifact digest: sha256:3ab9d7fe3517acb692481b060343bb8c672960676c2c6744d5ce82f461df5260
  • 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

  • Add lead to a campaign (addLead), Add lead to an outbound campaign, to be called by an assistant from our platform. Classification: read.
  • Send SMS to Customer (sendSms), Send an SMS to a customer using a phone number from our platform. Classification: read.
  • Start/Stop Campaign (campaignControl), Start or stop an outbound campaign from our platform. Classification: read.
  • Make Phone Call (makePhoneCall), Call a customer by it's phone number using an assistant from our platform. Classification: read.
  • Delete Lead (deleteLead), Delete a lead from a campaign. Classification: read.

Trigger contracts

  • Phone Call Ended, webhook.
  • Updated Assistant, polling.
  • Inbound Call, 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 objects8
Supported actions5
Triggers3

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Add lead to a campaign Yes No Add lead to an outbound campaign, to be called by an assistant from our platform.
Send SMS to Customer Yes No Send an SMS to a customer using a phone number from our platform.
Start/Stop Campaign Yes No Start or stop an outbound campaign from our platform.
Make Phone Call Yes No Call a customer by it's phone number using an assistant from our platform.
Delete Lead Yes No Delete a lead from a campaign.
Phone Call Ended Yes No webhook trigger declared by the pinned package.
Updated Assistant Yes No polling trigger declared by the pinned package.
Inbound Call Yes No webhook trigger declared by the pinned package.

Supported actions

Add lead to a campaign · Read

Add lead to an outbound campaign, to be called by an assistant from our platform.

add_lead · Risk: low · Retry: safe

Inputs

  • campaign · string · Required, Select a campaign
  • phone_number · string · Required, Enter the phone number of the customer
  • variables · object · Required, Variables to pass to the assistant
  • allow_dupplicate · boolean · Required, Allow the same phone number to be added to the campaign more than once
  • num_secondary_contacts · number · Optional, How many secondary contacts do you want to add?
  • secondary_contacts · object · Optional, Add secondary contacts for this lead. Each contact can have its own phone number and variables.
Send SMS to Customer · Read

Send an SMS to a customer using a phone number from our platform.

send_sms · Risk: low · Retry: safe

Inputs

  • from · string · Required, Select an SMS capable phone number to send the SMS from
  • to · string · Required, Enter the phone number of the customer
  • body · string · Required, Enter the text message to send to the customer (max 300 characters)
Start/Stop Campaign · Read

Start or stop an outbound campaign from our platform.

campaign_control · Risk: low · Retry: safe

Inputs

  • campaign · string · Required, Select a campaign
  • action · string · Required, Select action to perform on the campaign
Make Phone Call · Read

Call a customer by it's phone number using an assistant from our platform.

make_phone_call · Risk: low · Retry: safe

Inputs

  • assistant · string · Required, Select an assistant
  • phone_number · string · Required, Enter the phone number of the customer
  • variables · object · Required, Variables to pass to the assistant
Delete Lead · Read

Delete a lead from a campaign.

delete_lead · Risk: low · Retry: safe

Inputs

  • lead · string · Required, Select a lead to delete

Triggers

Phone Call Ended · Webhook

Triggers when a phone call ends, with extracted variables.

Inputs

  • assistant · string
Updated Assistant · Poll

Triggers when assistants are fetched or updated in your Autocalls account.

Inputs

  • start · string
  • end · string
Inbound Call · Webhook

Triggers for variables before connecting an inbound call.

Inputs

  • assistant · string

Setup

Setup

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