npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

n8n-nodes-flow

v0.1.1

Published

n8n community nodes for Flow SMS nurturing campaigns (tour-related templates and send message).

Readme

n8n-nodes-flow

Community nodes for n8n that integrate with Flow and the Common Service API for SMS nurturing campaigns. Process and send tour-related messages (new tour, tomorrow, today, completed, missed) with customizable templates.

n8n is a fair-code licensed workflow automation platform.

Nodes

Flow SMS Template

Process and customize SMS templates for nurturing campaigns. Supports variable substitution with {variableName}.

Message types:

  • Tour Is New – New tour prospects
  • Tour Is Tomorrow – Tours scheduled tomorrow
  • Tour Is Today – Tours scheduled today
  • Tour Completed – Completed tours
  • Tour Missed – Missed tours

Template options:

  • Use the default template from Common Service (e.g. from webhook payload), or
  • Provide a custom template override with your own copy and variables.

Common variables: {firstName}, {lastName}, {propertyName}, {propertySlug}, {scheduleTourDate}, {tourDateString}, {scheduleLink}, {rescheduleLink}, {applyLink}, {propertyAddress}.

You can use the generic Flow SMS Template node (choose message type in the UI) or the dedicated nodes: Tour Is New, Tour Is Tomorrow, Tour Is Today, Tour Completed, Tour Missed.

Flow SMS: Send Message

Send the processed SMS back to Common Service for delivery. Typically used after a template node in the same workflow.

  • Common Service URL – Base URL of your Common Service (e.g. https://dev-common-service.apps-and-services.com).
  • Endpoint – Default /v1/nurturing/send-message.
  • Processed Message – Usually {{ $json.processedContent }} from the previous template node.
  • Phone Number – From parameters or messageData / variables in the payload.

Supports API Key or Bearer authentication. Optional timeout and ignore-SSL options for troubleshooting.

Typical flow (n8n + Common Service)

  1. Common Service triggers an n8n Webhook when a tour event occurs (e.g. tour tomorrow, tour today, completed, missed).
  2. The webhook payload includes template data, variables, and messageData (e.g. phone, name).
  3. Use a Flow SMS template node (e.g. Tour Is Tomorrow) to process the template—either default or your override.
  4. Use Flow SMS: Send Message to POST the processedContent (and optional mediaURL) to Common Service, which handles delivery.

Installation

  1. Build the package: pnpm install then pnpm run build.
  2. Install in n8n per the community nodes installation guide. Use the path to this project (or dist after build).

Development

pnpm install
pnpm run build        # build nodes
pnpm run build:watch  # watch build
pnpm run dev          # run n8n with local nodes
pnpm run lint         # lint
pnpm run lint:fix     # lint and fix

Resources