What’s new?

You can now start a workflow whenever an inbound email is received in your mailbox. This covers cold emails from brand-new senders, warm emails from existing contacts, and, if you allow it, replies inside existing threads – so you can automate lead capture, routing, support intake, and follow-up from the moment an email arrives.

Why this matters

Every inbound email is a potential lead, support request, or deal moving forward – and now your workflows can act on it instantly. The Inbound Email trigger captures emails the moment they land, including first-touch messages from people who aren't in your CRM yet. That means sales teams can route and respond to cold inquiries automatically, support teams can assign incoming requests without manual sorting, and ops teams can kick off processes as soon as a signed document or form hits the inbox.

How it works

The trigger fires when an inbound email is received and can be narrowed with filters for mailbox, sender, CC, subject, body, attachments, and whether the message was tied to a workflow. You can also choose to run it only for new email conversations, which helps avoid retriggering on every reply in the same thread.

Available filters

• Email Sent To / Mailbox – Matches the receiving mailbox.
• From – Matches the sender’s email address.
• CC – Checks copied recipients.
• Subject – Matches the email subject line.
• Body (plain text) – Checks the email body.
• Has Attachments – Checks whether attachments are present.
• Replied to Workflow – Checks whether the email came from a specific workflow.
• Contact Tag – Filters by whether the contact has or does not have a specific tag.

Custom value picker

• {{messageid}} – Unique message ID of the inbound email.
• {{subject}} – Subject line of the inbound email.
• {{bodyplain}} – Plain-text body content of the email.
• {{<a href="http://from.email" rel="ugc nofollow noopener noreferrer" target="blank”>from.email}} – Sender’s email address.
• {{<a href="http://from.name" rel="ugc nofollow noopener noreferrer" target="blank”>from.name}} – Sender’s display name.
• {{cc}} – CC recipients of the inbound email.
• {{inboundEmail.bodyFullPlain}} – Full Body (Includes reply thread)

How to use it

• Go to Automations > Workflows > Add Trigger and add the Inbound Email trigger.
• Add filters based on mailbox, sender, subject, body, attachments, or workflow reply source.
• Save the trigger, then add actions like create contact, assign, tag, notify, or reply.

Common use cases

• Inbox routing: Check which mailbox received the email and send sales@, support@, or billing@ traffic into different workflow paths.
• Subject-based assignment: Catch emails with subjects like “refund” and route them faster.
• Attachment intake: Trigger only when attachments are present so teams can react to forms, documents, or proofs as soon as they arrive.
• First-touch autoresponder: Use the inbound email body in downstream actions to send a more contextual first response.

Additional notes

• Full cold inbound capture is supported for LC Email dedicated domains and Mailgun dedicated domains. Gmail/Outlook two-way sync, shared domains, and other SMTP setups do not support full cold inbound capture.
• This trigger is separate from Customer Replied, so both can exist at the same time. In some cases an email can match both, so filters and the reply tracking setting can help control overlap.
• Each sub-account should use its own dedicated email subdomain. Reusing the same domain across multiple sub-accounts can lead to unpredictable inbound routing

Preview:

What’s new?

You can now start a workflow whenever an inbound email is received in your mailbox. This covers cold emails from brand-new senders, warm emails from existing contacts, and, if you allow it, replies inside existing threads – so you can automate lead capture, routing, support intake, and follow-up from the moment an email arrives.

Why this matters

Every inbound email is a potential lead, support request, or deal moving forward – and now your workflows can act on it instantly. The Inbound Email trigger captures emails the moment they land, including first-touch messages from people who aren't in your CRM yet. That means sales teams can route and respond to cold inquiries automatically, support teams can assign incoming requests without manual sorting, and ops teams can kick off processes as soon as a signed document or form hits the inbox.

How it works

The trigger fires when an inbound email is received and can be narrowed with filters for mailbox, sender, CC, subject, body, attachments, and whether the message was tied to a workflow. You can also choose to run it only for new email conversations, which helps avoid retriggering on every reply in the same thread.

Available filters

• Email Sent To / Mailbox – Matches the receiving mailbox.
• From – Matches the sender’s email address.
• CC – Checks copied recipients.
• Subject – Matches the email subject line.
• Body (plain text) – Checks the email body.
• Has Attachments – Checks whether attachments are present.
• Replied to Workflow – Checks whether the email came from a specific workflow.
• Contact Tag – Filters by whether the contact has or does not have a specific tag.

Custom value picker

• {{messageid}} – Unique message ID of the inbound email.
• {{subject}} – Subject line of the inbound email.
• {{bodyplain}} – Plain-text body content of the email.
• {{<a href="http://from.email" rel="ugc nofollow noopener noreferrer" target="blank”>from.email}} – Sender’s email address.
• {{<a href="http://from.name" rel="ugc nofollow noopener noreferrer" target="blank”>from.name}} – Sender’s display name.
• {{cc}} – CC recipients of the inbound email.
• {{inboundEmail.bodyFullPlain}} – Full Body (Includes reply thread)

How to use it

• Go to Automations > Workflows > Add Trigger and add the Inbound Email trigger.
• Add filters based on mailbox, sender, subject, body, attachments, or workflow reply source.
• Save the trigger, then add actions like create contact, assign, tag, notify, or reply.

Common use cases

• Inbox routing: Check which mailbox received the email and send sales@, support@, or billing@ traffic into different workflow paths.
• Subject-based assignment: Catch emails with subjects like “refund” and route them faster.
• Attachment intake: Trigger only when attachments are present so teams can react to forms, documents, or proofs as soon as they arrive.
• First-touch autoresponder: Use the inbound email body in downstream actions to send a more contextual first response.

Additional notes

• Full cold inbound capture is supported for LC Email dedicated domains and Mailgun dedicated domains. Gmail/Outlook two-way sync, shared domains, and other SMTP setups do not support full cold inbound capture.
• This trigger is separate from Customer Replied, so both can exist at the same time. In some cases an email can match both, so filters and the reply tracking setting can help control overlap.
• Each sub-account should use its own dedicated email subdomain. Reusing the same domain across multiple sub-accounts can lead to unpredictable inbound routing

Preview:

What’s new?

You can now start a workflow whenever an inbound email is received in your mailbox. This covers cold emails from brand-new senders, warm emails from existing contacts, and, if you allow it, replies inside existing threads – so you can automate lead capture, routing, support intake, and follow-up from the moment an email arrives.

Why this matters

Every inbound email is a potential lead, support request, or deal moving forward – and now your workflows can act on it instantly. The Inbound Email trigger captures emails the moment they land, including first-touch messages from people who aren't in your CRM yet. That means sales teams can route and respond to cold inquiries automatically, support teams can assign incoming requests without manual sorting, and ops teams can kick off processes as soon as a signed document or form hits the inbox.

How it works

The trigger fires when an inbound email is received and can be narrowed with filters for mailbox, sender, CC, subject, body, attachments, and whether the message was tied to a workflow. You can also choose to run it only for new email conversations, which helps avoid retriggering on every reply in the same thread.

Available filters

• Email Sent To / Mailbox – Matches the receiving mailbox.
• From – Matches the sender’s email address.
• CC – Checks copied recipients.
• Subject – Matches the email subject line.
• Body (plain text) – Checks the email body.
• Has Attachments – Checks whether attachments are present.
• Replied to Workflow – Checks whether the email came from a specific workflow.
• Contact Tag – Filters by whether the contact has or does not have a specific tag.

Custom value picker

• {{messageid}} – Unique message ID of the inbound email.
• {{subject}} – Subject line of the inbound email.
• {{bodyplain}} – Plain-text body content of the email.
• {{<a href="http://from.email" rel="ugc nofollow noopener noreferrer" target="blank”>from.email}} – Sender’s email address.
• {{<a href="http://from.name" rel="ugc nofollow noopener noreferrer" target="blank”>from.name}} – Sender’s display name.
• {{cc}} – CC recipients of the inbound email.
• {{inboundEmail.bodyFullPlain}} – Full Body (Includes reply thread)

How to use it

• Go to Automations > Workflows > Add Trigger and add the Inbound Email trigger.
• Add filters based on mailbox, sender, subject, body, attachments, or workflow reply source.
• Save the trigger, then add actions like create contact, assign, tag, notify, or reply.

Common use cases

• Inbox routing: Check which mailbox received the email and send sales@, support@, or billing@ traffic into different workflow paths.
• Subject-based assignment: Catch emails with subjects like “refund” and route them faster.
• Attachment intake: Trigger only when attachments are present so teams can react to forms, documents, or proofs as soon as they arrive.
• First-touch autoresponder: Use the inbound email body in downstream actions to send a more contextual first response.

Additional notes

• Full cold inbound capture is supported for LC Email dedicated domains and Mailgun dedicated domains. Gmail/Outlook two-way sync, shared domains, and other SMTP setups do not support full cold inbound capture.
• This trigger is separate from Customer Replied, so both can exist at the same time. In some cases an email can match both, so filters and the reply tracking setting can help control overlap.
• Each sub-account should use its own dedicated email subdomain. Reusing the same domain across multiple sub-accounts can lead to unpredictable inbound routing

Preview:

What’s new?

You can now start a workflow whenever an inbound email is received in your mailbox. This covers cold emails from brand-new senders, warm emails from existing contacts, and, if you allow it, replies inside existing threads – so you can automate lead capture, routing, support intake, and follow-up from the moment an email arrives.

Why this matters

Every inbound email is a potential lead, support request, or deal moving forward – and now your workflows can act on it instantly. The Inbound Email trigger captures emails the moment they land, including first-touch messages from people who aren't in your CRM yet. That means sales teams can route and respond to cold inquiries automatically, support teams can assign incoming requests without manual sorting, and ops teams can kick off processes as soon as a signed document or form hits the inbox.

How it works

The trigger fires when an inbound email is received and can be narrowed with filters for mailbox, sender, CC, subject, body, attachments, and whether the message was tied to a workflow. You can also choose to run it only for new email conversations, which helps avoid retriggering on every reply in the same thread.

Available filters

• Email Sent To / Mailbox – Matches the receiving mailbox.
• From – Matches the sender’s email address.
• CC – Checks copied recipients.
• Subject – Matches the email subject line.
• Body (plain text) – Checks the email body.
• Has Attachments – Checks whether attachments are present.
• Replied to Workflow – Checks whether the email came from a specific workflow.
• Contact Tag – Filters by whether the contact has or does not have a specific tag.

Custom value picker

• {{messageid}} – Unique message ID of the inbound email.
• {{subject}} – Subject line of the inbound email.
• {{bodyplain}} – Plain-text body content of the email.
• {{<a href="http://from.email" rel="ugc nofollow noopener noreferrer" target="blank”>from.email}} – Sender’s email address.
• {{<a href="http://from.name" rel="ugc nofollow noopener noreferrer" target="blank”>from.name}} – Sender’s display name.
• {{cc}} – CC recipients of the inbound email.
• {{inboundEmail.bodyFullPlain}} – Full Body (Includes reply thread)

How to use it

• Go to Automations > Workflows > Add Trigger and add the Inbound Email trigger.
• Add filters based on mailbox, sender, subject, body, attachments, or workflow reply source.
• Save the trigger, then add actions like create contact, assign, tag, notify, or reply.

Common use cases

• Inbox routing: Check which mailbox received the email and send sales@, support@, or billing@ traffic into different workflow paths.
• Subject-based assignment: Catch emails with subjects like “refund” and route them faster.
• Attachment intake: Trigger only when attachments are present so teams can react to forms, documents, or proofs as soon as they arrive.
• First-touch autoresponder: Use the inbound email body in downstream actions to send a more contextual first response.

Additional notes

• Full cold inbound capture is supported for LC Email dedicated domains and Mailgun dedicated domains. Gmail/Outlook two-way sync, shared domains, and other SMTP setups do not support full cold inbound capture.
• This trigger is separate from Customer Replied, so both can exist at the same time. In some cases an email can match both, so filters and the reply tracking setting can help control overlap.
• Each sub-account should use its own dedicated email subdomain. Reusing the same domain across multiple sub-accounts can lead to unpredictable inbound routing

Preview:

🧭 Overview

We’ve extended support for assigned user custom values to ensure they work consistently across both Funnels and Calendar confirmation page experiences.

With this update, assigned user details can be carried forward into the next funnel step after booking a calendar appointment, as well as used in calendar confirmation messages., improving personalization after an appointment is booked.

✅ What’s New

1. Added support for assigned user custom values across:

• Next funnel step after booking a calendar appointment
• “Thank you message" on the calendar confirmation page

2. Improved consistency in how assigned user data is rendered across booking and funnel flows.

🔐 How It Works

1. When using a Calendar element in a funnel with the "Redirect action" set as “Go to next step” :

• After booking, users are redirected to the next funnel step
• You can now use assigned user custom values on that page

2. This value also work in:

• “Thank you message" on the calendar confirmation page

3. This values dynamically populate based on the assigned user linked to the contact, ensuring accurate and consistent output across flows.

🎯 Why This Matters

• Enables personalized experiences after booking (e.g., showing assigned user details).
• Ensures assigned user information carries forward into the next step.