New Response Generated from Chaindesk API

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

Trigger workflow on

New Response Generated from the Chaindesk API

Next, do this

Connect to 2,000+ APIs using code and no-code building blocks

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

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

Developers ♥ Pipedream

Getting Started#

Trigger a workflow on New Response Generated with Chaindesk API. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Configure the New Response Generated trigger
1. Connect your Chaindesk account
2. Configure timer
3. Configure Conversation Id
Add steps to connect to 2,000+ APIs using code and no-code building blocks
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Integrations#

Create Chat Invite Link with Telegram Bot API on New Response Generated from Chaindesk API

Chaindesk + Telegram Bot

Try it

Send Message with Discord Webhook API on New Response Generated from Chaindesk API

Chaindesk + Discord Webhook

Try it

Get Film with SWAPI - Star Wars API on New Response Generated from Chaindesk API

Chaindesk + SWAPI - Star Wars

Try it

Create Multiple Records with Airtable (API Key) API on New Response Generated from Chaindesk API

Chaindesk + Airtable (API Key)

Try it

Send any HTTP Request with HTTP / Webhook API on New Response Generated from Chaindesk API

Chaindesk + HTTP / Webhook

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 Response Generated on Chaindesk

Description:Emit new event when a new message from an agent is created.

Version:0.0.1

Key:chaindesk-new-response-generated

View on GitHub

Code#

import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform";
import chaindesk from "../../chaindesk.app.mjs";

export default {
  key: "chaindesk-new-response-generated",
  name: "New Response Generated",
  description: "Emit new event when a new message from an agent is created.",
  version: "0.0.1",
  type: "source",
  dedupe: "unique",
  props: {
    chaindesk,
    db: "$.service.db",
    timer: {
      type: "$.interface.timer",
      default: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
    conversationId: {
      type: "string",
      label: "Conversation Id",
      description: "The Id of the conversation you want to receive the events.",
    },
  },
  methods: {
    _getLastDatetime() {
      return this.db.get("lastDatetime") || 0;
    },
    _setLastDatetime(lastDatetime = null) {
      this.db.set("lastDatetime", lastDatetime);
    },
    generateMeta({
      id, createdAt,
    }) {
      return {
        id,
        summary: `New message from agent with Id: ${id}`,
        ts: Date.parse(createdAt),
      };
    },
    async startEvent(maxResults) {
      const lastDatetime = this._getLastDatetime();

      let { messages } = await this.chaindesk.listMessages({
        conversationId: this.conversationId,
      });

      messages = messages
        .filter(({ from }) => from === "agent")
        .filter(({ createdAt }) => Date.parse(createdAt) > lastDatetime);
      if (maxResults && (messages.length > maxResults)) messages.length = maxResults;

      if (messages.length) this._setLastDatetime(Date.parse(messages[0].createdAt));

      for (const message of messages.reverse()) {
        this.$emit(message, this.generateMeta(message));
      }
    },
  },
  hooks: {
    async deploy() {
      await this.startEvent(25);
    },
  },
  async run() {
    await this.startEvent();
  },
};

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
Chaindesk	`chaindesk`	`app`	This component uses the Chaindesk app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
	`timer`	`$.interface.timer`
Conversation Id	`conversationId`	`string`	The Id of the conversation you want to receive the events.

Authentication#

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