Block Category From Policy with DNSFilter API on New Event Received from Fomo API

Pipedream makes it easy to connect APIs for DNSFilter, Fomo and 2,700+ other apps remarkably fast.

Trigger workflow on

New Event Received from the Fomo API

Next, do this

Block Category From Policy with the DNSFilter 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 Fomo trigger and DNSFilter action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Event Received trigger
1. Connect your Fomo account
2. Configure timer
Configure the Block Category From Policy action
1. Connect your DNSFilter account
2. Select a Policy
3. Select a Category
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 Event Received on Fomo

Description:Emit new event on each new site event received.

Version:0.0.1

Key:fomo-new-event-received

View on GitHub

Fomo Overview#

The Fomo API enables real-time social proof by broadcasting customer interactions, like purchases or sign-ups, to site visitors, fostering a sense of urgency and trust. Leveraging this API on Pipedream, developers can create dynamic, event-driven workflows that respond to these social cues with automated actions like sending emails, updating CRM records, or triggering custom notifications.

Trigger Code#

import fomo from "../../fomo.app.mjs";
import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform";

export default {
  name: "New Event Received",
  version: "0.0.1",
  key: "fomo-new-event-received",
  description: "Emit new event on each new site event received.",
  type: "source",
  dedupe: "unique",
  props: {
    fomo,
    db: "$.service.db",
    timer: {
      type: "$.interface.timer",
      static: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
  },
  methods: {
    emitEvent(data) {
      this.$emit(data, {
        id: data.id,
        summary: `New event received with ID ${data.id}`,
        ts: Date.parse(data.created_at),
      });
    },
    _setLastSyncDate(date) {
      this.db.set("lastSyncDate", date);
    },
    _getLastSyncDate() {
      return this.db.get("lastSyncDate");
    },
  },
  hooks: {
    async deploy() {
      const events = await this.fomo.getEvents({
        params: {
          per_page: 10,
          order_by: "created_at",
          order_direction: "desc",
        },
      });

      events.forEach(this.emitEvent);
    },
  },
  async run() {
    const lastSyncDate = this._getLastSyncDate() ?? (new Date).getTime();
    this._setLastSyncDate((new Date).getTime());

    let page = 1;

    while (true) {
      const events = await this.fomo.getEvents({
        params: {
          page,
          per_page: 100,
          order_by: "created_at",
          order_direction: "desc",
        },
      });

      events
        .filter((event) => Date.parse(event.created_at) > lastSyncDate)
        .forEach(this.emitEvent);

      if (
        events.length < 100 ||
        !events.filter((event) => Date.parse(event.created_at) > lastSyncDate).length
      ) {
        break;
      }

      page++;
    }
  },
};

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
Fomo	`fomo`	`app`	This component uses the Fomo app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
	`timer`	`$.interface.timer`

Trigger Authentication#

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

To retrieve your Fomo API token,
* Navigate to your Fomo account and sign in
* Go to “Sites”
* Select a Site
* Go to “Settings” > “Auth Token”

About Fomo#

Fomo delivers social proof to create website conversion momentum. The Fomo app does this by enabling online experience that feels like a busy store. When a person converts -- whether buying a new jacket, signing up for a retreat, or anything else -- Fomo shows this activity off to other visitors to drive action.

Action#

Block Category From Policy on DNSFilter

Description:Blocks a selected category from a policy applied to your DNSFilter account's sites or roaming clients. [See the documentation](https://app.swaggerhub.com/apis-docs/DNSFilter/dns-filter_api/1.0.15#/Policies/Policies-add_blacklist_category)

Version:0.0.1

Key:dnsfilter-block-category-policy

View on GitHub

DNSFilter Overview#

The DNSFilter API enables you to automate interactions with your DNSFilter account, offering capabilities like managing filtered domains, accessing reports, updating settings, and more. Within Pipedream, you can wield this API for seamless and serverless integrations, crafting workflows that trigger on specified conditions, process DNSFilter data, and interact with other apps and services, all without managing infrastructure.

Action Code#

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

export default {
  key: "dnsfilter-block-category-policy",
  name: "Block Category From Policy",
  description: "Blocks a selected category from a policy applied to your DNSFilter account's sites or roaming clients. [See the documentation](https://app.swaggerhub.com/apis-docs/DNSFilter/dns-filter_api/1.0.15#/Policies/Policies-add_blacklist_category)",
  version: "0.0.1",
  type: "action",
  props: {
    dnsfilter,
    policyId: {
      propDefinition: [
        dnsfilter,
        "policyId",
      ],
    },
    categoryId: {
      propDefinition: [
        dnsfilter,
        "categoryId",
      ],
    },
  },
  async run({ $ }) {
    const response = await this.dnsfilter.blockCategoryFromPolicy({
      policyId: this.policyId,
      data: {
        category_id: this.categoryId,
      },
      $,
    });
    $.export("$summary", `Successfully blocked category ${this.categoryId} from policy ${this.policyId}.`);
    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
DNSFilter	`dnsfilter`	`app`	This component uses the DNSFilter app.
Policy	`policyId`	`string`	Select a value from the drop down menu.
Category	`categoryId`	`string`	Select a value from the drop down menu.

Action Authentication#

DNSFilter uses OAuth authentication. When you connect your DNSFilter account, Pipedream will open a popup window where you can sign into DNSFilter and grant Pipedream permission to connect to your account. Pipedream securely stores and automatically refreshes the OAuth tokens so you can easily authenticate any DNSFilter API.

Pipedream requests the following authorization scopes when you connect your account:

enrollread:authenticatorsremove:authenticatorsoffline_accessopenidpicturenameemail