Automation nodes are the individual building blocks of a workflow, with each node representing a specific action, decision point, or data processing step.
Any Automation has an "Automation Start" and "End Automation" Node. You can add and edit more Nodes between them to build an Automation that fits your needs.
Click the "+" button to create the first Node.
A new modal window will appear once you click the "+" button to add a Node. You will see all available Nodes that are divided into three sections: Popular, Logic and CRM Actions. Choose the one you need to create your first Node.
Popular Nodes Section
Outreach Nodes
Send Connection Request
The node Send Connection Request sends a LinkedIn connection request. Add a Connection Note if you like - 200 characters max, 300 if you're on LinkedIn Premium.
This Node has a custom text box, you can type your own message or use a Template. Once the Contact approves connection, the message you attach will be sent to their direct messages.
If you want to make the message personalized, use the "Insert variables" option.
Send message
The Send message Node sends a LinkedIn message. The text can be up to 8000 characters. You can not leave the message text box empty.
This node has a toggle "Send always". If enabled, the message will be sent to contacts with Replied status. If not enabled, the message will be sent only to contacts who have not replied before.
Withdraw Connection Request
This Node withdraws a LinkedIn connection request. If no connection request was previously sent to the contact, this node will be skipped.
Send InMail
Sends an InMail message. InMail can be sent for free to contacts with an Open Profile, or using credits if the Sender Profile has LinkedIn Premium. Otherwise, the task will fail.
This Node offers a text box for inserting your InMail text. The text box has the "Subject" section and the main section. You can also attach a file and insert variables. You can use a template by toggling the button above the text box.
By default, a contact's reply makes this task manual. You can toggle the "Always send" button to send emails regardless of replies.
Send Email
Sends an email message. If the contact doesn't have an email address for the selected email type, the task will fail.
You can choose the email type (Send to work email/Send to personal email/Send to any email):
If you toggle the button "Send in previous thread", the email will be sent in an existing thread, if available. Otherwise, it will create a new email with the specific subject.As for the email text, you can add a Subject and attach files. You can use a template and add variables as well.
The button "Always send" allows you to send the email regardless of the contact's reply.
Social Nodes
Visit Profile
Visits a linkedIn profile page. The contact will receive a notification that their LinkedIn profile was visited.
Like Latest Post
Leaves a Like on the latest post. The contact will receive a notification that their post was liked.
Note: When you create multiple Nodes "Like Latest Post", it doesn't allow you to like several posts. Only the latest post will be liked.
Comment Latest Post
Leaves a comment on the latest article or post. The contact will receive a notification that their post was commented on. The comment can be up to 1,250 characters.
The comment can contain Variables.
Endorse Skills
Endorses a specified number of skills. Up to 10 skills can be endorsed. You can set the number of skills in the "Skills count" box.
Advanced Nodes
Wait for Connection
Continuously checks if the connection request is accepted. If accepted, the contact immediately moves to the "Connected" branch. If not accepted during the subtasks sequence, they move to "No connect". Add subtasks to improve conversions.
This Node can contain Subtasks. Click "Add task" and choose one of the options: Time delay, Comment Latest Post, Like Latest Post, Visit profile.
Note: The actual wait time can differ from the set wait period due to executing subtasks. If the set period ends before all subtasks are executed, contacts will not go to the next node.
Rotate Sender Profile
Restarts the automation from the specified segment node with another sender as set in Rotation steps. The Rotation Steps define how many times the automation should be restarted. If no sender profile is selected, it will be set using the segment's settings.
You can create several rotations in this Node, just click the button "Add rotation". When all rotations are set, click "Create" to add the Node.
Call Custom Webhook
Triggers the selected custom webhook.
|Note: You need to have a webhook prepared to use it in this Node. Read more about webhooks in this article.
Call API
Connect and interact with the external tools or databases using a customizable API endpoint.
You can choose a Method:
GET
POST
PUT
PATCH
DELETE
By toggling the "Remove empty values" you can exclude empty, null, or undefined values from the request to prevent overwriting data.
Query StringAdd key-value parameters to customize your API request. These will be appended to the endpoint as query string parameters. Note: you can only use variables as keys.
Send to Automation
Sends the contact to the specified automation. Additionally, the contact will remain in progress within automation. You can choose the existing automation by clicking the "Select automation" box.
CRM Actions Section
Contact Management
Add Tag
Adds a specific tag. You need to create a tag in advance to use it in an automation.
Remove TagRemoves a specific tag.
Change List
Moves the contact to the specified list. A list has to be created in advance to be used in an automation.
Change Pipeline Stage
Changes the Pipeline Stage to the specified one.
5. Change Sender Profile
Change the Sender Profile to the specified one. Further automation will continue from new sender Profile.
Integrations
Call Custom Webhook
Triggers the selected custom webhook.
2. Call API
Connect and interact with external tools or databases using a customizable API endpoint.
You can choose the method (GET, POST, PUT, PATCH, DELETE).
Exclude empty, null, or undefined values from the request to prevent overwriting data.
Query string adds a key-value parameters to customize your API request. These will be appended to the endpoint as query string parameters. You can define the JSON payload to pass structured data in the request body.
Node Settings
Every node has settings available to change whenever you like. To access the Node Settings Sidebar, click the node, and the sidebar will appear on your right.
Every node can be set to run Manually or Automatically. By default, all nodes run automatically. If you want to change the node to manual mode, click the node to access the settings and change Automatically to Manually on the bottom of the sidebar.
You can also add a delay period here that the node will wait until executing the task. To add a delay period, put the number next to Wait and select in the next field Days or Minutes.
Deleting a Node
You can delete any node by clicking the three dots (⋯) in the top-right corner of the node settings sidebar and selecting Delete.
The sequence stays intact. When you delete a node, the node before it and the node after it are automatically reconnected — the flow continues without any gaps, as if the deleted node was never there.
Note: This applies regardless of where the node sits in the sequence — beginning, middle, or end.
What happens to leads currently in progress on that node
If the node you're deleting has leads currently in progress, you'll see a prompt asking how to handle them before the deletion completes:
Option | What it does |
Skip | Leads move forward to the next node and continue through the automation |
Cancel | Leads are cancelled and stop progressing through the automation entirely |
Choose Skip if you want those leads to continue their journey. Choose Cancel if you no longer want them in the automation.
Q: Is it possible to restore a deleted node in an automation?
Yes, you can recover a deleted node using version history. Click the calendar icon in the top-right corner of the automation builder to open version history. From there, you can view previous versions and restore the automation to a state before the node was deleted.
Q: Can I send native videos in LinkedIn messages through GetSales?
No, you cannot send native LinkedIn videos directly through GetSales. However, you can attach video files to LinkedIn messages — the video will appear as an attachment rather than a native inline video. For sending native videos, you would need to do so manually through LinkedIn directly.
Q: How does the "Wait for Connection" node work exactly?
The "Wait for Connection" node automatically checks whether a connection request has been accepted. It continuously monitors the connection status during the configured wait period. If the contact accepts the connection, they immediately move to the "Connected" branch and proceed to the next steps in the automation. If the connection is not accepted by the time the wait period ends, the contact moves to the "No Connect" branch. You can add subtasks (like Visit Profile or Like Latest Post) within this node to improve connection acceptance rates while waiting.
Q: Is there a quick way to see an A/B test overview or report for my automation?
There is no dedicated A/B test overview report in GetSales. To compare results between different message variants or automation paths, you need to do this manually — for example, by checking node-level statistics (sent, replied, connection rate) for each variant separately and comparing the numbers yourself. A built-in A/B testing report feature is not currently available.
Q: Can I set up an automation that sends a connection request if an email bounces?
Yes, this is possible using the Condition Rules node. After a Send Email node, add a Condition Rules node and configure it to check whether the email bounced (using the "Email Bounced" condition). In the branch for bounced emails, add a Send Connection Request node. This way, if the email fails to deliver, the automation will automatically attempt to connect with the contact on LinkedIn instead.
Q: Can I like 3 posts at once with the "Like Latest Post" node?
No, it is not possible to like multiple posts at once. The "Like Latest Post" node only likes the single most recent post from the contact's profile, regardless of how many "Like Latest Post" nodes you add to the automation. Each node will attempt to like the latest post, but since it's the same post, only one like will be registered. There is currently no option to like multiple posts in a single automation run.