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

@memberjunction/integration-actions

v5.26.0

Published

MemberJunction Integration Engine Actions - MJ Actions for triggering and managing integration syncs

Readme

@memberjunction/integration-actions

MJ Actions for triggering MemberJunction integration syncs. Connects the Integration Engine to the MJ Actions + Scheduling system.

Installation

This package is registered as a workspace package. Add it as a dependency and import it so the @RegisterClass decorator fires:

// In your bootstrap or entry point:
import '@memberjunction/integration-actions';

Actions

Run Integration Sync

Action Name: Run Integration Sync

Triggers a full sync run for a MJ: Company Integration record.

| Parameter | Direction | Type | Required | Description | |-----------|-----------|------|----------|-------------| | CompanyIntegrationID | Input | string | Yes | ID of the CompanyIntegration to sync | | TriggerType | Input | string | No | Manual, Scheduled, or Webhook (default: Manual) | | RecordsProcessed | Output | number | — | Total records processed | | RecordsCreated | Output | number | — | Records created in MJ | | RecordsUpdated | Output | number | — | Records updated in MJ | | RecordsDeleted | Output | number | — | Records deleted in MJ | | RecordsErrored | Output | number | — | Records that encountered errors | | RecordsSkipped | Output | number | — | Records that were skipped | | ErrorSummary | Output | string | — | JSON array of first 10 errors (only when errors exist) |

Result Codes:

  • SUCCESS — Sync completed without errors
  • SYNC_COMPLETED_WITH_ERRORS — Sync completed but some records failed
  • MISSING_PARAMETER — Required CompanyIntegrationID not provided
  • UNEXPECTED_ERROR — Unhandled exception during sync

Scheduling via MJ Scheduler

  1. Create an MJ: Actions record for Run Integration Sync
  2. Create an MJ: Action Params record for CompanyIntegrationID
  3. Set up a Scheduled Job pointing to this action
  4. The scheduler calls the action on the configured cadence

Usage from Code

import '@memberjunction/integration-actions'; // ensure registration
import { ActionEngine } from '@memberjunction/actions';

const engine = ActionEngine.Instance;
const result = await engine.RunAction({
    ActionName: 'Run Integration Sync',
    ContextUser: currentUser,
    Params: [
        { Name: 'CompanyIntegrationID', Type: 'Input', Value: 'your-ci-id' },
        { Name: 'TriggerType', Type: 'Input', Value: 'Scheduled' },
    ],
});

Direct Orchestrator Usage

For server-side code that doesn't go through the Actions system:

import { IntegrationOrchestrator } from '@memberjunction/integration-engine';

const orchestrator = new IntegrationOrchestrator();
const result = await orchestrator.RunSync(
    companyIntegrationID,
    contextUser,
    'Manual',
    (progress) => console.log(`${progress.PercentComplete}%`),
    (notification) => console.log(notification.Subject)
);