Create Monitor with UptimeRobot API on New Submission from Typeform API

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

Trigger workflow on

New Submission from the Typeform API

Next, do this

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

Select this integration
Configure the New Submission trigger
1. Connect your Typeform account
2. Select a Form
Configure the Create Monitor action
1. Connect your UptimeRobot account
2. Select a Monitor Type
3. Configure Friendly Name
4. Configure URL, IP Or Host
5. Select a Monitor Interval
6. Select one or more Alert Contacts
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 Submission on Typeform

Description:Emit new submission

Version:0.0.8

Key:typeform-new-submission

View on GitHub

Typeform Overview#

The Typeform API furnishes you with the means to create dynamic forms and collect user responses in real-time. By leveraging this API within Pipedream's serverless platform, you can automate workflows to process this data, integrate seamlessly with other services, and react to form submissions instantaneously. This empowers you to craft tailored responses, synchronize with databases, trigger email campaigns, or even manage event registrations without manual intervention.

Trigger Code#

import { createHmac } from "crypto";
import sampleEmit from "./test-event.mjs";
import { uuid } from "uuidv4";
import common from "../common/common.mjs";
import constants from "../../constants.mjs";
import utils from "../common/utils.mjs";

const { typeform } = common.props;
const { parseIsoDate } = utils;

export default {
  ...common,
  key: "typeform-new-submission",
  name: "New Submission",
  version: "0.0.8",
  type: "source",
  description: "Emit new submission",
  props: {
    ...common.props,
    http: {
      type: "$.interface.http",
      customResponse: true,
    },
    db: "$.service.db",
    formId: {
      propDefinition: [
        typeform,
        "formId",
      ],
    },
  },
  methods: {
    ...common.methods,
    generateSecret() {
      return "" + Math.random();
    },
  },
  hooks: {
    ...common.hooks,
    async activate() {
      const secret = this.generateSecret();
      this._setSecret(secret);

      let tag = this._getTag();
      if (!tag) {
        tag = uuid();
        this._setTag(tag);
      }

      return await this.typeform.createHook({
        endpoint: this.http.endpoint,
        formId: this.formId,
        tag,
        secret,
      });
    },
    async deactivate() {
      const tag = this._getTag();

      return await this.typeform.deleteHook({
        formId: this.formId,
        tag,
      });
    },
  },
  async run(event) {
    const {
      body,
      headers,
    } = event;

    const { [constants.TYPEFORM_SIGNATURE]: typeformSignature } = headers;

    if (typeformSignature) {
      const secret = this._getSecret();

      const hmac =
        createHmac(constants.ALGORITHM, secret)
          .update(body)
          .digest(constants.ENCODING);

      const signature = `${constants.ALGORITHM}=${hmac}`;

      if (typeformSignature !== signature) {
        throw new Error("signature mismatch");
      }
    }

    let formResponseString = "";
    const data = Object.assign({}, body.form_response);
    data.form_response_parsed = {};

    for (let i = 0; i < body.form_response.answers.length; i++) {
      const field = body.form_response.definition.fields[i];
      const answer = body.form_response.answers[i];

      let parsedAnswer;
      let value = answer[answer.type];

      if (value.label) {
        parsedAnswer = value.label;

      } else if (value.labels) {
        parsedAnswer = value.labels.join();

      } else if (value.choice) {
        parsedAnswer = value.choice;

      } else if (value.choices) {
        parsedAnswer = value.choices.join();

      } else {
        parsedAnswer = value;
      }

      data.form_response_parsed[field.title] = parsedAnswer;
      formResponseString += `### ${field.title}\n${parsedAnswer}\n`;
    }

    data.form_response_string = formResponseString;
    data.raw_webhook_event = body;

    if (data.landed_at) {
      data.landed_at = parseIsoDate(data.landed_at);
    }

    if (data.submitted_at) {
      data.submitted_at = parseIsoDate(data.submitted_at);
    }

    data.form_title = body.form_response.definition.title;
    delete data.answers;
    delete data.definition;

    this.$emit(data, {
      summary: JSON.stringify(data),
      id: data.token,
    });

    this.http.respond({
      status: 200,
    });
  },
  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
Typeform	`typeform`	`app`	This component uses the Typeform app.
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.
Form	`formId`	`string`	Select a value from the drop down menu.

Trigger Authentication#

Typeform uses OAuth authentication. When you connect your Typeform account, Pipedream will open a popup window where you can sign into Typeform and grant Pipedream permission to connect to your account. Pipedream securely stores and automatically refreshes the OAuth tokens so you can easily authenticate any Typeform API.

Pipedream requests the following authorization scopes when you connect your account:

offlineaccounts:readforms:writeforms:readimages:writeimages:readthemes:writethemes:readresponses:readresponses:writewebhooks:readwebhooks:writeworkspaces:readworkspaces:write

About Typeform#

Typeform lets you build no-code forms, quizzes, and surveys - and get more responses.

Action#

Create Monitor on UptimeRobot

Description:Create a new monitor. [See the documentation](https://uptimerobot.com/api/).

Version:0.0.1

Key:uptimerobot-create-monitor

View on GitHub

UptimeRobot Overview#

The UptimeRobot API allows you to monitor the uptime of websites and services, sending alerts for any downtime detected. With Pipedream, you can harness this API to create tailored notifications, generate uptime reports, and synchronize with incident management tools. By leveraging Pipedream's capabilities, you can integrate UptimeRobot with a myriad of services to automate responses to uptime changes, streamline communication processes, and maintain a pulse on your web infrastructure's health.

Action Code#

import constants from "../../common/constants.mjs";
import app from "../../uptimerobot.app.mjs";
import utils from "../../common/utils.mjs";

export default {
  key: "uptimerobot-create-monitor",
  name: "Create Monitor",
  description: "Create a new monitor. [See the documentation](https://uptimerobot.com/api/).",
  version: "0.0.1",
  type: "action",
  props: {
    app,
    type: {
      type: "string",
      label: "Monitor Type",
      description: "The type of the monitor.",
      reloadProps: true,
      default: constants.MONITOR_TYPE.PING.value,
      options: Object.values(constants.MONITOR_TYPE),
    },
    friendlyName: {
      description: "A friendly name for the monitor.",
      propDefinition: [
        app,
        "friendlyName",
      ],
    },
    url: {
      type: "string",
      label: "URL, IP Or Host",
      description: "The URL, IP address or Host to monitor.",
    },
    interval: {
      type: "string",
      label: "Monitor Interval",
      description: "The interval for the monitoring check in seconds. It is recommended to use at least 1-minute checks [available in paid plans](https://app.uptimerobot.com/billing/pricing).",
      default: String(5 * 60),
      options: [
        {
          label: "5 Minutes",
          value: String(5 * 60),
        },
        {
          label: "30 Minutes",
          value: String(30 * 60),
        },
        {
          label: "1 Hour",
          value: String(60 * 60),
        },
        {
          label: "12 Hours",
          value: String(12 * 60 * 60),
        },
        {
          label: "1 Day",
          value: String(24 * 60 * 60),
        },
      ],
    },
    alertContacts: {
      type: "string[]",
      label: "Alert Contacts",
      propDefinition: [
        app,
        "alertContact",
      ],
    },
  },
  additionalProps() {
    const {
      type: monitorType,
      subType,
    } = this;

    const timeout = {
      type: "string",
      label: "Request Timeout",
      description: "The request timeout. The shorter the timeout the earlier we mark website as down.",
      default: "30",
      options: [
        {
          label: "1 Second",
          value: "1",
        },
        {
          label: "15 Seconds",
          value: "15",
        },
        {
          label: "30 Seconds",
          value: "30",
        },
        {
          label: "45 Seconds",
          value: "45",
        },
        {
          label: "1 Minute",
          value: "60",
        },
      ],
    };

    const authProps = {
      httpAuthType: {
        type: "string",
        label: "HTTP Auth Type",
        description: "The HTTP auth type for the monitor.",
        optional: true,
        options: [
          {
            label: "HTTP Basic",
            value: "1",
          },
          {
            label: "Digest",
            value: "2",
          },
        ],
      },
      httpUsername: {
        type: "string",
        label: "HTTP Username",
        description: "The HTTP username for the monitor.",
        optional: true,
      },
      httpPassword: {
        type: "string",
        label: "HTTP Password",
        description: "The HTTP password for the monitor.",
        optional: true,
      },
    };

    if (monitorType === constants.MONITOR_TYPE.PORT.value) {
      return {
        timeout,
        subType: {
          type: "string",
          label: "Port Type",
          description: "The type of the port.",
          options: Object.values(constants.PORT_TYPE),
          default: constants.PORT_TYPE.HTTP.value,
          reloadProps: true,
        },
        ...(subType === constants.PORT_TYPE.CUSTOM.value && {
          port: {
            type: "string",
            label: "Port",
            description: "The port number to monitor.",
          },
        }),
      };
    }

    if (monitorType === constants.MONITOR_TYPE.KEYWORD.value) {
      return {
        keywordValue: {
          type: "string",
          label: "Keyword Value",
          description: "The keyword must be present in the response HTML source. You can use HTML markup, too. Eg. `apple` or `<span id=\"availability\">Out of stock</span>`.",
        },
        keywordType: {
          type: "string",
          label: "Keyword Type",
          description: "The keyword type of the monitor.",
          default: "1",
          options: [
            {
              label: "Start incident when keyword exists",
              value: "1",
            },
            {
              label: "Start incident when keyword does not exist",
              value: "2",
            },
          ],
        },
        keywordCaseType: {
          type: "string",
          label: "Keyword Case Type",
          description: "The keyword case type of the monitor.",
          default: "1",
          options: [
            {
              label: "Case Sensitive",
              value: "0",
            },
            {
              label: "Case Insensitive",
              value: "1",
            },
          ],
        },
        ...authProps,
      };
    }

    if (monitorType === constants.MONITOR_TYPE.HTTPS.value) {
      return {
        timeout,
        ...authProps,
      };
    }

    return {};
  },
  methods: {
    formatAlertContacts(alertContacts, useDefaultThresholdAndRecurrence = true) {
      const threshold = 0;
      const recurrence = 0;
      return utils.parseArray(alertContacts)
        ?.map((value) => useDefaultThresholdAndRecurrence
          ? `${value}_${threshold}_${recurrence}`
          : value)
        .join("-");
    },
    createMonitor(args = {}) {
      return this.app.post({
        path: "/newMonitor",
        ...args,
      });
    },
  },
  async run({ $ }) {
    const {
      createMonitor,
      formatAlertContacts,
      type,
      friendlyName,
      url,
      interval,
      alertContacts,
      timeout,
      subType,
      port,
      keywordType,
      keywordValue,
      keywordCaseType,
      httpUsername,
      httpPassword,
      httpAuthType,
    } = this;

    const response = await createMonitor({
      $,
      data: {
        friendly_name: friendlyName,
        url,
        type,
        interval,
        alert_contacts: formatAlertContacts(alertContacts),
        timeout,
        sub_type: subType,
        port,
        keyword_type: keywordType,
        keyword_value: keywordValue,
        keyword_case_type: keywordCaseType,
        http_username: httpUsername,
        http_password: httpPassword,
        http_auth_type: httpAuthType,
      },
    });

    $.export("$summary", `Successfully created monitor with ID \`${response.monitor.id}\`.`);
    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
UptimeRobot	`app`	`app`	This component uses the UptimeRobot app.
Monitor Type	`type`	`string`	Select a value from the drop down menu:`{ "label": "Ping", "value": "3" }{ "label": "Port", "value": "4" }{ "label": "HTTP(s)", "value": "1" }{ "label": "Keyword", "value": "2" }`
Friendly Name	`friendlyName`	`string`	A friendly name for the monitor.
URL, IP Or Host	`url`	`string`	The URL, IP address or Host to monitor.
Monitor Interval	`interval`	`string`	Select a value from the drop down menu:`{ "label": "5 Minutes", "value": "300" }{ "label": "30 Minutes", "value": "1800" }{ "label": "1 Hour", "value": "3600" }{ "label": "12 Hours", "value": "43200" }{ "label": "1 Day", "value": "86400" }`
Alert Contacts	`alertContacts`	`string[]`	Select a value from the drop down menu.

Action Authentication#

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

To retrieve your API keys,