Create Lead with Hyros API on New Stories by Keyword from Hacker News API

Pipedream makes it easy to connect APIs for Hyros, Hacker News and 2,700+ other apps remarkably fast.

Trigger workflow on

New Stories by Keyword from the Hacker News API

Next, do this

Create Lead with the Hyros 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 Hacker News trigger and Hyros action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Stories by Keyword trigger
1. Connect your Hacker News account
2. Configure timer
3. Optional- Configure Keyword
Configure the Create Lead action
1. Connect your Hyros account
2. Optional- Configure Email
3. Optional- Configure First Name
4. Optional- Configure Last Name
5. Optional- Configure Tags
6. Optional- Configure Lead IPs
7. Optional- Configure Phone Numbers
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 Stories by Keyword on Hacker News

Description:Emit new stories that mention a specific keyword

Version:0.0.4

Key:hacker_news-new-stories-by-keyword

View on GitHub

Hacker News Overview#

The Hacker News API on Pipedream allows you to tap into the vibrant pool of stories, comments, and user data from one of tech's favorite forums. By leveraging this API, you can automate the process of extracting data for analysis, tracking mentions of specific topics, or even monitoring the performance of your own submissions. The real power lies in integrating this wealth of information with other services to create custom, automated workflows that save time and keep you informed.

Trigger Code#

const Parser = require("rss-parser");
const hacker_news = require("../../hacker_news.app.js");
const { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } = require("@pipedream/platform");

const parser = new Parser();

module.exports = {
  key: "hacker_news-new-stories-by-keyword",
  name: "New Stories by Keyword",
  description: "Emit new stories that mention a specific keyword",
  version: "0.0.4",
  type: "source",
  props: {
    hacker_news,
    timer: {
      type: "$.interface.timer",
      default: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
    db: "$.service.db",
    // If you want a single search feed but multiple keywords, separate the keywords with " OR ":
    keyword: {
      type: "string",
      label: "Keyword",
      description: "Keyword to watch. Matches story titles. Leave blank to get all stories.",
      optional: true,
      default: "",
    },
  },
  methods: {
    // in theory if alternate setting title and description or aren't unique this won't work
    itemKey(item) {
      return item.guid || item.id || item.title || item.description;
    },
  },
  async run() {
    const seenKeys = this.db.get("seenKeys") || [];
    const seenKeysMap = seenKeys.reduce((acc, v) => {
      acc[v] = true;
      return acc;
    }, {});
    // All elements of an item are optional,
    // however at least one of title or description must be present.
    // should be listed from most recent to least recent
    const feed = await parser.parseURL(`https://hnrss.org/newest?q=${encodeURIComponent(this.keyword)}`);
    for (let idx = feed.items.length - 1; idx >= 0; idx--) {
      const item = feed.items[idx];
      const key = this.itemKey(item);
      // XXX throw if !key?
      if (seenKeysMap[key]) continue;
      seenKeys.unshift(key);
      seenKeysMap[key] = true; // just in case of dupes
      this.$emit(item, {
        id: this.itemKey(item),
        summary: item.title,
        ts: item.pubdate && +new Date(item.pubdate),
      });
    }
    if (seenKeys.length) {
      // XXX restrict by byte size instead of el size
      this.db.set("seenKeys", seenKeys.slice(0, 1000));
    }
  },
};

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
Hacker News	`hacker_news`	`app`	This component uses the Hacker News app.
	`timer`	`$.interface.timer`
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Keyword	`keyword`	`string`	Keyword to watch. Matches story titles. Leave blank to get all stories.

Trigger Authentication#

The Hacker News API does not require authentication.

About Hacker News#

Social news website

Action#

Create Lead on Hyros

Description:Create a new lead. [See the documentation](https://hyros.docs.apiary.io/#reference/0/leads/create-lead)

Version:0.0.1

Key:hyros-create-lead

View on GitHub

Hyros Overview#

The Hyros API offers the ability to track and analyze customer interactions across various marketing channels, aiming to improve ad tracking and ROI. Integrated within Pipedream, it allows for the automation of data collection, real-time analytics, and operational workflows. By leveraging Pipedream's serverless platform, developers can create workflows that respond to events from Hyros, trigger actions based on data insights, or synchronize data with other apps seamlessly.

Action Code#

import { ConfigurationError } from "@pipedream/platform";
import hyros from "../../hyros.app.mjs";

export default {
  key: "hyros-create-lead",
  name: "Create Lead",
  version: "0.0.1",
  description: "Create a new lead. [See the documentation](https://hyros.docs.apiary.io/#reference/0/leads/create-lead)",
  type: "action",
  props: {
    hyros,
    email: {
      propDefinition: [
        hyros,
        "email",
      ],
      optional: true,
    },
    firstName: {
      propDefinition: [
        hyros,
        "firstName",
      ],
      optional: true,
    },
    lastName: {
      propDefinition: [
        hyros,
        "lastName",
      ],
      optional: true,
    },
    tags: {
      type: "string[]",
      label: "Tags",
      description: "A list of tags that will be applied to the lead.",
      optional: true,
    },
    leadIps: {
      propDefinition: [
        hyros,
        "leadIps",
      ],
      optional: true,
    },
    phoneNumbers: {
      propDefinition: [
        hyros,
        "phoneNumbers",
      ],
      optional: true,
    },
  },
  async run({ $ }) {
    const {
      hyros,
      email,
      phoneNumbers,
      ...data
    } = this;

    let response;
    try {
      response = await hyros.createLead({
        $,
        data: {
          email,
          phoneNumbers,
          ...data,
        },
      });
    } catch ({ response }) {
      throw new ConfigurationError(response.data.message[0]);
    }

    $.export("$summary", `A new lead with Id: ${response.request_id} was successfully created!`);
    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
Hyros	`hyros`	`app`	This component uses the Hyros app.
Email	`email`	`string`	Email of the lead that will be created. `If no email is entered, a phone number is required`.
First Name	`firstName`	`string`	First name of the lead.
Last Name	`lastName`	`string`	Last name of the lead.
Tags	`tags`	`string[]`	A list of tags that will be applied to the lead.
Lead IPs	`leadIps`	`string[]`	IPs of the lead that will be created. Will be used to the Ad attributing proccess.
Phone Numbers	`phoneNumbers`	`string[]`	Phone numbers of the lead that will be created. Will be used on the Ad attributing proccess. `If no email is entered, a phone number is required`.