← Telegram Bot + Threads integrations

Delete a Thread with Threads APIon Channel Updates (Instant) from Telegram Bot API

Pipedream makes it easy to connect APIs for Threads, Telegram Bot and + other apps remarkably fast.

Trigger workflow on
Channel Updates (Instant) from the Telegram Bot API
Next, do this
Delete a Thread with the Threads API
No credit card required
Trusted by 200,000+ developers from startups to Fortune 500 companies:
Trusted by 200,000+ developers from startups to Fortune 500 companies

Developers Pipedream

Getting Started

This integration creates a workflow with a Telegram Bot trigger and Threads action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

  1. Select this integration
  2. Configure the Channel Updates (Instant) trigger
    1. Connect your Telegram Bot account
  3. Configure the Delete a Thread action
    1. Connect your Threads account
    2. Configure Thread ID
  4. Deploy the workflow
  5. Send a test event to validate your setup
  6. Turn on the trigger

Details

This integration uses pre-built, open source 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

Description:Emits an event each time a channel message is created or updated.
Version:0.0.1
Key:telegram-channel-updates

Trigger Code

const telegram = require("../../telegram.app.js");

module.exports = {
  key: "telegram-channel-updates",
  name: "Channel Updates (Instant)",
  description: "Emits an event each time a channel message is created or updated.",
  version: "0.0.1",
  dedupe: "unique",
  props: {
    db: "$.service.db",
    http: {
      type: "$.interface.http",
      customResponse: true,
    },
    telegram,
  },
  hooks: {
    async activate() {
      const response = await this.telegram.createHook(this.http.endpoint, ['channel_post', 'edited_channel_post']);
    },
    async deactivate() {
      const response = await this.telegram.deleteHook();
    },
  },
  async run(event) {
    if ((event.path).substring(1) !== this.telegram.$auth.token) {
      return;
    }
    this.http.respond({
      status: 200,
    });
    const { body } = event;
    if (!body) {
      return;
    }
    this.$emit(body, 
      {
        id: body.update_id,
        summary: `${body.channel_post.chat.title} - ${body.channel_post.text}`,
        ts: Date.now()
      }
    );
  },
};

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.
LabelPropTypeDescription
N/Adb$.service.dbThis component uses $.service.db to maintain state between component invocations.
N/Ahttp$.interface.httpThis 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.
Telegram BottelegramappThis component uses the Telegram Bot app.

Trigger Authentication

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

To use the Telegram Bot API, you must first create a new bot by chatting with the BotFather.

At the end of that process, you'll receive a token to authorize requests for your bot. Add that token below.

About Telegram Bot

Telegram is a cloud-based instant messaging and voice over IP service

Action

Description:Delete a thread
Version:0.0.1
Key:threads-delete-thread

Action Code

const threads = require("../../threads.app.js");

module.exports = {
  key: "threads-delete-thread",
  name: "Delete a Thread",
  description: "Delete a thread",
  version: "0.0.1",
  type: "action",
  props: {
    threads,
    threadID: {
      propDefinition: [
        threads,
        "threadID",
      ],
    },
  },
  async run() {
    return await this.threads.deleteThread({
      threadID: this.threadID,
    });
  },
};

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.

LabelPropTypeDescription
ThreadsthreadsappThis component uses the Threads app.
Thread IDthreadIDstring

Navigate to your thread on the Threads website. The URL will be threads.com/${thread_id}

Action Authentication

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

Visit your Integrations settings in your Threads account, and create a new API key in the API Keys section.

About Threads

Threads is a modern forum for work where focused discussions and decisions take place.

About Pipedream

Stop writing boilerplate code, struggling with authentication and managing infrastructure. Start connecting APIs with code-level control when you need it — and no code when you don't.

Into to Pipedream
Watch us build a workflow
Watch us build a workflow
4 min
Watch now ➜
"The past few weeks, I truly feel like the clichéd 10x engineer."
@heyellieday
Powerful features that scale
Manage concurrency and execution rate
Manage concurrency and execution rate

Queue up to 10,000 events per workfow and manage the concurrency and rate at which workflows are triggered.

Process large payloads up to 5 terabytes
Process large payloads up to 5 terabytes

Large file support enables you to trigger workflows with any data (e.g., large JSON files, images and videos) up to 5 terabytes.

Return custom responses to HTTP requests
Return custom responses to HTTP requests

Return any JSON-serializable response from an HTTP triggered workflow using $respond().

Use most npm packages
Use most npm packages

To use any npm package, just require() it -- there's no npm install or package.json required.

Maintain state between executions
Maintain state between executions

Use $checkpoint to save state in one workflow invocation and read it the next time your workflow runs.

Pass data between steps
Pass data between steps

Return data from any step to inspect it in a human-friendly way and reference the data in future steps via the steps object.