Overview
Connect Twilio with Flows360
Send and receive SMS, voice, video and WhatsApp communications through workflows.
Use the Twilio 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 5 triggers.
Available actions
- Send SMS
- Phone Number Lookup
- Call Phone
- Get Message
- Download Recording Media
- Custom API Call
Available triggers
- New Incoming SMS
- New Phone Number
- New Recording
- New Transcription
- New 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: Twilio
- Package:
@activepieces/piece-twilio@0.5.0 - Exact artifact digest:
sha256:51045ba20e430eed5a2076caadeccf071652d260252804277c1272e18093659d - Runtime: Activepieces-compatible deterministic worker
- Source: the exact reviewed Activepieces source
Authentication
BASIC AUTH. 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 SMS (
send_sms), Send a new SMS message Classification: read. - Phone Number Lookup (
phone_number_lookup), Lookup information about a phone number. Classification: read. - Call Phone (
make_call), Call a number and say a message. Classification: read. - Get Message (
get_message), Retrieves the details of a specific message. Classification: read. - Download Recording Media (
download_recording_media), Download the media file for a specific recording. Classification: read. - Custom API Call (
custom_api_call), Make a custom API call to a specific endpoint Classification: read.
Trigger contracts
- New Incoming SMS, polling.
- New Phone Number, polling.
- New Recording, polling.
- New Transcription, polling.
- New Call, polling.
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: basic
Authentication profiles
connection · basic
- Username Required
- Password Required · protected credential
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Send SMS | Yes | No | Send a new SMS message |
| Phone Number Lookup | Yes | No | Lookup information about a phone number. |
| Call Phone | Yes | No | Call a number and say a message. |
| Get Message | Yes | No | Retrieves the details of a specific message. |
| Download Recording Media | Yes | No | Download the media file for a specific recording. |
| Custom API Call | Yes | No | Make a custom API call to a specific endpoint |
| New Incoming SMS | Yes | No | polling trigger declared by the pinned package. |
| New Phone Number | Yes | No | polling trigger declared by the pinned package. |
| New Recording | Yes | No | polling trigger declared by the pinned package. |
| New Transcription | Yes | No | polling trigger declared by the pinned package. |
| New Call | Yes | No | polling trigger declared by the pinned package. |
Triggers
New Incoming SMS · Poll
Triggers when a new SMS message is received
Inputs
phone_number· string
New Phone Number · Poll
Triggers when you add a new phone number to your account.
New Recording · Poll
Triggers when a new call recording is completed and available.
New Transcription · Poll
Triggers when a new call recording transcription is completed.
New Call · Poll
Triggers when a call completes (incoming or outgoing).
Setup
Setup
- Add the Twilio connector to the workflow in the target Flows360 Studio instance.
- 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.
- Provide the connection fields declared by the pinned package:
- No provider credential fields are declared by the pinned package.
- Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
- Test the workflow in the appropriate environment before enabling production scheduling or event delivery.
Limitations
Limitations and operational notes
- This content describes
@activepieces/piece-twilio@0.5.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes. - Only the 6 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
Why canu2019t the connector authenticate?
Check the tenant connection in Studio and confirm every required Twilio 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-twilio@0.5.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.