List Records with Data Stores API on New Activity (Instant) from lemlist API

Pipedream makes it easy to connect APIs for Data Stores, lemlist and 1200+ other apps remarkably fast.

Trigger workflow on

New Activity (Instant) from the lemlist API

Next, do this

List Records with the Data Stores API

No credit card required

▶

Watch us build a workflow

7 min

Watch now ➜

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

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a lemlist 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 Activity (Instant) trigger
1. Connect your lemlist account
2. Optional- Select a Campaign Id
Configure the List Records action
1. Connect your Data Stores account
2. Configure Data Store
3. Select one or more Key
4. Select a Return Type
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 Activity (Instant) on lemlist

Description:Emit new event for each new activity. [See docs here](https://developer.lemlist.com/#add-a-hook)

Version:0.0.1

Key:lemlist-new-activity

View on GitHub

lemlist Overview#

With the lemlist API you can easily create campaigns with personalized emails
and track the results.

Some things you can build with the lemlist API:

A system to personalize emails based on information in a database
A campaign tracking system to see which emails are being opened and clicked
A way to A/B test different email content to see what works best

Trigger Code#

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

export default {
  ...common,
  type: "source",
  name: "New Activity (Instant)",
  key: "lemlist-new-activity",
  description: "Emit new event for each new activity. [See docs here](https://developer.lemlist.com/#add-a-hook)",
  version: "0.0.1",
  dedupe: "unique",
  props: {
    ...common.props,
  },
  methods: {
    ...common.methods,
    getDataToEmit(activity) {
      const ts = new Date().getTime();
      return {
        id: `${activity.type}-${ts}`,
        summary: `New activity ${activity.type} received`,
        ts,
      };
    },
    async loadHistoricalData() {
      const activities = await this.lemlist.getActivities({
        params: {
          campaignId: this.campaignId || null,
          limit: 25,
        },
      });

      return activities.map((activity) => ({
        main: activity,
        sub: this.getDataToEmit(activity),
      }));
    },
    async proccessEvent({ body: activity }) {
      this.$emit(activity,  this.getDataToEmit(activity));
    },
  },
};

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
lemlist	`lemlist`	`app`	This component uses the lemlist app.
Campaign Id	`campaignId`	`string`	Select a value from the drop down menu.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
N/A	`http`	`$.interface.http`	This component uses `$.interface.http` to generate a unique URL when the component is first instantiated. Each request to the URL will trigger the `run()` method of the component.

Trigger Authentication#

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

Get your lemlist API key at the integration page.

About lemlist#

Personalize cold emails, automate follow-ups, and engage with leads across all channels

Action#

List Records on Data Stores

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

Version:0.0.3

Key:data_stores-list-records

View on GitHub

Data Stores Overview#

With the Data Stores API, you can build applications that:

Store data for later retrieval
Retrieve data from a store
Update data in a store
Delete data from a store

Action Code#

/* eslint-disable newline-per-chained-call */
import app from "../../data_stores.app.mjs";
import options from "../../common/options.mjs";

export default {
  key: "data_stores-list-records",
  name: "List Records",
  description: "List all records in your [Pipedream Data Store](https://pipedream.com/data-stores/).",
  version: "0.0.3",
  type: "action",
  props: {
    app,
    dataStore: {
      propDefinition: [
        app,
        "dataStore",
      ],
    },
    keys: {
      propDefinition: [
        app,
        "key",
        ({ dataStore }) => ({
          dataStore,
        }),
      ],
      description: "Select one or multiple keys to retrieve their records.",
      type: "string[]",
    },
    returnType: {
      label: "Return Type",
      description: "Specify the preferred data structure to return.",
      type: "string",
      options: options.LIST_ALL_RECORDS,
      default: "object",
    },
  },
  async run ({ $ }) {
    let keys = await this.dataStore.keys();
    if (this.keys.length > 0) {
      keys = keys.filter((key) => this.keys.includes(key));
    }
    const promises = [];
    for (const key of keys) {
      promises.push(new Promise((resolve, reject) => {
        this.dataStore.get(key).then((value) => {
          resolve({
            key,
            value,
          });
        }).catch((err) => {
          reject(err);
        });
      }));
    }

    const records = await Promise.all(promises);
    if (keys.length > 0) {
      $.export("$summary", `Found ${keys.length} record(s).`);
    } else {
      $.export("$summary", "No record found.");
    }

    switch (this.returnType) {
    case "object": {
      return records.reduce((acc, record) => {
        acc[record.key] = record.value;
        return acc;
      }, {});
    }
    case "array": {
      return records;
    }
    default:
      throw new Error(`Unknown return type: ${this.returnType}`);
    }
  },
};

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
Data Stores	`app`	`app`	This component uses the Data Stores app.
Data Store	`dataStore`	`data_store`	Select an existing Data Store or create a new one.
Key	`keys`	`string[]`	Select a value from the drop down menu.
Return Type	`returnType`	`string`	Select a value from the drop down menu:`{ "label": "Return records as a single object", "value": "object" }`{ "label": "Return records as an array with `key` and `value` properties", "value": "array" }

Action Authentication#

The Data Stores API does not require authentication.

About Data Stores#

Use Pipedream Data Stores to manage state throughout your workflows.

More Ways to Connect Data Stores + lemlist#

Other Popular Integrations#

Delete All Records with Data Stores API on New Activity (Instant) from lemlist API

lemlist + Data Stores

Try it

List keys with Data Stores API on New Activity (Instant) from lemlist API

lemlist + Data Stores

Try it

Add or update multiple records with Data Stores API on New Activity (Instant) from lemlist API

lemlist + Data Stores

Try it

Add or update a single record with Data Stores API on New Activity (Instant) from lemlist API

lemlist + Data Stores

Try it

Delete a single record with Data Stores API on New Activity (Instant) from lemlist API

lemlist + Data Stores

Try it

Popular Triggers#

New Activity (Instant) from the lemlist API

Emit new event for each new activity. See docs here

Try it

New Unsubscribed Recipient (Instant) from the lemlist API

Emit new event when a recipient unsubscribes. See docs here

Try it

Popular Actions#

Add Email In Unsubscribes with the lemlist API

This action adds a lead in the unsubscribed list. See the docs here

Try it

Add Lead To A Campaign with the lemlist API

This action adds a lead in a specific campaign. If the lead doesn't exist, it'll be created, then inserted to the campaign. The creator of the lead is the campaign's sender See the docs here

Try it

Delete An Email From Unsubscribes with the lemlist API

This action deletes a lead in the unsubscribed list. See the docs here

Try it

Delete Lead From Campaign with the lemlist API

This action deletes a lead from a specific campaign. All information, including statistics, will be deleted. See the docs here

Try it

Get Lead with the lemlist API

This action retrieves all the information of a specific lead using its email. See the docs here

Try it