← SuperSaaS + SWAPI - Star Wars integrations

Get Film with SWAPI - Star Wars APIon New or changed appointments from SuperSaaS API

Pipedream makes it easy to connect APIs for SWAPI - Star Wars, SuperSaaS and + other apps remarkably fast.

Trigger workflow on
New or changed appointments from the SuperSaaS API
Next, do this
Get Film with the SWAPI - Star Wars API
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

This integration creates a workflow with a SuperSaaS trigger and SWAPI - Star Wars action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

  1. Select this integration
  2. Configure the New or changed appointments trigger
    1. Connect your SuperSaaS account
    2. Select one or more Schedules
  3. Configure the Get Film action
    1. Connect your SWAPI - Star Wars account
    2. Select a film
  4. Deploy the workflow
  5. Send a test event to validate your setup
  6. Turn on the trigger

Details

This integration uses pre-built, open source components from Pipedream's GitHub repo. These components are 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.

Trigger

Description:Emits an event for every changed appointments from the selected schedules.
Version:0.0.1
Key:supersaas-changed-appointments

Trigger Code

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

module.exports = {
  key: 'supersaas-changed-appointments',
  name: 'New or changed appointments',
  description: `Emits an event for every changed appointments from the selected schedules.`,
  version: '0.0.1',
  props: {
    supersaas,
    schedules: { propDefinition: [supersaas, 'schedules'] },
    db: "$.service.db",
    http: '$.interface.http',
  },
  hooks: {
    async activate() {
      const { http, schedules } = this;

      this.db.set('activeHooks', await this.supersaas.createHooks(schedules.map(x => ({
        event: 'C', // change_appointment
        parent_id: Number(x),
        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);
  },
};

Trigger Configuration

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.
LabelPropTypeDescription
SuperSaaSsupersaasappThis component uses the SuperSaaS app.
Schedulesschedulesstring[]Select a value from the drop down menu.
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.

Trigger Authentication

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

Action

Description:
Version:0.0.12
Key:swapi-get-film

Action Code

const swapi = require('../../swapi.app.js')
const axios = require('axios')

module.exports = {
  key: "swapi-get-film",
  name: "Get Film",
  version: "0.0.12",
  type: "action",
  props: {
    swapi,
    film: { propDefinition: [swapi, "film"] },
  },
  async run() {
    return (await axios({
      url: `https://swapi.dev/api/films/${this.film}`
    })).data
  },
}

Action Configuration

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI.

LabelPropTypeDescription
SWAPI - Star WarsswapiappThis component uses the SWAPI - Star Wars app.
filmfilmstringSelect a value from the drop down menu.

Action Authentication

The SWAPI - Star Wars API does not require authentication.

About SWAPI - Star Wars

The Star Wars API

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."
@heyellieday
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.