Skip to content
← Back to documentation
Technical Reference

IMAP

Receive new email trigger

CategoryBusiness Intelligence
Authenticationcustom
Version0.4.9
Published scopes0 published scopes
Last updatedSeptember 30, 2026

Overview

Connect IMAP with Flows360

Receive new email trigger

Use the IMAP 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 4 actions and 1 trigger.

Available actions

  • Mark Email as Read/Unread
  • Copy Email
  • Move Email
  • Delete Email

Available triggers

  • New Email

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: IMAP
  • Package: @activepieces/piece-imap@0.4.9
  • Exact artifact digest: sha256:490357b6b9b9853edd9a4e0d70a72be8e49ac78dca32f20a8a1bfe3ec66a64ba
  • 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

  • Mark Email as Read/Unread (mark_email_read), Sets the read status of an email Classification: read.
  • Copy Email (copy_email), Copy an email to another mailbox Classification: read.
  • Move Email (move_email), Move an email to another mailbox Classification: read.
  • Delete Email (delete_email), Permanently delete an email Classification: read.

Trigger contracts

  • New Email, polling.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects5
Supported actions4
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Host Required
  • Username Required
  • Password Required · protected credential
  • Port Required
  • Use TLS Required
  • Validate TLS Certificates Required

Supported objects

ObjectReadWriteNotes
Mark Email as Read/Unread Yes No Sets the read status of an email
Copy Email Yes No Copy an email to another mailbox
Move Email Yes No Move an email to another mailbox
Delete Email Yes No Permanently delete an email
New Email Yes No polling trigger declared by the pinned package.

Supported actions

Mark Email as Read/Unread · Read

Sets the read status of an email

mark_email_read · Risk: low · Retry: safe

Inputs

  • mailbox · string · Required, Select the parent folder containing the email.
  • uid · number · Required, The UID of the email to mark.
  • markAsRead · boolean · Optional, Check to mark as read, uncheck to mark as unread.
Copy Email · Read

Copy an email to another mailbox

copy_email · Risk: low · Retry: safe

Inputs

  • sourceMailbox · string · Required, Folder to copy the email from.
  • uid · number · Required, The UID of the email to copy.
  • targetMailbox · string · Required, Folder to copy the email to.
Move Email · Read

Move an email to another mailbox

move_email · Risk: low · Retry: safe

Inputs

  • sourceMailbox · string · Required, Folder to move the email from.
  • uid · number · Required, The UID of the email to move.
  • targetMailbox · string · Required, Destination folder for the email.
Delete Email · Read

Permanently delete an email

delete_email · Risk: low · Retry: safe

Inputs

  • mailbox · string · Required, Folder to delete the email from.
  • uid · number · Required, The UID of the email to delete.
  • permanentDeletionNotice · string · Optional, n**Permanent Deletion:**nnThis action permanently deletes the email. This action cannot be undone. To move an email to the Trash folder, use the Move Email action instead.n

Triggers

New Email · Poll

Trigger when a new email is received

Inputs

  • mailbox · string
  • filterInstructions · string

Setup

Setup

  1. Add the IMAP 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:
  • Host (host), required.
  • Username (username), required.
  • Password (password), required; stored as a sensitive connection value.
  • Port (port), required.
  • Use TLS (tls), required.
  • Validate TLS Certificates (validateCertificates), 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-imap@0.4.9; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 4 actions and 1 trigger 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 IMAP 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-imap@0.4.9 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.