On the left sidebar navigate to the “Automations” section and click “Create New Automation”.
Set the automation name and priority. The "Use Sender Profile’s Schedule" toggle is enabled by default, meaning the automation's working hours will sync with the sender profile's schedule. However, you can manually adjust the automation's working hours if needed.
*The server's schedule must align with the automation schedule. Otherwise, the automation may not function correctly or at all.
Once you've completed it, the system will take you to the sequence builder, which is structured like a mind map. The first key feature to note is “Add Segment”. By default, the system distributes outreach messages randomly among multiple sender profiles. However, if you have multiple profiles and need to assign imported contacts to specific profiles, adding a new segment allows you to manage everything in one automation instead of creating separate ones for each sender.
Clicking on “Segment” allows you to set contact limits. For example, if you set the “contacts limit” to 100, contacts will be added gradually. Until the first 100 contacts complete their step, no additional contacts will proceed.
*In most cases, leaving the setting as “Unlimited” is sufficient, unless you are working with complex workflows with multiple branches.
In the “Sender Profiles” section, select the account from which the campaign will be conducted. You can add multiple sender profiles to a single segment, also choose a method for distributing contacts between sender profiles..
Clicking “+” opens a menu with available automation blocks. Start with connection requests, which can be sent and withdrawn after a specified time interval.
Clicking “Send Connection Request” opens a “connection note” window. You can either leave this field empty or add a short message (up to 300 characters).
It’s recommended to keep the toggle switch ON so that when the personalized invite limit is reached, the system automatically sends blank connection requests instead. The "Withdraw Connection Request" feature enables automatic withdrawal of unaccepted pending requests.
“Messages Section” - There are 2 messaging options: LinkedIn messages and Email messages.
LinkedIn messages – type your message in the text field and attach a file if needed (1). You can also add variables (2).
The “Send always, even if contact replied” toggle (3), when turned off, stops the automation if the lead responds. If switched on, the system will continue sending messages even after receiving a reply.
Email messages – when opening the message window, you can choose to send an email to a personal or work address, or both.
Reply to previous thread(1) – keep it enabled if you want follow-up emails to stay within the same thread (with an identical subject). Disable it if you plan to use different subjects for each email. Subject field (2) and body text field (3) for composing the email.
“Social Activity Section” - the main goal of this section is to increase your visibility to potential clients. It is typically used between message sequences or before sending a connection request. Available actions include visiting profiles, liking and commenting on posts, and endorsing skills. Key points to consider:
LinkedIn tracks profile visit frequency, so avoid excessive use of the visit profile function.
for post comments, you can write a custom template, but keep in mind that the system will comment on the latest post without analyzing its content. To avoid issues, use a neutral comment that fits any type of post.
skill endorsements are only available for 1st-degree connections, so apply this function only after your connection request has been accepted.
“Triggers Section” - triggers allow you to branch out automation flows based on different scenarios. (For example, the Connection Request Accepted trigger creates two paths: one for accepted requests and another for ignored requests.)
Connection Request Accepted – this trigger is essential after sending a connection request, as it determines whether the request was accepted and helps structure the message flow accordingly.
Message Replied Trigger– checks whether the lead has responded to your message.
Both triggers support Social Activity actions and wait time settings. They can be set sequentially throughout the automation.
*Common mistake – setting a trigger for only 1 day. Keep in mind that the trigger will only be active for the duration you specify. If the connection request trigger is set to 1 day, any lead who doesn’t accept within 24 hours will move down the "No Connect" path. Even if they accept later, they won’t return to the trigger stage. To prevent this, set the connection request trigger to 14–20 days and the message reply trigger to at least 3–4 days between messages.
“Delay Section” - Time Delay sets a waiting period before the next action is executed.
“Data Section” - automates data management, including: assigning or removing tags, changing pipeline stages, moving contacts between lists, or changing sender profiles and automation sequences.
Call Webhook, API Call, and Rotate Sender Profile require some initial setup before use.
You can find detailed instructions for each function at the following links:
“Automation Control Section”
Condition Rules - allows filtering contacts to create different scenarios.
A/B Testing – allows splitting the automation flow into different branches with unique actions for each. You can adjust the number of branches and control the percentage of contacts that follow each path.
