Get Extract Data with FireCrawl API on New Error from ElmahIO API

Pipedream makes it easy to connect APIs for FireCrawl, ElmahIO and 2,700+ other apps remarkably fast.

Trigger workflow on

New Error from the ElmahIO API

Next, do this

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

Select this integration
Configure the New Error trigger
1. Connect your ElmahIO account
2. Configure timer
3. Select a Log ID
4. Configure alert
Configure the Get Extract Data action
1. Connect your FireCrawl account
2. Configure Extract Job ID
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 Error on ElmahIO

Description:Emit new event on each new error. [See the documentation](https://api.elmah.io/swagger/index.html#/Messages/Messages_GetAll)

Version:0.0.4

Key:elmah_io-new-error

View on GitHub

ElmahIO Overview#

The elmah.io API allows developers to automate error logging and management in their applications. By using this API, you can create robust monitoring systems that capture, analyze, and notify you of any application errors in real-time. Integrating elmah.io with Pipedream opens up possibilities for streamlining incident responses, correlating errors with system metrics, and improving application stability through automated workflows. With Pipedream's serverless platform, you can connect elmah.io to numerous other services to enhance your error management processes.

Trigger Code#

import elmah_io from "../../elmah_io.app.mjs";
import constants from "../common/constants.mjs";
import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform";

const QUERY = "severity:Error OR severity:Fatal";

export default {
  name: "New Error",
  version: "0.0.4",
  key: "elmah_io-new-error",
  description: "Emit new event on each new error. [See the documentation](https://api.elmah.io/swagger/index.html#/Messages/Messages_GetAll)",
  type: "source",
  dedupe: "unique",
  props: {
    elmah_io,
    timer: {
      type: "$.interface.timer",
      default: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
    db: "$.service.db",
    logId: {
      propDefinition: [
        elmah_io,
        "logId",
      ],
    },
    alert: {
      type: "alert",
      alertType: "info",
      content: "Note: This source requires that your api key have the `logs_read` and `messages_read` permissions.",
    },
  },
  methods: {
    emitEvent(event) {
      this.$emit(event, {
        id: event.id,
        summary: `New error with ID ${event.id}`,
        ts: Date.parse(event.dateTime),
      });
    },
    _setLastEventDatetime(datetime) {
      this.db.set("lastEventDatetime", datetime);
    },
    _getLastEventDatetime() {
      return this.db.get("lastEventDatetime");
    },
  },
  hooks: {
    async deploy() {
      const messages = await this.elmah_io.getMessages({
        logId: this.logId,
        params: {
          pageSize: 10,
          query: QUERY,
        },
      });

      if (!messages.length) {
        return;
      }

      messages.forEach(this.emitEvent);
      this._setLastEventDatetime(messages[0].dateTime);
    },
  },
  async run() {
    let page = 0;
    const lastEventDatetime = this._getLastEventDatetime();

    while (page >= 0) {
      const messages = await this.elmah_io.getMessages({
        logId: this.logId,
        params: {
          pageIndex: page,
          pageSize: constants.DEFAULT_PAGE_SIZE,
          query: QUERY,
          from: lastEventDatetime
            ? lastEventDatetime
            : undefined,
        },
      });

      if (!messages.length) {
        return;
      }

      messages.forEach(this.emitEvent);
      this._setLastEventDatetime(messages[0].dateTime);

      page++;

      if (messages.length < constants.DEFAULT_PAGE_SIZE) {
        page = -1;
        return;
      }
    }
  },
};

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
ElmahIO	`elmah_io`	`app`	This component uses the ElmahIO app.
	`timer`	`$.interface.timer`
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Log ID	`logId`	`string`	Select a value from the drop down menu.

Trigger Authentication#

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

About ElmahIO#

elmah.io is the easy error logging and uptime monitoring service for .NET. Take back control of your errors with support for all .NET web and logging frameworks.

Action#

Get Extract Data on FireCrawl

Description:Obtains the status and data from a previous extract operation. [See the documentation](https://docs.firecrawl.dev/api-reference/endpoint/extract-get)

Version:0.0.2

Key:firecrawl-get-extract-status

View on GitHub

Action Code#

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

export default {
  key: "firecrawl-get-extract-status",
  name: "Get Extract Data",
  description: "Obtains the status and data from a previous extract operation. [See the documentation](https://docs.firecrawl.dev/api-reference/endpoint/extract-get)",
  version: "0.0.2",
  type: "action",
  props: {
    firecrawl,
    extractId: {
      type: "string",
      label: "Extract Job ID",
      description: "The ID of the extract job",
    },
  },
  async run({ $ }) {
    const response = await this.firecrawl.getExtractStatus({
      $,
      id: this.extractId,
    });

    $.export("$summary", `Successfully retrieved status for extract (ID: ${this.extractId})`);
    return response;
  },
};