Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Talkable

Referral marketing programs that drive revenue

CategoryMarketing
Authenticationcustom
Version0.3.0
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect Talkable with Flows360

Referral marketing programs that drive revenue

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

Available actions

  • Find person
  • Find coupon
  • Update person
  • Anonymize person
  • Unsubscribe person
  • Create purchase
  • Create batch of purchases
  • Create event
  • Plus 6 additional declared actions.

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: Talkable
  • Package: @activepieces/piece-talkable@0.3.0
  • Exact artifact digest: sha256:69f4c922d8345972c6aa85386b203e4efbea11713a86bb7f2eb25778798dccd6
  • 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

  • Find person (find_person), Find person by email Classification: read.
  • Find coupon (find_coupon), Find coupon code Classification: read.
  • Update person (update_person), Update person by email Classification: read.
  • Anonymize person (anonymize_person), Anonymize person by email Classification: read.
  • Unsubscribe person (unsubscribe_person), Unsubscribe person by email Classification: read.
  • Create purchase (create_purchase), Create purchase in Talkable Classification: read.
  • Create batch of purchases (create_purchases_batch), Create batch of purchases in Talkable Classification: read.
  • Create event (create_event), Create event in Talkable Classification: read.
  • Create batch of events (create_events_batch), Create batch of events in Talkable Classification: read.
  • Refund purchase/event (refund), Mark origin as refund Classification: read.
  • Get loyalty actions (get_loyalty_redeem_actions), Get array of loyalty actions Classification: read.
  • Update referral status (update-referral-status), You can void or approve referral Classification: read.
  • Share and claim offer (claim-offer), Using this action, you can share and get a friend's reward Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint 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 objects14
Supported actionsNot published
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Talkable site ID Required
  • API key Required · protected credential

Supported objects

ObjectReadWriteNotes
Find person Yes No Find person by email
Find coupon Yes No Find coupon code
Update person Yes No Update person by email
Anonymize person Yes No Anonymize person by email
Unsubscribe person Yes No Unsubscribe person by email
Create purchase Yes No Create purchase in Talkable
Create batch of purchases Yes No Create batch of purchases in Talkable
Create event Yes No Create event in Talkable
Create batch of events Yes No Create batch of events in Talkable
Refund purchase/event Yes No Mark origin as refund
Get loyalty actions Yes No Get array of loyalty actions
Update referral status Yes No You can void or approve referral
Share and claim offer Yes No Using this action, you can share and get a friend's reward
Custom API Call Yes No Make a custom API call to a specific endpoint

Setup

Setup

  1. Add the Talkable 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:
  • Talkable site ID (site), required.
  • API key (api_key), required; stored as a sensitive connection value.
  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-talkable@0.3.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 14 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 Talkable 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-talkable@0.3.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.

github.com