Email lookup with Clearbit API on New Item in Feed from RSS API

Pipedream makes it easy to connect APIs for Clearbit, RSS and 2,000+ other apps remarkably fast.

Trigger workflow on

New Item in Feed from the RSS API

Next, do this

Email lookup with the Clearbit API

No credit card required

▶

Watch us build a workflow

4 min

Watch now ➜

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

Developers ♥ Pipedream

Getting Started#

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

Select this integration
Configure the New Item in Feed trigger
1. Connect your RSS account
2. Configure timer
3. Configure Feed URL
4. Configure Published After
Configure the Email lookup action
1. Connect your Clearbit account
2. Configure Email
3. Optional- Configure Webhook URL
4. Optional- Configure Given Name
5. Optional- Configure Family Name
6. Optional- Configure IP Address
7. Optional- Configure Location
8. Optional- Configure Company
9. Optional- Configure Company Domain
10. Optional- Configure LinkedIn
11. Optional- Configure Twitter
12. Optional- Configure Facebook
13. Optional- Configure Handle lack of records found as an error?
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 Item in Feed on RSS

Description:Emit new items from an RSS feed

Version:1.2.6

Key:rss-new-item-in-feed

View on GitHub

RSS Overview#

The RSS app allows users to automatically fetch and parse updates from web feeds. This functionality is pivotal for staying abreast of content changes or updates from websites, blogs, and news outlets that offer RSS feeds. With Pipedream, you can harness the RSS API to trigger workflows that enable a broad range of automations, like content aggregation, monitoring for specific keywords, notifications, and data synchronization across platforms.

Trigger Code#

import rss from "../../app/rss.app.mjs";
import { defineSource } from "@pipedream/types";
import rssCommon from "../common/common.mjs";
export default defineSource({
    ...rssCommon,
    key: "rss-new-item-in-feed",
    name: "New Item in Feed",
    description: "Emit new items from an RSS feed",
    version: "1.2.6",
    type: "source",
    dedupe: "unique",
    props: {
        ...rssCommon.props,
        url: {
            propDefinition: [
                rss,
                "url",
            ],
        },
        publishedAfter: {
            type: "string",
            label: "Published After",
            description: "Emit items published after the specified date in ISO 8601 format .e.g `2022-12-07T12:57:10+07:00`",
            default: new Date(Date.now() - 24 * 60 * 60 * 1000).toISOString(), // default to one day ago
        },
    },
    hooks: {
        async activate() {
            // Try to parse the feed one time to confirm we can fetch and parse.
            // The code will throw any errors to the user.
            await this.rss.fetchAndParseFeed(this.url);
        },
    },
    methods: {
        ...rssCommon.methods,
        generateMeta: function (item) {
            return {
                id: this.rss.itemKey(item),
                summary: item.title,
                ts: Date.now(),
            };
        },
    },
    async run() {
        const items = await this.rss.fetchAndParseFeed(this.url);
        for (const item of items.reverse()) {
            const publishedAfter = +new Date(this.publishedAfter);
            const ts = this.rss.itemTs(item);
            if (Number.isNaN(publishedAfter) || publishedAfter > ts) {
                continue;
            }
            const meta = this.generateMeta(item);
            this.$emit(item, 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.

Label	Prop	Type	Description
RSS	`rss`	`app`	This component uses the RSS app.
	`timer`	`$.interface.timer`	How often you want to poll the feed for new items
Feed URL	`url`	`string`	Enter the URL for any public RSS feed
Published After	`publishedAfter`	`string`	Emit items published after the specified date in ISO 8601 format .e.g `2022-12-07T12:57:10+07:00`

Trigger Authentication#

The RSS API does not require authentication.

About RSS#

Real Simple Syndication

Action#

Email lookup on Clearbit

Description:This endpoint retrieves a person by email address. [See the docs here](https://dashboard.clearbit.com/docs#enrichment-api-person-api-email-lookup)

Version:0.4.0

Key:clearbit-email-lookup

View on GitHub

Clearbit Overview#

Clearbit API offers robust data enrichment capabilities, allowing you to seamlessly integrate comprehensive business intelligence into your applications. By leveraging Clearbit, you can append real-time insights to your leads, automate personalized outreach, and gain a deeper understanding of your customers. With insights ranging from company profiles, contact details, to employment information, the possibilities to enhance your marketing, sales, and customer support efforts are vast.

Action Code#

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

export default {
  key: "clearbit-email-lookup",
  name: "Email lookup",
  description: "This endpoint retrieves a person by email address. [See the docs here](https://dashboard.clearbit.com/docs#enrichment-api-person-api-email-lookup)",
  version: "0.4.0",
  type: "action",
  props: {
    app,
    email: {
      propDefinition: [
        app,
        "email",
      ],
    },
    webhookUrl: {
      propDefinition: [
        app,
        "webhookUrl",
      ],
    },
    givenName: {
      label: "Given Name",
      type: "string",
      description: "First name of person.",
      optional: true,
    },
    familyName: {
      label: "Family Name",
      type: "string",
      description: "Last name of person. If you have this, passing this is strongly recommended to improve match rates.",
      optional: true,
    },
    ipAddress: {
      label: "IP Address",
      type: "string",
      description: "IP address of the person. If you have this, passing this is strongly recommended to improve match rates.",
      optional: true,
    },
    location: {
      label: "Location",
      type: "string",
      description: "The city or country where the person resides.",
      optional: true,
    },
    company: {
      label: "Company",
      type: "string",
      description: "The name of the person's employer.",
      optional: true,
    },
    companyDomain: {
      label: "Company Domain",
      type: "string",
      description: "The domain for the person's employer.",
      optional: true,
    },
    linkedin: {
      propDefinition: [
        app,
        "linkedin",
      ],
      description: "The LinkedIn URL for the person.",
    },
    twitter: {
      propDefinition: [
        app,
        "twitter",
      ],
      description: "The Twitter handle for the person.",
    },
    facebook: {
      propDefinition: [
        app,
        "facebook",
      ],
      description: "The Facebook URL for the person.",
    },
    errorIfNoRecords: {
      propDefinition: [
        app,
        "errorIfNoRecords",
      ],
    },
  },
  async run({ $ }) {
    try {
      const res = await this.app.emailLookup($, {
        email: this.email,
        webhook_url: this.webhookUrl,
        given_name: this.givenName,
        family_name: this.familyName,
        ip_address: this.ipAddress,
        location: this.location,
        company: this.company,
        company_domain: this.companyDomain,
        linkedin: this.linkedin,
        twitter: this.twitter,
        facebook: this.facebook,
      });
      $.export("$summary", "Successfully looked up email.");
      return res;
    } catch (err) {
      if (!this.errorIfNoRecords && err.response?.status == 404) {
        $.export("$summary", "No person found.");
      } else {
        throw err;
      }
    }
  },
};

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
Clearbit	`app`	`app`	This component uses the Clearbit app.
Email	`email`	`string`	The email address to look up.
Webhook URL	`webhookUrl`	`string`	A webhook URL that results will be sent to.
Given Name	`givenName`	`string`	First name of person.
Family Name	`familyName`	`string`	Last name of person. If you have this, passing this is strongly recommended to improve match rates.
IP Address	`ipAddress`	`string`	IP address of the person. If you have this, passing this is strongly recommended to improve match rates.
Location	`location`	`string`	The city or country where the person resides.
Company	`company`	`string`	The name of the person's employer.
Company Domain	`companyDomain`	`string`	The domain for the person's employer.
LinkedIn	`linkedin`	`string`	The LinkedIn URL for the person.
Twitter	`twitter`	`string`	The Twitter handle for the person.
Facebook	`facebook`	`string`	The Facebook URL for the person.
Handle lack of records found as an error?	`errorIfNoRecords`	`boolean`	Defaults to `false`. If `false` and no records are found, the step will still be considered a success. If `true` and no records are found, the step will return an error and workflow execution will stop.