Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Mailchain

Mailchain is a simple, secure, and decentralized communications protocol that enables blockchain-based email.

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

Overview

Connect Mailchain with Flows360

Mailchain is a simple, secure, and decentralized communications protocol that enables blockchain-based email.

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

Available actions

  • Get Authenticated User
  • Send Email

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: Mailchain
  • Package: @activepieces/piece-mailchain@0.1.6
  • Exact artifact digest: sha256:19921caaf4d702c2c00e7c2800fa3aa6c634c270e60d06516ff2258d35e2328e
  • 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

  • Get Authenticated User (getAuthenticatedUser), Get the authenticated user to the Mailchain Protocol Classification: read.
  • Send Email (sendEmail), Send an email to blockchain or mailchain addresses Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects2
Supported actions2
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Secret Recovery Phrase Required · protected credential

Supported objects

ObjectReadWriteNotes
Get Authenticated User Yes No Get the authenticated user to the Mailchain Protocol
Send Email Yes No Send an email to blockchain or mailchain addresses

Supported actions

Get Authenticated User · Read

Get the authenticated user to the Mailchain Protocol

get_authenticated_user · Risk: low · Retry: safe

Send Email · Read

Send an email to blockchain or mailchain addresses

send_email · Risk: low · Retry: safe

Inputs

  • markdown · string · Optional, **Getting Started with Mailchain:**nnTo send emails using the Mailchain Protocol, you need to first create an account on [Mailchain](https://app.mailchain.com/). Once your account is set up, you will receive a Mailchain address. You can also connect your wallet to associate a blockchain address with your Mailchain account.nn**Recipients:**nnWhen sending an email, you can use either a Mailchain address or a blockchain address as the recipient. For blockchain addresses, you can leverage supported web3 domain services, including ENS, Unstoppable Domains, Lens, Coinbase, and many more.nn**Example Usage:**n- **Mailchain Address:** 'yourname@mailchain.com'n- **Blockchain Address:** 'yourname.eth' (ENS), 'yourname.crypto' (Unstoppable Domains), etc.nnTo manage your inbox and send emails, visit [Mailchain's Web App](https://app.mailchain.com/).n
  • to · array · Required, The blockchain or mailchain addresses to send the email to
  • subject · string · Required, The subject of the email
  • content · string · Required, The content of the email

Setup

Setup

  1. Add the Mailchain 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-mailchain@0.1.6; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 2 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.
  • 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 Mailchain 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-mailchain@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