List keys with Data Stores API on New Recurring Lead from Leadfeeder API

Pipedream makes it easy to connect APIs for Data Stores, Leadfeeder and 2,400+ other apps remarkably fast.

Trigger workflow on

New Recurring Lead from the Leadfeeder API

Next, do this

List keys with the Data Stores 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 Leadfeeder trigger and Data Stores action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Recurring Lead trigger
1. Connect your Leadfeeder account
2. Configure Polling schedule
3. Select a Account ID
4. Select a Lead ID
Configure the List keys action
1. Connect your Data Stores account
2. Configure Data Store
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 Recurring Lead on Leadfeeder

Description:Emit new event when a lead is recurred. [See the docs](https://docs.leadfeeder.com/api/#get-all-visits-of-a-lead)

Version:0.0.1

Key:leadfeeder-new-recurring-lead

View on GitHub

Leadfeeder Overview#

Leadfeeder is a tool that reveals the companies visiting your website and how they interact with your content. By harnessing the power of the Leadfeeder API on Pipedream, you can automate the process of capturing lead data and integrating it directly into your sales and marketing workflows. This can range from enriching CRM records to triggering custom email campaigns based on visitor behavior, enabling a more dynamic and responsive engagement with potential customers.

Trigger Code#

import common from "../common/polling.mjs";
import utils from "../../common/utils.mjs";

export default {
  key: "leadfeeder-new-recurring-lead",
  name: "New Recurring Lead",
  description: "Emit new event when a lead is recurred. [See the docs](https://docs.leadfeeder.com/api/#get-all-visits-of-a-lead)",
  type: "source",
  version: "0.0.1",
  dedupe: "unique",
  props: {
    ...common.props,
    leadId: {
      propDefinition: [
        common.props.app,
        "leadId",
        ({ accountId }) => ({
          accountId,
        }),
      ],
    },
  },
  methods: {
    ...common.methods,
    getResourceFn() {
      return this.app.getLeadVisits;
    },
    getResourceFnArgs() {
      const lastVisitDateStr = this.getLastVisitDate();
      const currentDateStr = utils.getFormatDate();
      const threeDaysAgoStr = utils.getFormatDate(3);
      return {
        accountId: this.accountId,
        leadId: this.leadId,
        params: {
          start_date: lastVisitDateStr || threeDaysAgoStr,
          end_date: currentDateStr,
        },
      };
    },
    generateMeta(resource) {
      const ts = Date.parse(resource.attributes.last_visit_date) || Date.now();
      return {
        id: ts,
        ts,
        summary: `New Lead Recurred ${resource.id}`,
      };
    },
  },
};

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
Leadfeeder	`app`	`app`	This component uses the Leadfeeder app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Polling schedule	`timer`	`$.interface.timer`	How often to poll the Leadfeeder API
Account ID	`accountId`	`string`	Select a value from the drop down menu.
Lead ID	`leadId`	`string`	Select a value from the drop down menu.

Trigger Authentication#

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

Leadfeeder API expects an API token to be included in all requests sent to the server.

You can generate your unique authentication token at Leadfeeder API settings.

About Leadfeeder#

Leadfeeder is the #1-rated app for Google Analytics and it's the best way to generate free sales leads.

Action#

List keys on Data Stores

Description:List all keys in your [Pipedream Data Store](https://pipedream.com/data-stores/).

Version:0.0.2

Key:data_stores-list-keys

View on GitHub

Data Stores Overview#

Data Stores are a key-value store that allow you to persist state and share data across workflows. You can perform CRUD operations, enabling dynamic data management within your serverless architecture. Use it to save results from API calls, user inputs, or interim data; then read, update, or enrich this data in subsequent steps or workflows. Data Stores simplify stateful logic and cross-workflow communication, making them ideal for tracking process statuses, aggregating metrics, or serving as a simple configuration store.

Action Code#

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

export default {
  key: "data_stores-list-keys",
  name: "List keys",
  description: "List all keys in your [Pipedream Data Store](https://pipedream.com/data-stores/).",
  version: "0.0.2",
  type: "action",
  props: {
    app,
    dataStore: {
      propDefinition: [
        app,
        "dataStore",
      ],
    },
  },
  async run ({ $ }) {
    const keys = await this.dataStore.keys();
    if (keys.length > 0) {
      $.export("$summary", `Found ${keys.length} key(s).`);
    } else {
      $.export("$summary", "No keys found.");
    }
    return keys;
  },
};