All Collections
Kula Flows
Kula Flows FAQs
How to create a LinkedIn InMail in Kula Flows?
How to create a LinkedIn InMail in Kula Flows?
Kulanaut avatar
Written by Kulanaut
Updated over a week ago

As you select 'InMail' as a step in a Kula Flow, the editor opens up.

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

  1. Fill in an indicative name for the InMail for internal reference.

  2. Select if you want the step to be 'automatic' or 'manual'.

  3. Use the 'send after' drop-down to perfectly time the trigger of the InMail.

  4. Fill in the subject of the email. Subjects are an available field for all new emails and not available for any of the follow-ups.

  5. For the InMail body, you can either select a pre-saved InMail template or write the content from scratch.

  6. You have a limit of using a maximum of 2000 characters for an InMail body.

  7. Mail 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.

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

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

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


How to use personalization in LinkedIn InMails on Kula Flows?

Personalization in Kula is enabled through personalization tokens. You can find the list of such tokens in the InMail 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


Did this answer your question?