All Collections
Kula Flows
Kula Flows FAQs
How to setup a LinkedIn 'Connection Request' as a step on Kula Flows
How to setup a LinkedIn 'Connection Request' as a step on Kula Flows
Kulanaut avatar
Written by Kulanaut
Updated over a week ago

As you select 'Connection Request' as a step in Kula Flows, the editor for the request message opens up.

In the editor, you get to see certain empty fields. Here are the steps to follow:

  • Fill in an indicative name for the step for internal reference.

  • Choose whether you want the request to go out Manually or you want to automate the step

  • Use the 'Perform Action' drop-down to perfectly time the trigger of the email.

  • For the message body, you can either select a pre-saved mail template or write a message from scratch.

  • The maximum limit of the message can only be 300 characters.

  • Message template: You can select a pre-saved template the editor will populate itself with all the details of the template. You can edit it further.

  • Save as template: If there is a message copy that you reuse a lot of times with minor edits, you can save those as templates and you'll find them under 'Message Template' on the top-right of the email editor.

  • Click on the 'preview' icon in the center-right of the email editor for a final check.

  • Click on 'Save Step' to save all edits and changes.


Personalize the 'LinkedIn connection request message'

Personalization in Kula is enabled through personalization tokens. You can find the list of such tokens in the message editor. The tokens are segregated into 3 groups - Candidate tokens, Org tokens, and Sender tokens.

Here is the exhaustive list of tokens:

  1. Candidate Email

  2. Candidate First Name

  3. Candidate Last Name

  4. Candidate Full Name

  5. Candidate Company Name

  6. Candidate Phone Number

  7. Candidate Position

  8. Org Name (of the recruiter)

  9. Sender Email

  10. Sender First Name

  11. Sender Last Name

  12. Sender Full Name

  13. Sender Timezone

  14. Sender Signature


Also read:

Did this answer your question?