Add Contact To List with Mailmodo API on New Scheduled Tasks from Pipedream API

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

Trigger workflow on

New Scheduled Tasks from the Pipedream API

Next, do this

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

Select this integration
Configure the New Scheduled Tasks trigger
1. Connect your Pipedream account
2. Optional- Configure Secret
Configure the Add Contact To List action
1. Connect your Mailmodo account
2. Select a List
3. Configure Email
4. Optional- Configure Firstname
5. Optional- Configure Lastname
6. Optional- Configure Name
7. Optional- Configure Gender
8. Optional- Configure Age
9. Optional- Configure Phone
10. Optional- Configure Address
11. Optional- Configure Address(more)
12. Optional- Configure City
13. Optional- Configure State
14. Optional- Configure Country
15. Optional- Configure Postal Code
16. Optional- Configure Designation
17. Optional- Configure Company
18. Optional- Configure Industry
19. Optional- Configure Description
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 Scheduled Tasks on Pipedream

Description:Exposes an HTTP API for scheduling messages to be emitted at a future time

Version:0.3.1

Key:pipedream-new-scheduled-tasks

View on GitHub

Pipedream Overview#

Pipedream is an API that allows you to build applications that can connect to
various data sources and processes them in real-time. You can use Pipedream to
create applications that can perform ETL (Extract, Transform, and Load) tasks,
as well as to create data-driven workflows.

Some examples of applications you can build using the Pipedream API include:

An application that can extract data from a database, transform it, and then
load it into another database.
An application that can monitor a data source for changes, and then trigger a
workflow in response to those changes.
An application that can poll an API for new data, and then process that data
in real-time.

Trigger Code#

import pipedream from "../../pipedream.app.mjs";
import sampleEmit from "./test-event.mjs";
import { uuid } from "uuidv4";

export default {
  key: "pipedream-new-scheduled-tasks",
  name: "New Scheduled Tasks",
  type: "source",
  description:
    "Exposes an HTTP API for scheduling messages to be emitted at a future time",
  version: "0.3.1",
  dedupe: "unique", // Dedupe on a UUID generated for every scheduled task
  props: {
    pipedream,
    secret: {
      type: "string",
      secret: true,
      label: "Secret",
      optional: true,
      description:
        "**Optional but recommended**: if you enter a secret here, you must pass this value in the `x-pd-secret` HTTP header when making requests",
    },
    http: {
      label: "Endpoint",
      description: "The endpoint where you'll send task scheduler requests",
      type: "$.interface.http",
      customResponse: true,
    },
    db: "$.service.db",
  },
  methods: {
    // To schedule future emits, we emit to the selfChannel of the component
    selfChannel() {
      return "self";
    },
    // Queue for future emits that haven't yet been delivered
    queuedEventsChannel() {
      return "$in";
    },
    httpRespond({
      status, body,
    }) {
      this.http.respond({
        headers: {
          "content-type": "application/json",
        },
        status,
        body,
      });
    },
    async selfSubscribe() {
      // Subscribe the component to itself. We do this here because even in
      // the activate hook, the component isn't available to take subscriptions.
      // Scheduled tasks are sent to the self channel, which emits the message at
      // the specified delivery_ts to this component.
      const isSubscribedToSelf = this.db.get("isSubscribedToSelf");
      if (!isSubscribedToSelf) {
        const componentId = process.env.PD_COMPONENT;
        const selfChannel = this.selfChannel();
        console.log(`Subscribing to ${selfChannel} channel for event source`);
        console.log(
          await this.pipedream.subscribe(componentId, componentId, selfChannel),
        );
        this.db.set("isSubscribedToSelf", true);
      }
    },
    validateEventBody(event, operation) {
      const errors = [];

      // Secrets are optional, so we first check if the user configured
      // a secret, then check its value against the prop (validation below)
      if (this.secret && event.headers["x-pd-secret"] !== this.secret) {
        errors.push(
          "Secret on incoming request doesn't match the configured secret",
        );
      }

      if (operation === "schedule") {
        const {
          timestamp,
          message,
        } = event.body;
        // timestamp should be an ISO 8601 string. Parse and check for validity below.
        const epoch = Date.parse(timestamp);

        if (!timestamp) {
          errors.push(
            "No timestamp included in payload. Please provide an ISO8601 timestamp in the 'timestamp' field",
          );
        }
        if (timestamp && !epoch) {
          errors.push("Timestamp isn't a valid ISO 8601 string");
        }
        if (!message) {
          errors.push("No message passed in payload");
        }
      }

      return errors;
    },
    scheduleTask(event) {
      const errors = this.validateEventBody(event, "schedule");
      let status, body;

      if (errors.length) {
        console.log(errors);
        status = 400;
        body = {
          errors,
        };
      } else {
        const id = this.emitScheduleEvent(event.body, event.body.timestamp);
        status = 200;
        body = {
          msg: "Successfully scheduled task",
          id,
        };
      }

      this.httpRespond({
        status,
        body,
      });
    },
    emitScheduleEvent(event, timestamp) {
      const selfChannel = this.selfChannel();
      const epoch = Date.parse(timestamp);
      const $id = uuid();

      console.log(`Scheduled event to emit on: ${new Date(epoch)}`);

      this.$emit(
        {
          ...event,
          $channel: selfChannel,
          $id,
        },
        {
          name: selfChannel,
          id: $id,
          delivery_ts: epoch,
        },
      );

      return $id;
    },
    async cancelTask(event) {
      const errors = this.validateEventBody(event, "cancel");
      let status, msg;

      if (errors.length) {
        console.log(errors);
        status = 400;
        msg = "Secret on incoming request doesn't match the configured secret";
      } else {
        try {
          const id = event.body.id;
          const isCanceled = await this.deleteEvent(event);
          if (isCanceled) {
            status = 200;
            msg = `Cancelled scheduled task for event ${id}`;
          } else {
            status = 404;
            msg = `No event with ${id} found`;
          }
        } catch (error) {
          console.log(error);
          status = 500;
          msg = "Failed to schedule task. Please see the logs";
        }
      }

      this.httpRespond({
        status,
        body: {
          msg,
        },
      });
    },
    async deleteEvent(event) {
      const componentId = process.env.PD_COMPONENT;
      const inChannel = this.queuedEventsChannel();

      // The user must pass a scheduled event UUID they'd like to cancel
      // We lookup the event by ID and delete it
      const { id } = event.body;

      // List events in the $in channel - the queue of scheduled events, to be emitted in the future
      const events = await this.pipedream.listEvents(
        componentId,
        inChannel,
      );
      console.log("Events: ", events);

      // Find the event in the list by id
      const eventToCancel = events.data.find((e) => {
        const { metadata } = e;
        return metadata.id === id;
      });

      console.log("Event to cancel: ", eventToCancel);

      if (!eventToCancel) {
        console.log(`No event with ${id} found`);
        return false;
      }

      // Delete the event
      await this.pipedream.deleteEvent(
        componentId,
        eventToCancel.id,
        inChannel,
      );
      return true;
    },
    emitEvent(event, summary) {
      // Delete the channel name and id from the incoming event, which were used only as metadata
      const id = event.$id;
      delete event.$channel;
      delete event.$id;

      this.$emit(event, {
        summary: summary ?? JSON.stringify(event),
        id,
        ts: +new Date(),
      });
    },
  },
  async run(event) {
    await this.selfSubscribe();

    const { path } = event;
    if (path === "/schedule") {
      this.scheduleTask(event);
    } else if (path === "/cancel") {
      await this.cancelTask(event);
    } else if (event.$channel === this.selfChannel()) {
      this.emitEvent(event);
    }
  },
  sampleEmit,
};

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
Pipedream	`pipedream`	`app`	This component uses the Pipedream app.
Secret	`secret`	`string`	Optional but recommended: if you enter a secret here, you must pass this value in the `x-pd-secret` HTTP header when making requests
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.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.

Trigger Authentication#

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

About Pipedream#

Integration platform for developers

Action#

Add Contact To List on Mailmodo

Description:Adds a contact to a list [See the docs here](https://api.salesflare.com/docs#operation/postAccountsAccount_idContacts)

Version:0.0.1

Key:mailmodo-add-contact-to-list

View on GitHub

Mailmodo Overview#

Mailmodo's API turns email marketing into a more powerful tool by allowing you to automate and personalize your email campaigns. Through Pipedream, you can trigger workflows based on events from other apps, update customer data in real time, send transactional emails without leaving your app, and analyze the performance of your campaigns. By leveraging Pipedream's serverless platform, you can integrate Mailmodo with countless apps to enhance your marketing strategies, improve customer engagement, and streamline your communication processes.

Action Code#

import app from "../../mailmodo.app.mjs";
import utils from "../../common/utils.mjs";

export default {
  key: "mailmodo-add-contact-to-list",
  version: "0.0.1",
  type: "action",
  name: "Add Contact To List",
  description: "Adds a contact to a list [See the docs here](https://api.salesflare.com/docs#operation/postAccountsAccount_idContacts)",
  props: {
    app,
    listName: {
      propDefinition: [
        app,
        "listName",
      ],
    },
    email: {
      propDefinition: [
        app,
        "email",
      ],
    },
    firstName: {
      type: "string",
      label: "Firstname",
      description: "Firstname of the contact",
      optional: true,
    },
    lastName: {
      type: "string",
      label: "Lastname",
      description: "Lastname of the contact",
      optional: true,
    },
    name: {
      type: "string",
      label: "Name",
      description: "Name of the contact",
      optional: true,
    },
    gender: {
      type: "string",
      label: "Gender",
      description: "Gender of the contact",
      optional: true,
    },
    age: {
      type: "integer",
      label: "Age",
      description: "Age of the contact",
      optional: true,
    },
    phone: {
      type: "string",
      label: "Phone",
      description: "Phone of the contact",
      optional: true,
    },
    address1: {
      type: "string",
      label: "Address",
      description: "Address",
      optional: true,
    },
    address2: {
      type: "string",
      label: "Address(more)",
      description: "Address(more)",
      optional: true,
    },
    city: {
      type: "string",
      label: "City",
      description: "City",
      optional: true,
    },
    state: {
      type: "string",
      label: "State",
      description: "State",
      optional: true,
    },
    country: {
      type: "string",
      label: "Country",
      description: "Country",
      optional: true,
    },
    postalCode: {
      type: "string",
      label: "Postal Code",
      description: "Postal code",
      optional: true,
    },
    designation: {
      type: "string",
      label: "Designation",
      description: "Designation",
      optional: true,
    },
    company: {
      type: "string",
      label: "Company",
      description: "Company",
      optional: true,
    },
    industry: {
      type: "string",
      label: "Industry",
      description: "Industry",
      optional: true,
    },
    description: {
      type: "string",
      label: "Description",
      description: "Description",
      optional: true,
    },
  },
  async run ({ $ }) {
    const pairs = {
      firstName: "first_name",
      lastName: "last_name",
      postalCode: "postal_code",
    };
    const {
      listName, email, ...data
    } = utils.extractProps(this, pairs);
    const resp = await this.app.addContactToList({
      $,
      data: {
        listName,
        email,
        data,
      },
    });
    $.export("$summary", resp.message);
    return resp;
  },
};

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
Mailmodo	`app`	`app`	This component uses the Mailmodo app.
List	`listName`	`string`	Select a value from the drop down menu.
Email	`email`	`string`	Email of the user
Firstname	`firstName`	`string`	Firstname of the contact
Lastname	`lastName`	`string`	Lastname of the contact
Name	`name`	`string`	Name of the contact
Gender	`gender`	`string`	Gender of the contact
Age	`age`	`integer`	Age of the contact
Phone	`phone`	`string`	Phone of the contact
Address	`address1`	`string`	Address
Address(more)	`address2`	`string`	Address(more)
City	`city`	`string`	City
State	`state`	`string`	State
Country	`country`	`string`	Country
Postal Code	`postalCode`	`string`	Postal code
Designation	`designation`	`string`	Designation
Company	`company`	`string`	Company
Industry	`industry`	`string`	Industry
Description	`description`	`string`	Description

Action Authentication#

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

Navigate to Settings > API Keys, and click Show API Key to view the default API key.

About Mailmodo#

Free Email Marketing Software to create & send email

More Ways to Connect Mailmodo + Pipedream#

Other Popular Integrations#

Trigger Campaign with Mailmodo API on New Scheduled Tasks from Pipedream API

Pipedream + Mailmodo

Add Contact To List with Mailmodo API on New Scheduled Tasks from Pipedream API

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

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

Developers ♥ Pipedream

1-24of2,400+apps by most popular

1
-
24
of
2,400+
apps by most popular