Kapso

Overview

Connect Kapso with Flows360

Send and receive WhatsApp messages, media, templates, and more using the Kapso WhatsApp API.

Use the Kapso 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 15 actions and 2 triggers.

Available actions

• Send Text Message
• Send Button Message
• Send List Message
• Send Image
• Send Video
• Send Audio
• Send Document
• Send Sticker
• Plus 7 additional declared actions.

Available triggers

• New Message Received
• Message Status Update

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: Kapso
• Package: @activepieces/piece-kapso@0.2.0
• Exact artifact digest: sha256:bcff3315e7b30056767485af4dfe6ae26562ca6c07811006c030e1c907ced411
• 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

• Send Text Message (send_text_message), Send a text message via WhatsApp. Classification: read.
• Send Button Message (send_buttons), Send an interactive button message via WhatsApp (up to 3 buttons). Classification: read.
• Send List Message (send_list_message), Send an interactive list message via WhatsApp. Classification: read.
• Send Image (send_image), Send an image message via WhatsApp. Classification: read.
• Send Video (send_video), Send a video message via WhatsApp. Classification: read.
• Send Audio (send_audio), Send an audio message via WhatsApp. Classification: read.
• Send Document (send_document), Send a document message via WhatsApp. Classification: read.
• Send Sticker (send_sticker), Send a sticker message via WhatsApp. Classification: read.
• Send Location (send_location), Send a location message via WhatsApp. Classification: read.
• Request User Location (request_user_location), Send a location request message to a WhatsApp user. Classification: read.
• Send Contact (send_contact), Send a contact card via WhatsApp. Classification: read.
• Send Reaction (send_reaction), React to a WhatsApp message with an emoji. Classification: read.
• Mark Message as Read (mark_as_read), Mark a WhatsApp message as read. Classification: read.
• Send Template Message (send_template_message), Send a pre-approved WhatsApp template message. Classification: read.
• Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

• New Message Received, webhook.
• Message Status Update, webhook.

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: custom

Authentication profiles

Supported objects

Triggers

Setup

Setup

1. Add the Kapso 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-kapso@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
• Only the 15 actions and 2 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

Related documentation