← HTTP / Webhook + Twitch integrations

Block User with Twitch API on New Requests from HTTP / Webhook API

Pipedream makes it easy to connect APIs for Twitch, HTTP / Webhook and 1000+ other apps remarkably fast.

Trigger workflow on
New Requests from the HTTP / Webhook API
Next, do this
Block User with the Twitch API
No credit card required
Into to Pipedream
Watch us build a workflow
Watch us build a workflow
7 min
Watch now ➜

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

Adyen logo
Brex logo
Carta logo
Checkr logo
Chameleon logo
DevRev logo
LinkedIn logo
Netflix logo
New Relic logo
OnDeck logo
Replicated logo
Scale AI logo
Teamwork logo
Warner Bros. logo
Xendit logo

Developers Pipedream

Getting Started

This integration creates a workflow with a HTTP / Webhook trigger and Twitch 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 New Requests trigger
    1. Optional- Configure Body Only
    2. Optional- Configure Response Status Code
    3. Optional- Configure Response Content-Type
    4. Optional- Configure Response Body
    5. Connect your HTTP / Webhook account
  3. Configure the Block User action
    1. Connect your Twitch account
    2. Configure User ID
    3. Optional- Select a Source Context
    4. Optional- Select a Reason
  4. Deploy the workflow
  5. Send a test event to validate your setup
  6. 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

Description:Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.
Version:0.1.1
Key:http-new-requests

Trigger Code

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

// Core HTTP component
export default {
  key: "http-new-requests",
  name: "New Requests",
  description: "Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.",
  version: "0.1.1",
  type: "source",
  props: {
    httpInterface: {
      type: "$.interface.http",
      customResponse: true,
    },
    emitBodyOnly: {
      type: "boolean",
      label: "Body Only",
      description: "This source emits an event representing the full HTTP request by default. Select `true` to emit the body only.",
      optional: true,
      default: false,
    },
    resStatusCode: {
      type: "string",
      label: "Response Status Code",
      description: "The status code to return in the HTTP response",
      optional: true,
      default: "200",
    },
    resContentType: {
      type: "string",
      label: "Response Content-Type",
      description: "The `Content-Type` of the body returned in the HTTP response",
      optional: true,
      default: "application/json",
    },
    resBody: {
      type: "string",
      label: "Response Body",
      description: "The body to return in the HTTP response",
      optional: true,
      default: "{ \"success\": true }",
    },
    http,
  },
  async run(event) {
    const summary = `${event.method} ${event.path}`;

    this.httpInterface.respond({
      status: this.resStatusCode,
      body: this.resBody,
      headers: {
        "content-type": this.resContentType,
      },
    });

    if (this.emitBodyOnly) {
      this.$emit(event.body, {
        summary,
      });
    } else {
      this.$emit(event, {
        summary,
      });
    }
  },
};

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/AhttpInterface$.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.
Body OnlyemitBodyOnlyboolean

This source emits an event representing the full HTTP request by default. Select true to emit the body only.

Response Status CoderesStatusCodestring

The status code to return in the HTTP response

Response Content-TyperesContentTypestring

The Content-Type of the body returned in the HTTP response

Response BodyresBodystring

The body to return in the HTTP response

HTTP / WebhookhttpappThis component uses the HTTP / Webhook app.

Trigger Authentication

The HTTP / Webhook API does not require authentication.

About HTTP / Webhook

Get a unique URL where you can send HTTP or webhook requests

Action

Description:Blocks a user; that is, adds a specified target user to your blocks list
Version:0.0.3
Key:twitch-block-user

Twitch Overview

With the Twitch API, you can develop apps that:

  • Display a list of top Twitch channels
  • Allow users to search for specific Twitch channels
  • Show information about a specific Twitch channel
  • Allow users to follow or unfollow a Twitch channel
  • Notify users when their favorite Twitch channels go live

Action Code

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

export default {
  ...common,
  name: "Block User",
  key: "twitch-block-user",
  description: "Blocks a user; that is, adds a specified target user to your blocks list",
  version: "0.0.3",
  type: "action",
  props: {
    ...common.props,
    user: {
      propDefinition: [
        common.props.twitch,
        "user",
      ],
      description: "User ID of the user to be blocked",
    },
    sourceContext: {
      type: "string",
      label: "Source Context",
      description: "Source context for blocking the user. Valid values: \"chat\", \"whisper\".",
      optional: true,
      options: [
        "chat",
        "whisper",
      ],
    },
    reason: {
      type: "string",
      label: "Reason",
      description: "Reason for blocking the user. Valid values: \"spam\", \"harassment\", or \"other\".",
      optional: true,
      options: [
        "spam",
        "harassment",
        "other",
      ],
    },
  },
  async run() {
    const params = {
      target_user_id: this.user,
      source_context: this.sourceContext,
      reason: this.reason,
    };
    const {
      status,
      statusText,
    } = await this.twitch.blockUser(params);
    return status == 204
      ? "User Blocked Successfully"
      : `${status} ${statusText}`;
  },
};

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
TwitchtwitchappThis component uses the Twitch app.
N/Adb$.service.dbThis component uses $.service.db to maintain state between executions.
User IDuserstring

User ID of the user to be blocked

Source ContextsourceContextstringSelect a value from the drop down menu:chatwhisper
ReasonreasonstringSelect a value from the drop down menu:spamharassmentother

Action Authentication

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

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

analytics:read:extensionsanalytics:read:gamesbits:readchannel:read:subscriptionsclips:edituser:edituser:edit:broadcastuser:read:broadcastuser:read:emailuser:read:blocked_usersuser:manage:blocked_userschannel:read:editorschannel:manage:videosuser:read:subscriptions

About Twitch

Live streaming platform for gamers

More Ways to Connect Twitch + HTTP / Webhook

Custom Request with HTTP / Webhook API on New Clips from Twitch API
Twitch + HTTP / Webhook
 
Try it
GET Request with HTTP / Webhook API on New Clips from Twitch API
Twitch + HTTP / Webhook
 
Try it
POST Request with HTTP / Webhook API on New Clips from Twitch API
Twitch + HTTP / Webhook
 
Try it
PUT Request with HTTP / Webhook API on New Clips from Twitch API
Twitch + HTTP / Webhook
 
Try it
Custom Request with HTTP / Webhook API on New Videos from Twitch API
Twitch + HTTP / Webhook
 
Try it
New Requests from the HTTP / Webhook API

Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.

 
Try it
New Requests (Payload Only) from the HTTP / Webhook API

Get a URL and emit the HTTP body as an event on every request

 
Try it
New event when the content of the URL changes. from the HTTP / Webhook API

Emit new event when the content of the URL changes.

 
Try it
New Clip By Streamer from the Twitch API

Emit new event when there is a new clip for the specified streamer.

 
Try it
New Clips from the Twitch API

Emit new event when there is a new clip for the specified game.

 
Try it
Send any HTTP Request with the HTTP / Webhook API

Send an HTTP request using any method and URL. Optionally configure query string parameters, headers, and basic auth.

 
Try it
Send GET Request with the HTTP / Webhook API

Send an HTTP GET request to any URL. Optionally configure query string parameters, headers and basic auth.

 
Try it
Send POST Request with the HTTP / Webhook API

Send an HTTP POST request to any URL. Optionally configure query string parameters, headers and basic auth.

 
Try it
Send PUT Request with the HTTP / Webhook API

Send an HTTP PUT request to any URL. Optionally configure query string parameters, headers and basic auth.

 
Try it
Return HTTP Response with the HTTP / Webhook API

Use with an HTTP Source that uses Return a custom response from your workflow as its HTTP Response

 
Try it