Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Zagomail

All-in-one email marketing and automation platform

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

Overview

Connect Zagomail with Flows360

All-in-one email marketing and automation platform

Use the Zagomail 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

  • Create Subscriber
  • Tag Subscriber
  • Update Subscriber
  • Search Subscriber
  • Get Subscriber
  • Get Campaign

Available triggers

  • Subscriber Added
  • Unsubscribed Subscriber
  • Tagged 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: Zagomail
  • Package: @activepieces/piece-zagomail@0.1.6
  • Exact artifact digest: sha256:e819d998e1f43e50e2d14c4894c035199ec26052b9af985b349f096483b38d53
  • 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

  • Create Subscriber (createSubscriber), Creates a new subscriber in a list. Classification: read.
  • Tag Subscriber (tagSubscriber), Adds A Tag to A Subscriber. Classification: read.
  • Update Subscriber (updateSubscriber), Updates an existing subscriber. Classification: read.
  • Search Subscriber (searchSubscriberByEmail), Finds a subscriber by their email address. Classification: read.
  • Get Subscriber (getSubscriberDetails), Gets the details of a subscriber. Classification: read.
  • Get Campaign (getCampaignDetails), Gets the details of a campaign. Classification: read.

Trigger contracts

  • Subscriber Added, webhook.
  • Unsubscribed Subscriber, webhook.
  • Tagged Subscriber, 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 objects9
Supported actions6
Triggers3

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Application Public Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Subscriber Yes No Creates a new subscriber in a list.
Tag Subscriber Yes No Adds A Tag to A Subscriber.
Update Subscriber Yes No Updates an existing subscriber.
Search Subscriber Yes No Finds a subscriber by their email address.
Get Subscriber Yes No Gets the details of a subscriber.
Get Campaign Yes No Gets the details of a campaign.
Subscriber Added Yes No webhook trigger declared by the pinned package.
Unsubscribed Subscriber Yes No webhook trigger declared by the pinned package.
Tagged Subscriber Yes No webhook trigger declared by the pinned package.

Supported actions

Create Subscriber · Read

Creates a new subscriber in a list.

create_subscriber · Risk: low · Retry: safe

Inputs

  • listUId · string · Required
  • fields · object · Required
Tag Subscriber · Read

Adds A Tag to A Subscriber.

tag_subscriber · Risk: low · Retry: safe

Inputs

  • tags · array · Required, Add one or more tags you would like to add to this subscriber.
  • listUId · string · Required
  • subscriberUid · string · Required, The ID of the subscriber you want to add the tag to.
Update Subscriber · Read

Updates an existing subscriber.

update_subscriber · Risk: low · Retry: safe

Inputs

  • listUId · string · Required
  • subsriberUid · string · Required, The ID of the subscriber you want to update.
  • fields · object · Required
Search Subscriber · Read

Finds a subscriber by their email address.

search_subscriber_by_email · Risk: low · Retry: safe

Inputs

  • listUId · string · Required
  • email · string · Required
Get Subscriber · Read

Gets the details of a subscriber.

get_subscriber_details · Risk: low · Retry: safe

Inputs

  • listUId · string · Required
  • subscriberUid · string · Required, The ID of the subscriber you want to get the details for.
Get Campaign · Read

Gets the details of a campaign.

get_campaign_details · Risk: low · Retry: safe

Inputs

  • campaignUid · string · Required

Triggers

Subscriber Added · Webhook

Triggers when subscriber is signed up or confirmed.

Unsubscribed Subscriber · Webhook

Triggers when subscriber is unsubscribed.

Tagged Subscriber · Webhook

Trigers when subscriber is tagged with a tag.

Inputs

  • tagName · string

Setup

Setup

  1. Add the Zagomail 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-zagomail@0.1.6; 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.
  • 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 Zagomail 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-zagomail@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