n8n-nodes-lomavis

This is an n8n community node for integrating with the Lomavis social media management platform in n8n workflows. Lomavis helps teams manage social publishing, media uploads, approvals, analytics, competitors, and profile groups from one API.

n8n is a fair-code licensed workflow automation platform.

Installation
Operations
Credentials
Usage
Examples
Resources
Development
Publishing

Installation

Community Nodes (Recommended)

For users on n8n v0.187+, install this package directly from the Community Nodes panel in the n8n editor:

1. Open your n8n editor
2. Go to Settings > Community Nodes
3. Search for n8n-nodes-lomavis
4. Select Install
5. Reload the editor if prompted

Manual Installation

You can also install this node manually:

1. Navigate to your n8n installation directory
2. Run:

npm install n8n-nodes-lomavis

3. Restart n8n so the node is loaded

For local development:

# In this repository:
npm install
npm run build
npm link

# In your n8n custom folder (~/.n8n/custom):
npm link n8n-nodes-lomavis

Operations

This node currently supports the following Lomavis resources and actions:

Profile Group

• List profile groups
• Get a profile group by ID
• Search profile groups by name

Post

• Create a post
• Create a draft and send it for approval
• Send a post approval request
• List posts by status
• Delete a post

Media

• Upload media files before attaching them to posts

Analytics

• Get analytics-ready post data

Competitor

• List tracked competitors

Credentials

To use this node, you need a Lomavis API key.

1. Sign in to your Lomavis account
2. Open Settings > API Access
3. Copy your API key
4. In n8n, create new Lomavis API credentials and paste the key

The node authenticates requests with the header format Authorization: Token <api_key>.

Usage

Use this node when you want n8n to create or manage social-media activity in Lomavis without building raw HTTP requests yourself.

Typical workflow pattern:

1. Upload media with Media > Upload when a post requires assets
2. Create the content with Post > Create or Post > Create Draft and Send Approval
3. Route approval requests through Post > Send Approval or track them with Post > List By Status
4. Pull reporting data with Analytics > Get Posts

Examples

Example 1: Create and approve a social post

• Use Media > Upload to upload an image from binary data
• Pass the returned media_uuid into Post > Create Draft and Send Approval
• Configure first-step approvers and optional second-step approvers
• Use Post > List By Status to monitor approval progress

Example 2: Find the right profile group before posting

• Use Profile Group > Search with part of the group name
• Select the returned profile group ID
• Reuse that ID in Post > Create so the post is sent to the correct connected profiles

Example 3: Pull Lomavis analytics into downstream reporting

• Use Analytics > Get Posts to fetch reporting data for published content
• Send the output into Google Sheets, Notion, Slack, or another reporting destination in n8n

Resources

• Lomavis website
• Lomavis API documentation
• n8n community nodes documentation
• npm package

Development

npm install
npm run build
npm run build:watch
npm run lint
npm test
npm run release:verify

Publishing

GitHub publishing is handled automatically by ci.yml using npm trusted publishing.

1. In npm package settings for n8n-nodes-lomavis, add a trusted publisher for Lomavis / n8n-nodes-lomavis / ci.yml
2. The workflow filename must match exactly, including case and the .yml extension
3. Update package.json to the version you want to release before merging to main
4. Merge code into main
5. GitHub Actions will run npm run release:verify
6. If that commit is still the latest tip of main when CI finishes and package.json is newer than the currently published npm version, the workflow creates a vX.Y.Z tag from that exact commit, publishes to npm using OIDC, and creates the GitHub release
7. If package.json still matches the published npm version, CI skips publishing
8. If a newer commit lands on main while CI is still running, the older run skips releasing and the newer main run becomes the deploy candidate

For local validation before cutting a release, run:

npm run release:verify

License

MIT