Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Sender

Sender integration for Flows360 workflows.

CategoryMarketing
Authenticationcustom
Version0.1.7
Published scopes0 published scopes
Last updatedSeptember 23, 2026

Overview

Connect Sender with Flows360

Sender integration for Flows360 workflows.

Use the Sender 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 7 triggers.

Available actions

  • Add / Update Subscriber
  • Create Campaign
  • Unsubscribe Subscriber
  • Add Subscriber to Group
  • Remove Subscriber from Group
  • Send Campaign
  • Update Subscriber

Available triggers

  • New Campaign
  • New Group
  • New Subscriber
  • New Subscriber in Group
  • Updated Subscriber
  • New Unsubscriber
  • Plus 1 additional declared trigger.

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: Sender
  • Package: @activepieces/piece-sender@0.1.7
  • Exact artifact digest: sha256:41ac7d6a4d383f81ab30c3d610911c5af9c9dbfdbd0cc40fb02797a039ce6255
  • 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 / Update Subscriber (add_update_subscriber), Add a new subscriber or update existing subscriber's data Classification: read.
  • Create Campaign (create_campaign), Creates a draft campaign in Sender Classification: read.
  • Unsubscribe Subscriber (unsubscribe_subscriber), Mark an email address as unsubscribed globally or from a group Classification: read.
  • Add Subscriber to Group (add_subscriber_to_group), Add an existing or new subscriber into one or more groups Classification: read.
  • Remove Subscriber from Group (remove_subscriber_from_group), Remove a subscriber from a specific group Classification: read.
  • Send Campaign (send_campaign), Trigger sending of a drafted campaign to its recipient list Classification: read.
  • Update Subscriber (update_subscriber), Update an existing subscriber's data Classification: read.

Trigger contracts

  • New Campaign, webhook.
  • New Group, webhook.
  • New Subscriber, webhook.
  • New Subscriber in Group, webhook.
  • Updated Subscriber, webhook.
  • New Unsubscriber, webhook.
  • New Unsubscriber From Group, webhook.

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
Triggers7

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Token Required · protected credential

Supported objects

ObjectReadWriteNotes
Add / Update Subscriber Yes No Add a new subscriber or update existing subscriber's data
Create Campaign Yes No Creates a draft campaign in Sender
Unsubscribe Subscriber Yes No Mark an email address as unsubscribed globally or from a group
Add Subscriber to Group Yes No Add an existing or new subscriber into one or more groups
Remove Subscriber from Group Yes No Remove a subscriber from a specific group
Send Campaign Yes No Trigger sending of a drafted campaign to its recipient list
Update Subscriber Yes No Update an existing subscriber's data
New Campaign Yes No webhook trigger declared by the pinned package.
New Group Yes No webhook trigger declared by the pinned package.
New Subscriber Yes No webhook trigger declared by the pinned package.
New Subscriber in Group Yes No webhook trigger declared by the pinned package.
Updated Subscriber Yes No webhook trigger declared by the pinned package.
New Unsubscriber Yes No webhook trigger declared by the pinned package.
New Unsubscriber From Group Yes No webhook trigger declared by the pinned package.

Triggers

New Campaign · Webhook

Fires when a new campaign is created in Sender

New Group · Webhook

Fires when a new group/list is created

New Subscriber · Webhook

Fires when a subscriber is added to any group or to account

New Subscriber in Group · Webhook

Fires when a subscriber is added to a specific group/list

Inputs

  • groupId · string
Updated Subscriber · Webhook

Fires when a subscriber's data (fields) is updated

New Unsubscriber · Webhook

Fires when someone unsubscribes globally

New Unsubscriber From Group · Webhook

Fires when a subscriber is removed/unsubscribed from a specific group

Inputs

  • groupId · string

Setup

Setup

  1. Add the Sender 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-sender@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 7 actions and 7 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 Sender 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-sender@0.1.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