Import Subscribers to Group

mailerlite.import_subscribers
ActionEmailconnection required

Calls the MailerLite API with the connection's credentials.

Queue a bulk import of subscribers into a group and return the job to poll.

Connection

Required
Yes — the node will not save without one
Auth type
Bearer token
Providers
MailerLite
Secret shape
the API token, or {"api_key": "…"}
Config it needs
base_url
Resolved by
config.connection_id, else node.connection_id

Configuration

2 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
group_id
The MailerLite id of the group the rows are imported into.
stringYes——123456789
subscribers
Rows to import; each needs an email and may carry a fields object.
arrayYes—≥ 1 characters; array of object[{"email":"dummy@example.com","fields":{"name":"Jane"}}]

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "group_id": "123456789",
  "subscribers": [
    {
      "email": "dummy@example.com",
      "fields": {
        "name": "Jane"
      }
    }
  ]
}

Output

One shape.

result

FieldTypeExample
submitted
How many rows were sent to MailerLite.
number—
import_progress_url
Where MailerLite reports the progress.
string—
import_id
Import id to pass to Get Import Report.
string—
group_id
The group the rows are imported into.
string—
{
  "group_id": "",
  "import_id": "",
  "import_progress_url": "",
  "submitted": 0
}

Notes

  • The import is asynchronous: MailerLite accepts the rows and validates them afterwards, so this node reports the queued job, never a per-row result. Read the outcome with Get Import Report.
  • MailerLite rate-limits this endpoint to 5 requests per minute per token.

See Import Subscribers to Group run in a workflow.

In a technical demo we add the MailerLite connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.