Create LinkedIn Message Sequences via API

// OVERVIEW

What it does

Create a multi-step LinkedIn outreach sequence: a series of message templates with a delay before each step, an optional connection request before the first message, and a sending schedule by day and hour in UTC.

Templates support {{variable}} placeholders with fallbacks, such as {{first_name|there}}, filled from each recipient's data when you enroll them. A recipient from Search People gives you {{first_name}}, {{headline}}, and the other fields of that record.

The first step's delay counts from the moment the recipient accepts the connection request; each later step counts from the previous one. Nothing is sent until you add people with Enroll Recipients.

Available in MCP and REST. Coming soon to the n8n node.

// PARAMETERS

Inputs

Name	Type	Required	Description
`name`	string	Required	Sequence name, up to 100 characters.
`steps`	array	Required	One or more message steps, sent in order.
`steps[].template`	string	Required	Message text, up to 8,000 characters. Supports {{variable}} and {{variable\|fallback}} placeholders.
`steps[].delayS`	—	Required	Seconds to wait before this step: from connection acceptance for the first step, from the previous step after that. For example, 172800 is 2 days.
`sendConnectionRequest`	boolean	Optional	Send a connection request to recipients who are not connected yet, before the first message.
`schedule`	object	Optional	Hours when messages may be sent, in UTC, per day (mo, tu, we, th, fr, sa, su), each with start and end in HH:MM. "*" or omitted means any time.

// OUTPUT SHAPE

Example JSON output

{
  "id": "BJ9KsYXf",
  "createdAt": "2026-09-28T12:42:39.834Z",
  "updatedAt": "2026-09-28T12:42:39.834Z",
  "name": "Q4 SaaS founders outreach",
  "status": "active",
  "sendConnectionRequest": true,
  "schedule": {
    "mo": [
      {
        "start": "09:00",
        "end": "17:00"
      }
    ],
    "tu": [
      {
        "start": "09:00",
        "end": "17:00"
      }
    ],
    "we": [
      {
        "start": "09:00",
        "end": "17:00"
      }
    ],
    "th": [
      {
        "start": "09:00",
        "end": "17:00"
      }
    ],
    "fr": [
      {
        "start": "09:00",
        "end": "17:00"
      }
    ]
  },
  "steps": [
    {
      "id": "BJ9KrssP",
      "position": 0,
      "delayS": 172800,
      "template": "Hi {{first_name|there}}, thanks for connecting. Curious how {{company|your team}} handles LinkedIn prospecting today?"
    },
    {
      "id": "BJ9Kr3tx",
      "position": 1,
      "delayS": 345600,
      "template": "Quick follow-up, {{first_name|there}}: happy to share how teams like {{company|yours}} automate this."
    }
  ]
}

// INVOCATION

How to call

Not available yet for this channel.

// CONSTRAINTS

Limits & status

Name up to 100 characters, each template up to 8,000 characters. Messages go out only within the sequence schedule and the sending limits of each profile. Create the sequence once and reuse it for any number of enrollments.

// USED IN

Playbooks using this Action

Score LinkedIn or Sales Navigator leads by ICP and draft outreach
LinkedIn or Sales Navigator search returns hundreds of profiles, and most of them are not a fit. Teams handle this in two expensive ways. Some message everyone, which burns limited sending capacity, hurts reply rate, and trains them to blast more. Others pay to enrich and AI-score every single row in a tool like Clay, spending credits on leads that were never going to qualify. Either way you pay full price for the whole list before you know who is worth it.

// GET STARTED

Start building with Periodix Actions

Create an account, get an API key, and call this Action from your stack.

Create your account