Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Manychat

Automations for Instagram, WhatsApp, TikTok, and Messenger marketing.

CategoryMarketing
Authenticationcustom
Version0.1.6
Published scopes0 published scopes
Last updatedSeptember 21, 2026

Overview

Connect Manychat with Flows360

Automations for Instagram, WhatsApp, TikTok, and Messenger marketing.

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

Available actions

  • Add Tag to User
  • Create Subscriber
  • Find User by Custom Field
  • Find User by Name
  • Remove Tag from User
  • Send Content to User
  • Set Custom Field

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: Manychat
  • Package: @activepieces/piece-manychat@0.1.6
  • Exact artifact digest: sha256:9cb9ba93a7d45f5060313a4ec54bbd65a576e8f37c4766076944c1af172575bd
  • 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 Tag to User (addTagToUser), Adds a tag to a user. Classification: read.
  • Create Subscriber (createSubscriber), Creates a Unified or a Whatsapp subscriber. Classification: read.
  • Find User by Custom Field (findUserByCustomField), Finds a user by custom field. Classification: read.
  • Find User by Name (findUserByName), Finds a user by name. Classification: read.
  • Remove Tag from User (removeTagFromUser), Remove a tag from a user. Classification: read.
  • Send Content to User (sendContentToUser), Sends a content to a user. Classification: read.
  • Set Custom Field (setCustomField), Ass or Updates a custom field value for a user. 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 objects7
Supported actions7
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Add Tag to User Yes No Adds a tag to a user.
Create Subscriber Yes No Creates a Unified or a Whatsapp subscriber.
Find User by Custom Field Yes No Finds a user by custom field.
Find User by Name Yes No Finds a user by name.
Remove Tag from User Yes No Remove a tag from a user.
Send Content to User Yes No Sends a content to a user.
Set Custom Field Yes No Ass or Updates a custom field value for a user.

Supported actions

Add Tag to User · Read

Adds a tag to a user.

add_tag_to_user · Risk: low · Retry: safe

Inputs

  • subscriberId · number · Required, Please refer [Manychat Guide](https://help.manychat.com/hc/en-us/articles/14959510331420-How-to-generate-a-token-for-the-Manychat-API-and-where-to-get-parameters#h_01JCR55RJ0B0PQW6HDW6RW0A42) to obtain user/contact ID.
  • tagId · string · Required
Create Subscriber · Read

Creates a Unified or a Whatsapp subscriber.

create_subscriber · Risk: low · Retry: safe

Inputs

  • first_name · string · Required
  • last_name · string · Optional
  • phone · string · Optional, Fill in at least one field: phone or email or whatsapp phone.
  • whatsapp_phone · string · Optional, Fill in at least one field: phone or email or whatsapp phone.
  • email · string · Optional, Fill in at least one field: phone or email or whatsapp phone.
  • gender · string · Optional
  • has_opt_in_sms · boolean · Optional
  • has_opt_in_email · boolean · Optional
  • consent_phrase · string · Optional, The consent phrase provided by the subscriber.
Find User by Custom Field · Read

Finds a user by custom field.

find_user_by_custom_field · Risk: low · Retry: safe

Inputs

  • field · string · Required
  • value · string · Required, The value to search for.
Find User by Name · Read

Finds a user by name.

find_user_by_name · Risk: low · Retry: safe

Inputs

  • name · string · Required, Provide user's full name to search.
Remove Tag from User · Read

Remove a tag from a user.

remove_tag_from_user · Risk: low · Retry: safe

Inputs

  • subscriberId · number · Required, Please refer [Manychat Guide](https://help.manychat.com/hc/en-us/articles/14959510331420-How-to-generate-a-token-for-the-Manychat-API-and-where-to-get-parameters#h_01JCR55RJ0B0PQW6HDW6RW0A42) to obtain user/contact ID.
  • tagId · string · Required
Send Content to User · Read

Sends a content to a user.

send_content_to_user · Risk: low · Retry: safe

Inputs

  • subscriber_id · number · Required, Please refer [Manychat Guide](https://help.manychat.com/hc/en-us/articles/14959510331420-How-to-generate-a-token-for-the-Manychat-API-and-where-to-get-parameters#h_01JCR55RJ0B0PQW6HDW6RW0A42) to obtain user/contact ID.
  • platform · string · Optional, The platform to send the content to.
  • content_type · string · Required, The type of content to send.
  • text_content · string · Optional, The text content to send. Required when content type is Text.
  • media_url · string · Optional, URL of the media to send (image, video, audio, or file). Required for media content types.
  • message_tag · string · Optional, The tag to use for the message.
Set Custom Field · Read

Ass or Updates a custom field value for a user.

set_custom_field · Risk: low · Retry: safe

Inputs

  • subscriber_id · number · Required, Please refer [Manychat Guide](https://help.manychat.com/hc/en-us/articles/14959510331420-How-to-generate-a-token-for-the-Manychat-API-and-where-to-get-parameters#h_01JCR55RJ0B0PQW6HDW6RW0A42) to obtain user/contact ID.
  • field_id · string · Required
  • field_value · object · Required

Setup

Setup

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