New Lead Status Changed from noCRM.io API

Pipedream makes it easy to connect APIs for noCRM.io and 1200+ other apps remarkably fast.

Trigger workflow on

New Lead Status Changed from the noCRM.io API

Next, do this

Connect to 1200+ APIs using code and no-code building blocks

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#

Trigger a workflow on New Lead Status Changed with noCRM.io API. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Configure the New Lead Status Changed trigger
1. Connect your noCRM.io account
Add steps to connect to 1200+ APIs using code and no-code building blocks
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Integrations#

Send Message with Discord Webhook API on New Lead Status Changed from noCRM.io API

noCRM.io + Discord Webhook

Try it

Add Multiple Rows with Google Sheets API on New Lead Status Changed from noCRM.io API

noCRM.io + Google Sheets

Try it

Get Film with SWAPI - Star Wars API on New Lead Status Changed from noCRM.io API

noCRM.io + SWAPI - Star Wars

Try it

Create Multiple Records with Airtable API on New Lead Status Changed from noCRM.io API

noCRM.io + Airtable

Try it

Chat with OpenAI (ChatGPT) API on New Lead Status Changed from noCRM.io API

noCRM.io + OpenAI (ChatGPT)

Try it

Details#

This is a pre-built, source-available component from Pipedream's GitHub repo. The component is 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.

New Lead Status Changed on noCRM.io

Description:Emit new event when a lead status is changed.

Version:0.0.1

Key:nocrm_io-new-lead-status-changed

View on GitHub

Code#

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

export default {
  ...common,
  name: "New Lead Status Changed",
  version: "0.0.1",
  key: "nocrm_io-new-lead-status-changed",
  description: "Emit new event when a lead status is changed.",
  type: "source",
  methods: {
    ...common.methods,
    getWebhookEventType() {
      return "lead.status.changed";
    },
    emitEvent(body) {
      const data = body?.webhook_event?.data ?? body;

      this.$emit(data, {
        id: `${data.id}-${data.status}-${data.created_at}`,
        summary: `New lead status changed with id ${data.id} and status ${data.status}`,
        ts: Date.parse(data.created_at),
      });
    },
    async deploy() {
      const leads = await this.nocrm_io.getLeads({
        params: {
          limit: 10,
        },
      });

      if (leads) {
        leads.forEach(this.emitEvent);
      }
    },
  },
};

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
noCRM.io	`nocrm_io`	`app`	This component uses the noCRM.io app.
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.

Authentication#

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

Your noCRM.io API key is in your Profile > Admin Panel page, below the API section inside the Integrations card.

If your Nocrm.io URL is https://1234.nocrm.io.com/, your subdomain is 1234.