Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Sendy

Self-hosted email marketing software

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

Overview

Connect Sendy with Flows360

Self-hosted email marketing software

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

Available actions

  • Count Active Subscribers
  • Create Campaign
  • Delete Subscriber
  • Get Brands
  • Get Lists for a Brand
  • Get Subscription Status
  • Subscribe Updated
  • Subscribe Multiple Lists
  • Plus 2 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: Sendy
  • Package: @activepieces/piece-sendy@0.1.6
  • Exact artifact digest: sha256:272d28518f67020fb1403143db35661d7cf919f2dafa0845680700a8dd50d75d
  • 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

  • Count Active Subscribers (count_subscribers), Get the active subscriber count for a list Classification: read.
  • Create Campaign (create_campaign), Create a new campaign Classification: read.
  • Delete Subscriber (delete_subscriber), Delete a subscriber from a list Classification: read.
  • Get Brands (get_brands), Get a list of brands from Sendy Classification: read.
  • Get Lists for a Brand (get_brand_lists), Get the Lists for a Brand Classification: read.
  • Get Subscription Status (get_subscription_status), Get the subscription status of a user Classification: read.
  • Subscribe Updated (subscribe), Add a new subscriber to a list Classification: read.
  • Subscribe Multiple Lists (subscribe_multiple_lists), Add a new subscriber to a multiple lists Classification: read.
  • Unsubscribe (unsubscribe), Unsubscribe a subscriber from a list Classification: read.
  • Unsubscribe Multiple Lists (unsubscribe_multiple), Unsubscribe a subscriber from multiple lists 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 objects10
Supported actions10
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Sendy Domain Required
  • API Key Required · protected credential
  • Brand ID Required

Supported objects

ObjectReadWriteNotes
Count Active Subscribers Yes No Get the active subscriber count for a list
Create Campaign Yes No Create a new campaign
Delete Subscriber Yes No Delete a subscriber from a list
Get Brands Yes No Get a list of brands from Sendy
Get Lists for a Brand Yes No Get the Lists for a Brand
Get Subscription Status Yes No Get the subscription status of a user
Subscribe Updated Yes No Add a new subscriber to a list
Subscribe Multiple Lists Yes No Add a new subscriber to a multiple lists
Unsubscribe Yes No Unsubscribe a subscriber from a list
Unsubscribe Multiple Lists Yes No Unsubscribe a subscriber from multiple lists

Supported actions

Count Active Subscribers · Read

Get the active subscriber count for a list

count_subscribers · Risk: low · Retry: safe

Inputs

  • list · string · Required, Select the list to get the status from
Create Campaign · Read

Create a new campaign

create_campaign · Risk: low · Retry: safe

Inputs

  • fromEmail · string · Required, The email address the campaign will be sent from
  • fromName · string · Required, The name the campaign will be sent from
  • replyTo · string · Required, The email address that will be used for replies
  • title · string · Required, The title of the campaign
  • subject · string · Required, The subject of the campaign email
  • plainText · string · Optional, The plain text version of the campaign email
  • html · string · Required, The HTML version of the campaign email
  • lists · array · Optional, Select lists to send the campaign to
  • excludeLists · array · Optional, Select lists to exclude from the campaign send
  • segments · string · Optional, Comma separated list of segment IDs to send the campaign to
  • excludeSegments · string · Optional, Comma separated list of segment IDs to exclude from the campaign send
  • queryString · string · Optional, The query string to append to the campaign URL
  • trackOpens · string · Required, Enable open tracking
  • trackClicks · string · Required, Enable click tracking
  • autoSend · boolean · Optional, Automatically send the campaign after creation
  • schedule · string · Optional, Schedule the campaign to be sent at a specific date and time. Date/time format: 2023-06-09T12:00:00Z
  • timezone · string · Optional, The timezone to use for the schedule
Delete Subscriber · Read

Delete a subscriber from a list

delete_subscriber · Risk: low · Retry: safe

Inputs

  • list · string · Required, Select the list to delete from
  • email · string · Required, The user's email
Get Brands · Read

Get a list of brands from Sendy

get_brands · Risk: low · Retry: safe

Get Lists for a Brand · Read

Get the Lists for a Brand

get_brand_lists · Risk: low · Retry: safe

Inputs

  • includeHidden · boolean · Optional, Include hidden lists in the results
Get Subscription Status · Read

Get the subscription status of a user

get_subscription_status · Risk: low · Retry: safe

Inputs

  • list · string · Required, Select the list to get the status from
  • email · string · Required, The user's email
Subscribe Updated · Read

Add a new subscriber to a list

subscribe · Risk: low · Retry: safe

Inputs

  • list · string · Required, Select the list to subscribe to
  • email · string · Required, The user's email
  • name · string · Optional, The user's name
  • country · string · Optional, The user's 2 letter country code
  • ipaddress · string · Optional, The user's IP address
  • referrer · string · Optional, The URL where the user signed up from
  • gdpr · boolean · Optional, If you're signing up EU users in a GDPR compliant manner, set to true
  • silent · boolean · Optional, set to true if your list is 'Double opt-in' but you want to bypass that and signup the user to the list as 'Single Opt-in instead'
Subscribe Multiple Lists · Read

Add a new subscriber to a multiple lists

subscribe_multiple_lists · Risk: low · Retry: safe

Inputs

  • lists · array · Required, Select the lists to subscribe to
  • email · string · Required, The user's email
  • name · string · Optional, The user's name
  • country · string · Optional, The user's 2 letter country code
  • ipaddress · string · Optional, The user's IP address
  • referrer · string · Optional, The URL where the user signed up from
  • gdpr · boolean · Optional, If you're signing up EU users in a GDPR compliant manner, set to true
  • silent · boolean · Optional, set to true if your list is 'Double opt-in' but you want to bypass that and signup the user to the list as 'Single Opt-in instead'
Unsubscribe · Read

Unsubscribe a subscriber from a list

unsubscribe · Risk: low · Retry: safe

Inputs

  • list · string · Required, Select the list to unsubscribe from
  • email · string · Required, The user's email
Unsubscribe Multiple Lists · Read

Unsubscribe a subscriber from multiple lists

unsubscribe_multiple · Risk: low · Retry: safe

Inputs

  • lists · array · Required, Select the lists to subscribe to
  • email · string · Required, The user's email

Setup

Setup

  1. Add the Sendy 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:
  • Sendy Domain (domain), required.
  • API Key (apiKey), required; stored as a sensitive connection value.
  • Brand ID (brandId), 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-sendy@0.1.6; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 10 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 Sendy 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-sendy@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