Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

WhatsApp Business

Manage your WhatsApp business account

CategoryOther
Authenticationcustom
Version0.2.7
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect WhatsApp Business with Flows360

Manage your WhatsApp business account

Use the WhatsApp Business 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 3 actions and no declared triggers.

Available actions

  • Send Message
  • Send Media
  • Send Template Message

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: WhatsApp Business
  • Package: @activepieces/piece-whatsapp@0.2.7
  • Exact artifact digest: sha256:bc65876d5b77bcb22bfa1d09dc42c96e73a17cfe77afda93e9b928032bb9ddb2
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM 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 Message (sendMessage), Send a text message through WhatsApp Classification: read.
  • Send Media (sendMedia), Send a media message through WhatsApp Classification: read.
  • Send Template Message (send-template-message), Sends a template message. 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 objects3
Supported actions3
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • System User Access Token Required · protected credential
  • Business Account ID Required

Supported objects

ObjectReadWriteNotes
Send Message Yes No Send a text message through WhatsApp
Send Media Yes No Send a media message through WhatsApp
Send Template Message Yes No Sends a template message.

Supported actions

Send Message · Read

Send a text message through WhatsApp

send_message · Risk: low · Retry: safe

Inputs

  • phone_number_id · string · Required, Phone number ID that will be used to send the message.
  • to · string · Required, The recipient of the message
  • text · string · Required, The message to send
Send Media · Read

Send a media message through WhatsApp

send_media · Risk: low · Retry: safe

Inputs

  • phone_number_id · string · Required, Phone number ID that will be used to send the message.
  • to · string · Required, The recipient of the message
  • type · string · Required, The type of media to send
  • media · string · Required, The URL of the media to send
  • caption · string · Optional, A caption for the media
  • filename · string · Optional, Filename of the document to send
Send Template Message · Read

Sends a template message.

send_template_message · Risk: low · Retry: safe

Inputs

  • phone_number_id · string · Required, Phone number ID that will be used to send the message.
  • to · string · Required, Recipient phone number.
  • message_template_id · string · Required
  • message_template_fields · object · Required

Setup

Setup

  1. Add the WhatsApp Business 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:
  • System User Access Token (access_token), required; stored as a sensitive connection value.
  • Business Account ID (businessAccountId), required.
  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-whatsapp@0.2.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 3 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 WhatsApp Business 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-whatsapp@0.2.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