🧭 Overview

We’ve improved the booking experience for Rentals to make selecting dates faster and more intuitive.

Previously, when a customer selected a start date in a future month, the end date picker would still open in the current month, requiring users to manually navigate again. This added unnecessary friction during booking.

With this update, the end date picker now opens in the same month as the selected start date.

✅ What’s New

• End date picker now opens in the same month as the selected start date.
• Eliminates the need to scroll across months again when selecting the end date.

🔐 How It Works

When a customer selects a start date in a future month on the booking page:

• The end date picker will automatically open in that same month.

🎯 Why This Matters

• Reduces friction in the booking flow.
• Makes date selection faster and more intuitive.
• Improves overall customer experience for rental bookings.

What’s new?

You can now drag and move nodes directly inside the workflow canvas. This enhancement makes it easier to reorganize actions and branches without deleting steps or using the right-click move option for each node you want to move.

How it works

When you hover over a node, a 6-dot drag handle appears. Click and hold the handle, then move the node to a new position in the workflow. As you drag, the canvas shows a clear “Move here” indicator so you can see where the node can be dropped.

How to use it

• Hover over a node to reveal the 6-dot drag handle.
• Click and hold the handle, then drag the node to a new location.
• Drop it where you see the “Move here” indicator.

Why we built it

Managing larger workflows can be slow when you have to move steps one by one through right click menus. Drag and drop gives you a faster, more fun and intuitive way to clean up layouts and reorganize branches as your workflow changes.

Additional Notes

• The 6-dot drag handle is only visible when you hover over a node.
• Moving nodes is done directly from the canvas.
• Valid drop locations are guided by the “Move here” indicator.

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: