New Features
Wait Until → Multiple Days Selection New
You can now select multiple days in the “Wait Until → Next Day of the Week” delay type. The workflow will automatically resume on the soonest matching day.
How this helps you
- No need to duplicate workflows for different days
- More control over timing without complex logic
- Cleaner and simpler automation setup
Example use case
- You want to send follow-ups only on Monday, Wednesday, and Friday
- Select all three days in one step
- The workflow resumes on the next available matching day
- Ensures better engagement timing without manual effort
Advanced Delay Options in Sequences New
Sequences now support multiple delay types using the existing connector:
- Fixed Delay
- Immediate
- Random Delay
- Time of the Day
- Day of the Week
- Days from Now
- Specific Date
How this helps you
- Build more natural and human-like communication flows
- Avoid predictable timing patterns
- Customize delays based on real-world scenarios
Example use case
- Send a welcome email immediately
- Wait a random delay before the next email to avoid spam patterns
- Schedule a follow-up at a specific time of day for higher open rates
2-Step Email Source Picker New
The email compose flow now includes a 2-step email source picker, giving you more flexibility while creating emails.
What you can do
- Create a new email using:
- Drag & Drop Builder
- Rich Text Editor
- Custom HTML Editor
- Or reuse emails from past campaigns
How this helps you
- Saves time by reusing proven email templates
- Reduces repetitive work
- Keeps messaging consistent across campaigns
Example use case
- Reuse a high-performing campaign email in a new automation
- Quickly tweak content instead of creating from scratch
Bug Fixes
Generic Errors & Multiple Retries in Email Actions FIXED
Resolved an issue where failed email actions (e.g., Send Email, Send Opt-in Reminder) showed only a generic error:
“An error occurred while executing this action.”
What’s improved
- Clearer and more useful error messages for better debugging
- Failed actions no longer execute multiple times unnecessarily
Workflow Structure Breaking After Deleting Actions FIXED
Deleting an action placed before a branch no longer breaks the workflow structure.
Previously
- Actions inside the “Yes” branch were moved outside
- This caused “unreachable nodes” errors when saving
NOW
- Workflow structure remains intact
- Branch logic works as expected after deletion