lime-marketing

n8n community node for Lime Marketing — send transactional email and SMS

Package Information

Released: this month
Downloads: 0 weekly / 0 monthly
Latest Version: 1.1.0
Author: Lime Technologies

Available Nodes

Documentation generating…

Lime CRM Marketing icon
Lime CRM Marketing
Send transactional emails and SMS via the Lime CRM Marketing API

Documentation

@limetech/n8n-nodes-lime-marketing

This is an n8n community node. It lets you use Lime Marketing in your n8n workflows.

Lime Marketing is a marketing automation platform from Lime Technologies. This node lets you send transactional email and SMS through your Lime Marketing instance.

n8n is a fair-code licensed workflow automation platform.

Installation
Operations
Credentials
Compatibility
Usage
Resources
Version history
Development

Installation

Follow the installation guide in the n8n community nodes documentation and install @limetech/n8n-nodes-lime-marketing.

Operations

Lime CRM Marketing

  • Email → Send: send a transactional email, either from a Lime Marketing template (with merge-code mapping) or with custom HTML/text content, including attachments, scheduling, tracking and header options.
  • SMS → Send: send a transactional SMS from a Lime Marketing template with merge-code support.

Failed sends can be routed to the node's error output by setting On Error to "Continue (using error output)" in the node settings.

Credentials

To use this node you need a Lime Marketing account and an API key.

  1. In Lime Marketing, generate an API key for the REST API.
  2. In n8n, create a Lime CRM Marketing API credential with:
Field Description
Lime CRM Marketing API URL The API URL of your Lime Marketing instance, e.g. https://app.bwz.se/bedrock/CUSTOMERNAME/api/
API Key The API key obtained from Lime Marketing

Requests are authenticated with the apikey header, which n8n adds automatically. The credential is verified against the /ping/version endpoint of your instance when you save it.

Compatibility

Requires n8n with n8n-workflow 2.9 or later. Node.js 24 is used for local development.

Usage

Lime CRM Marketing: send an email from a template

  1. Add a Lime CRM Marketing node and select your Lime CRM Marketing API credential.
  2. Set Resource to Email and Operation to Send.
  3. Set Content Type to Lime Marketing Template and pick the template under Template.
  4. Fill in From Email (the domain must be verified in Lime Marketing), Recipient Email and optionally Subject, From Name and Recipient Name.
  5. Under Merge Code Mapping, the merge codes found in the template are listed. Enter a value for each one you want to replace, for example {{ $json.firstname }}. Alternatively set Merge Codes Input Method to JSON Object and provide them as {"{{firstname}}": "Anna"}.

To send your own content instead, set Content Type to Custom HTML or Plain Text and enter the body in HTML Content or Text Content. Files from an upstream node can be attached under Attachments by naming the binary property (default data). Additional Options holds scheduling, reply-to, opt-out exclusions and custom headers.

Lime CRM Marketing: send an SMS

  1. Add a Lime CRM Marketing node and select your Lime CRM Marketing API credential.
  2. Set Resource to SMS and Operation to Send.
  3. Enter From Number (an alphanumeric sender ID of 2 to 11 characters, for example MyCompany) and Destination Number in international format, for example +46701234567.
  4. Enter the Text. Merge codes such as {{firstname}} are replaced with the values you provide under Merge Code Mapping.

Both operations output one item per input item with the API response for the sent message. Failed sends throw by default. To route them to a separate branch instead, set On Error to Continue (using error output) in the node settings. The error output carries the API message as $json.error.

Resources

Version history

The full history is generated by semantic-release in CHANGELOG.md and on the GitHub releases page.

Development

npm ci
npm run build   # compile to dist/
npm test        # jest unit tests
npm run lint    # n8n community node lint rules
npm run knip    # dead code check

License

MIT

Discussion