← SuperSaaS

New or changed users from SuperSaaS API

Pipedream makes it easy to connect APIs for SuperSaaS and + other apps remarkably fast.

Trigger workflow on
New or changed users from the SuperSaaS API
Next, do this
Connect to 500+ APIs using code and no-code building blocks
No credit card required
Trusted by 200,000+ developers from startups to Fortune 500 companies:
Trusted by 200,000+ developers from startups to Fortune 500 companies

Developers Pipedream

Getting Started

Trigger a workflow on New or changed users with SuperSaaS API. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

  1. Configure the New or changed users trigger
    1. Connect your SuperSaaS account
  2. Add steps to connect to + APIs using code and no-code building blocks
  3. Deploy the workflow
  4. Send a test event to validate your setup
  5. Turn on the trigger


This is a pre-built, open source component from Pipedream's GitHub repo. The component is developed by Pipedream and the community, and verified and maintained by Pipedream.

To contribute an update to an existing component or create a new component, create a PR on GitHub. If you're new to Pipedream component development, you can start with quickstarts for trigger span and action development, and then review the component API reference.

New or changed users on SuperSaaS
Description:Emits an event for every new and changed user.


const dayjs = require('dayjs');
const makeEventSummary = require('../utils/makeEventSummary');
const supersaas = require('../supersaas.app.js');

module.exports = {
  key: 'supersaas-changed-users',
  name: 'New or changed users',
  description: `Emits an event for every new and changed user.`,
  version: '0.0.1',
  props: {
    db: "$.service.db",
    http: '$.interface.http',
  hooks: {
    async activate() {
      const { $auth } = this.supersaas;
      const { http } = this;

      this.db.set('activeHooks', await this.supersaas.createHooks([{
        event: 'M', // change_appointment
        parent_id: $auth.account,
        target_url: http.endpoint,
    async deactivate() {
      await this.supersaas.destroyHooks(this.db.get('activeHooks') || []);
      this.db.set('activeHooks', []);
  async run(ev) {
    const outEv = {
      meta: {
        summary: makeEventSummary(ev),
        ts: dayjs(ev.body.created_on).valueOf(),
      body: ev.body,

    console.log('Emitting:', outEv);
    this.$emit(outEv, outEv.meta);


This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI and CLI.
SuperSaaSsupersaasappThis component uses the SuperSaaS app.
N/Adb$.service.dbThis component uses $.service.db to maintain state between component invocations.
N/Ahttp$.interface.httpThis component uses $.interface.http to generate a unique URL when the component is first instantiated. Each request to the URL will trigger the run() method of the component.


SuperSaaS uses API keys for authentication. When you connect your SuperSaaS account, Pipedream securely stores the keys so you can easily authenticate to SuperSaaS APIs in both code and no-code steps.

You can find your account name and API key in the Account Info section of your settings. See the Authentication docs for more info.

About SuperSaaS

Appointment Scheduling for Every Situation

About Pipedream

Stop writing boilerplate code, struggling with authentication and managing infrastructure. Start connecting APIs with code-level control when you need it — and no code when you don't.

Into to Pipedream
Watch us build a workflow
Watch us build a workflow
4 min
Watch now ➜
"The past few weeks, I truly feel like the clichéd 10x engineer."
Powerful features that scale
Manage concurrency and execution rate
Manage concurrency and execution rate

Queue up to 10,000 events per workfow and manage the concurrency and rate at which workflows are triggered.

Process large payloads up to 5 terabytes
Process large payloads up to 5 terabytes

Large file support enables you to trigger workflows with any data (e.g., large JSON files, images and videos) up to 5 terabytes.

Return custom responses to HTTP requests
Return custom responses to HTTP requests

Return any JSON-serializable response from an HTTP triggered workflow using $respond().

Use most npm packages
Use most npm packages

To use any npm package, just require() it -- there's no npm install or package.json required.

Maintain state between executions
Maintain state between executions

Use $checkpoint to save state in one workflow invocation and read it the next time your workflow runs.

Pass data between steps
Pass data between steps

Return data from any step to inspect it in a human-friendly way and reference the data in future steps via the steps object.