Skip to main content
All CollectionsAutomationOverview
Inside Automation: Node Types - Triggers
Inside Automation: Node Types - Triggers
Katherine Semenowa avatar
Written by Katherine Semenowa
Updated over a week ago

What are Triggers?

  • Triggers in GetSales.io Automations are specialized tasks designed to monitor the status of previous tasks and initiate subsequent tasks once certain conditions are met. Currently, there are two types of triggers: 'Connection Request Accepted' (LinkedIn only) and 'Message Replied'.

Why Use Triggers?

  • Fail prevention: you can't sent messages without being connected, and since GetSales checks for the connection before sending any message, lack thereof can lead to a failed status. Check connection trigger is an integral part of LinkedIn automation

  • Cold/ warm outreach. You don't want to send the same messages to cold leads and your contacts. Triggers can help you to manage this out of the box

  • Conversion rates boost: Persistency and consistency help to increase the conversion. As everyone knows utilising social activities helps to increase the CR. For example, while you are waiting for the contact to accept the connection request, schedule some social activity

How to Implement Triggers:

You can create Trigger nodes by hitting the 'plus' button in the Automation for adding a node and choosing the 'Triggers' section.

Screen Recording 2024-05-10 at 17.59.41.mov [video-to-gif output image]

In-between tasks: Both 'Connection Request Accepted' and 'Message Reply' triggers allow you to schedule additional tasks while the contact is on hold at the trigger node.

These tasks can include social activities and time delays. We are checking connection every 4 hours, if you set up a time delay that is less than 4 hours, the Contact will stay on the node until the presence of connection is checked.

All set delays will be cumulative - that would affect the total time a contact stays on that node before going into the rejected scenario (either not replied, or connection request wasn't accepted). If the positive outcome happens, the Contact will go forward, not waiting for the delays to end.

The delays will not take into account the schedule you set up for the Automation, the delay will count the time according to the 7-day week.

Did this answer your question?