Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

SendPulse

SendPulse integration for Flows360 workflows.

CategoryOther
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 30, 2026

Overview

Connect SendPulse with Flows360

SendPulse integration for Flows360 workflows.

Use the SendPulse 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 6 actions and 3 triggers.

Available actions

  • Add Subscriber
  • Change Variable for Subscriber
  • Delete Contact
  • Unsubscribe User
  • Update Subscriber
  • Custom API Call

Available triggers

  • New Subscriber
  • New Unsubscriber
  • Updated Subscriber

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: SendPulse
  • Package: @activepieces/piece-sendpulse@0.2.0
  • Exact artifact digest: sha256:90094468dbf151efd19385a5ae9c4ed5bf11c7b66a657eb2b2464a9ec84df642
  • 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

  • Add Subscriber (add-subscriber), Add subscriber to mailing list Classification: read.
  • Change Variable for Subscriber (change-variable-for-subscriber), Update subscriber variable Classification: read.
  • Delete Contact (delete-contact), Permanently delete contact from all mailing lists Classification: read.
  • Unsubscribe User (unsubscribe-user), Remove subscribers from mailing list Classification: read.
  • Update Subscriber (update-subscriber), Update subscriber details and variables Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Subscriber, webhook.
  • New Unsubscriber, webhook.
  • Updated Subscriber, polling.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects9
Supported actions6
Triggers3

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Client ID Required · protected credential
  • Client Secret Required · protected credential

Supported objects

ObjectReadWriteNotes
Add Subscriber Yes No Add subscriber to mailing list
Change Variable for Subscriber Yes No Update subscriber variable
Delete Contact Yes No Permanently delete contact from all mailing lists
Unsubscribe User Yes No Remove subscribers from mailing list
Update Subscriber Yes No Update subscriber details and variables
Custom API Call Yes No Make a custom API call to a specific endpoint
New Subscriber Yes No webhook trigger declared by the pinned package.
New Unsubscriber Yes No webhook trigger declared by the pinned package.
Updated Subscriber Yes No polling trigger declared by the pinned package.

Supported actions

Add Subscriber · Read

Add subscriber to mailing list

add_subscriber · Risk: low · Retry: safe

Inputs

  • mailingListId · string · Required, Select one of your SendPulse mailing lists
  • email · string · Required, Subscriber email address
  • variables · object · Optional, Optional subscriber variables (e.g., name, phone)
  • tags · array · Optional, Optional tag IDs to assign
Change Variable for Subscriber · Read

Update subscriber variable

change_variable_for_subscriber · Risk: low · Retry: safe

Inputs

  • mailingListId · string · Required, Select one of your SendPulse mailing lists
  • email · string · Required, Subscriber email address
  • variableName · string · Required, Select variable to update
  • variableValue · string · Required, New value for the variable
Delete Contact · Read

Permanently delete contact from all mailing lists

delete_contact · Risk: low · Retry: safe

Inputs

  • email · string · Required, Email address to delete from all mailing lists
Unsubscribe User · Read

Remove subscribers from mailing list

unsubscribe_user · Risk: low · Retry: safe

Inputs

  • mailingListId · string · Required, Select one of your SendPulse mailing lists
  • emails · array · Required, Email addresses to unsubscribe (max 100)
Update Subscriber · Read

Update subscriber details and variables

update_subscriber · Risk: low · Retry: safe

Inputs

  • mailingListId · string · Required, Select one of your SendPulse mailing lists
  • email · string · Required, Email address of the subscriber to update
  • phone · string · Optional, New phone number (optional)
  • variables · object · Optional, Subscriber variables to update (e.g., name, custom fields)
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Subscriber · Webhook

Fires when new subscriber is added

Inputs

  • mailingListId · string
New Unsubscriber · Webhook

Fires when subscriber unsubscribes

Inputs

  • mailingListId · string
Updated Subscriber · Poll

Fires when subscriber details change (polling)

Inputs

  • mailingListId · string

Setup

Setup

  1. Add the SendPulse 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:
  • Client ID (clientId), required; stored as a sensitive connection value.
  • Client Secret (clientSecret), 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-sendpulse@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 3 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.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required SendPulse 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-sendpulse@0.2.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