Update Row with Supabase API on New or Removed Documents in a Collection from Fauna API

Pipedream makes it easy to connect APIs for Supabase, Fauna and 2,400+ other apps remarkably fast.

Trigger workflow on

New or Removed Documents in a Collection from the Fauna API

Next, do this

Update Row with the Supabase API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

Trusted by 1,000,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

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

Select this integration
Configure the New or Removed Documents in a Collection trigger
1. Configure timer
2. Connect your Fauna account
3. Select a Collection
4. Optional- Configure Emit changes as a single event
Configure the Update Row action
1. Connect your Supabase account
2. Configure Table
3. Configure Column
4. Configure Value
5. Configure Row Data
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Details#

This integration uses pre-built, source-available 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#

New or Removed Documents in a Collection on Fauna

Description:Emit new event each time you add or remove a document from a specific collection, with the details of the document.

Version:0.0.8

Key:faunadb-changes-to-collection

View on GitHub

Fauna Overview#

Fauna API offers a powerful serverless database solution for modern applications. Its unique capabilities allow for highly scalable, secure, and flexible data management. With Pipedream, you can harness the power of Fauna to create intricate serverless workflows that react to various triggers, manage data efficiently, and connect seamlessly with other services and APIs to automate complex tasks.

Trigger Code#

import fauna from "../../faunadb.app.mjs";
import _ from "lodash";
import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform";

export default {
  type: "source",
  key: "faunadb-changes-to-collection",
  name: "New or Removed Documents in a Collection",
  description: "Emit new event each time you add or remove a document from a specific collection, with the details of the document.",
  version: "0.0.8",
  dedupe: "unique", // Dedupe events based on the concatenation of event + document ref id
  props: {
    timer: {
      type: "$.interface.timer",
      default: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
    db: "$.service.db",
    fauna,
    collection: {
      propDefinition: [
        fauna,
        "collections",
      ],
    },
    emitEventsInBatch: {
      type: "boolean",
      label: "Emit changes as a single event",
      description:
        "If `true`, all events are emitted as an array, within a single Pipedream event. Defaults to `false`, emitting each event in Fauna as its own event in Pipedream",
      optional: true,
      default: false,
    },
  },
  async run() {
    // As soon as the script runs, mark the start time so we can fetch changes
    // since this time on the next run. Fauna expects epoch ms as its cursor.
    const ts = +new Date() * 1000;
    const cursor = this.db.get("cursor") || ts;

    const events = await this.fauna.getEventsInCollectionAfterTs(
      this.collection,
      cursor,
    );

    if (!events.length) {
      console.log(`No new events in collection ${this.collection}`);
      this.db.set("cursor", ts);
      return;
    }

    console.log(`${events.length} new events in collection ${this.collection}`);

    // Batched emits do not take advantage of the built-in deduper
    if (this.emitEventsInBatch) {
      this.$emit({
        events,
      }, {
        summary: `${events.length} new event${events.length > 1
          ? "s"
          : ""}`,
        id: cursor,
      });
    } else {
      for (const event of events) {
        this.$emit(event, {
          summary: `${event.action.toUpperCase()} - ${event.document.id}`,
          id: `${event.action}-${event.document.id}`, // dedupes events based on this ID
        });
      }
    }

    // Finally, set cursor for the next run to the max timestamp of the changed events, ensuring we
    // get all events after that on the next run. We need to add 1 since the timestamp filter in
    // Fauna is inclusive: https://docs.fauna.com/fauna/current/api/fql/functions/paginate
    const maxEventTs = _.maxBy(events, (event) => event.ts).ts + 1;

    this.db.set("cursor", maxEventTs);
  },
};

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.

Label	Prop	Type	Description
	`timer`	`$.interface.timer`
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Fauna	`fauna`	`app`	This component uses the Fauna app.
Collection	`collection`	`string`	Select a value from the drop down menu.
Emit changes as a single event	`emitEventsInBatch`	`boolean`	If `true`, all events are emitted as an array, within a single Pipedream event. Defaults to `false`, emitting each event in Fauna as its own event in Pipedream

Trigger Authentication#

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

Create a key in the Security section of your FaunaDB dashboard, then enter the Secret below.

About Fauna#

The distributed serverless database combining the flexibility of NoSQL with the relational querying capabilities of SQL systems.

Action#

Update Row on Supabase

Description:Updates row(s) in a database. [See the docs here](https://supabase.com/docs/reference/javascript/update)

Version:0.1.2

Key:supabase-update-row

View on GitHub

Supabase Overview#

Supabase is a real-time backend-as-a-service that provides developers with a suite of tools to quickly build and scale their applications. It offers database storage, authentication, instant APIs, and real-time subscriptions. With the Supabase API, you can perform CRUD operations on your database, manage users, and listen to database changes in real time. When integrated with Pipedream, you can automate workflows that react to these database events, synchronize data across multiple services, or streamline user management processes.

Action Code#

import supabase from "../../supabase.app.mjs";

export default {
  key: "supabase-update-row",
  name: "Update Row",
  type: "action",
  version: "0.1.2",
  description: "Updates row(s) in a database. [See the docs here](https://supabase.com/docs/reference/javascript/update)",
  props: {
    supabase,
    table: {
      propDefinition: [
        supabase,
        "table",
      ],
      description: "Name of the table to update row(s) in",
    },
    column: {
      propDefinition: [
        supabase,
        "column",
      ],
      description: "Search column to find row(s) to update",
    },
    value: {
      propDefinition: [
        supabase,
        "value",
      ],
      description: "Value of the search column in the row(s) to update",
    },
    data: {
      propDefinition: [
        supabase,
        "data",
      ],
      description: "Enter the column names and values to update as key/value pairs",
    },
  },
  async run({ $ }) {
    const response = await this.supabase.updateRow(this.table, this.column, this.value, this.data);
    $.export("$summary", `Successfully updated ${response.length} row(s) from table ${this.table}`);
    return response;
  },
};

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.

Label	Prop	Type	Description
Supabase	`supabase`	`app`	This component uses the Supabase app.
Table	`table`	`string`	Name of the table to update row(s) in
Column	`column`	`string`	Search column to find row(s) to update
Value	`value`	`string`	Value of the search column in the row(s) to update
Row Data	`data`	`object`	Enter the column names and values to update as key/value pairs

Action Authentication#

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

Supabase provides a Service Key to get started. You can find the service_role in the API Settings page.

Finding the Supabase subdomain

About Supabase#

Supabase is an open source Firebase alternative.

More Ways to Connect Supabase + Fauna#

Other Popular Integrations#

Delete Row with Supabase API on New or Removed Documents in a Collection from Fauna API

Fauna + Supabase

Try it

Insert Row with Supabase API on New or Removed Documents in a Collection from Fauna API

Fauna + Supabase

Try it

Remote Procedure Call with Supabase API on New or Removed Documents in a Collection from Fauna API

Fauna + Supabase

Try it

Select Row with Supabase API on New or Removed Documents in a Collection from Fauna API

Fauna + Supabase

Try it

Upsert Row with Supabase API on New or Removed Documents in a Collection from Fauna API

Fauna + Supabase

Try it

Popular Triggers#

New or Removed Documents in a Collection from the Fauna API

Emit new event each time you add or remove a document from a specific collection, with the details of the document.

Try it

New Row Added from the Supabase API

Emit new event for every new row added in a table. See documentation here

Try it

New Webhook Event (Instant) from the Supabase API

Emit new event for every insert, update, or delete operation in a table. This source requires user configuration using the Supabase website. More information in the README. Also see documentation here

Try it