Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

LobsterMail

Email infrastructure for AI agents, create inboxes, send and receive email, search, threads, and webhooks.

CategoryCommunication
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect LobsterMail with Flows360

Email infrastructure for AI agents, create inboxes, send and receive email, search, threads, and webhooks.

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

Available actions

  • Create Inbox
  • Get Inbox
  • Delete Inbox
  • List Inboxes
  • Send Email
  • List Emails
  • Get Email
  • Search Emails
  • Plus 2 additional declared actions.

Available triggers

  • New Email Received
  • New Email Thread
  • Thread Reply Received
  • Email Bounced
  • Email Sent

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: LobsterMail
  • Package: @activepieces/piece-lobstermail@0.2.0
  • Exact artifact digest: sha256:581fcfc3a27dc3bcc3b96f38b1ee167f4a70a0075ba245bf6b9e749947c3f585
  • 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 Inbox (create_inbox), Create a new email inbox on LobsterMail. Classification: read.
  • Get Inbox (get_inbox), Get details for a single inbox including its address, status, and settings. Classification: read.
  • Delete Inbox (delete_inbox), Permanently delete an inbox and release its address. This action cannot be undone. Classification: read.
  • List Inboxes (list_inboxes), List all email inboxes on the account. Classification: read.
  • Send Email (send_email), Send an email from one of your LobsterMail inboxes. Requires a verified account (Tier 1+). Classification: read.
  • List Emails (list_emails), List emails in a specific inbox. Classification: read.
  • Get Email (get_email), Get a single email with full body content. Classification: read.
  • Search Emails (search_emails), Search emails across inboxes using full-text search and optional filters. Rate limited to 30 requests/minute. Classification: read.
  • Get Account (get_account), Get account details including subscription tier, usage, and sending limits. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Email Received, webhook.
  • New Email Thread, webhook.
  • Thread Reply Received, webhook.
  • Email Bounced, webhook.
  • Email Sent, 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 objects15
Supported actionsNot published
Triggers5

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Inbox Yes No Create a new email inbox on LobsterMail.
Get Inbox Yes No Get details for a single inbox including its address, status, and settings.
Delete Inbox Yes No Permanently delete an inbox and release its address. This action cannot be undone.
List Inboxes Yes No List all email inboxes on the account.
Send Email Yes No Send an email from one of your LobsterMail inboxes. Requires a verified account (Tier 1+).
List Emails Yes No List emails in a specific inbox.
Get Email Yes No Get a single email with full body content.
Search Emails Yes No Search emails across inboxes using full-text search and optional filters. Rate limited to 30 requests/minute.
Get Account Yes No Get account details including subscription tier, usage, and sending limits.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Email Received Yes No webhook trigger declared by the pinned package.
New Email Thread Yes No webhook trigger declared by the pinned package.
Thread Reply Received Yes No webhook trigger declared by the pinned package.
Email Bounced Yes No webhook trigger declared by the pinned package.
Email Sent Yes No webhook trigger declared by the pinned package.

Triggers

New Email Received · Webhook

Triggers instantly when a new email is received in an inbox.

Inputs

  • inbox_id · string
New Email Thread · Webhook

Triggers when a brand-new conversation (thread) is started in an inbox.

Inputs

  • inbox_id · string
Thread Reply Received · Webhook

Triggers when someone replies to an existing email thread. Useful for follow-up and support automation.

Inputs

  • inbox_id · string
Email Bounced · Webhook

Triggers when an outbound email fails to deliver. Use this to update CRM records, retry with a different address, or alert your team.

Inputs

  • inbox_id · string
Email Sent · Webhook

Triggers when an outbound email is successfully delivered. Use for audit logs, CRM updates, or confirming delivery.

Inputs

  • inbox_id · string

Setup

Setup

  1. Add the LobsterMail 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-lobstermail@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 10 actions and 5 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 LobsterMail 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-lobstermail@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