← HTTP / Webhook + Cisco Webex integrations

Create Message with Cisco Webex API on New Requests (Payload Only) from HTTP / Webhook API

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

Trigger workflow on
New Requests (Payload Only) from the HTTP / Webhook API
Next, do this
Create Message with the Cisco Webex 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 Cisco Webex 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 (Payload Only) trigger
    1. Connect your HTTP / Webhook account
  3. Configure the Create Message action
    1. Connect your Cisco Webex account
    2. Configure Text
    3. Optional- Configure Markdown
    4. Optional- Configure Person ID
    5. Optional- Configure To Person Email
    6. Optional- Select a Room ID
    7. Optional- Select a Parent ID
    8. Optional- Configure File
  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 HTTP body as an event on every request
Version:0.1.1
Key:http-new-requests-payload-only

Trigger Code

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

// Core HTTP component
// Returns a 200 OK response, emits the HTTP payload as an event
export default {
  key: "http-new-requests-payload-only",
  name: "New Requests (Payload Only)",
  // eslint-disable-next-line
  description: "Get a URL and emit the HTTP body as an event on every request",
  version: "0.1.1",
  type: "source",
  props: {
    // eslint-disable-next-line
    httpInterface: {
      type: "$.interface.http",
      customResponse: true,
    },
    http,
  },
  async run(event) {
    const { body } = event;
    this.httpInterface.respond({
      status: 200,
      body,
    });
    // Emit the HTTP payload
    this.$emit({
      body,
    });
  },
};

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.
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:Post a plain text or [rich text](https://developer.webex.com/docs/basics#formatting-messages) message, and optionally, a [file attachment](https://developer.webex.com/docs/basics#message-attachments), to a room. [See the docs here](https://developer.webex.com/docs/api/v1/messages/create-a-message)
Version:0.0.1
Key:cisco_webex-create-message

Cisco Webex Overview

Some things you can build using the Cisco Webex API include:

  • A bot that can perform various tasks such as scheduling meeting, sending
    reminders, and taking minutes
  • An application that can help manage your team's tasks and to-do lists
  • A tool that can help transcribe meeting notes into text format
  • A system that can automatically record and archive your team's Webex meetings

Action Code

import ciscoWebex from "../../cisco_webex.app.mjs";

export default {
  key: "cisco_webex-create-message",
  name: "Create Message",
  description: "Post a plain text or [rich text](https://developer.webex.com/docs/basics#formatting-messages) message, and optionally, a [file attachment](https://developer.webex.com/docs/basics#message-attachments), to a room. [See the docs here](https://developer.webex.com/docs/api/v1/messages/create-a-message)",
  type: "action",
  version: "0.0.1",
  props: {
    ciscoWebex,
    text: {
      type: "string",
      label: "Text",
      description: "The message, in plain text. If markdown is specified this parameter may be optionally used to provide alternate text for UI clients that do not support rich text. The maximum message length is 7439 bytes.",
    },
    markdown: {
      type: "string",
      label: "Markdown",
      description: "The message, in Markdown format. The maximum message length is 7439 bytes.",
      optional: true,
    },
    toPersonId: {
      propDefinition: [
        ciscoWebex,
        "personId",
      ],
      optional: true,
    },
    toPersonEmail: {
      type: "string",
      label: "To Person Email",
      description: "The email address of the recipient when sending a private 1:1 message.",
      optional: true,
    },
    roomId: {
      optional: true,
      propDefinition: [
        ciscoWebex,
        "roomId",
      ],
    },
    parentId: {
      optional: true,
      propDefinition: [
        ciscoWebex,
        "messageId",
        ({ roomId }) => ({
          roomId,
        }),
      ],
    },
    file: {
      type: "string",
      label: "File",
      description: "The public URL to a binary file to be posted into the room. (E.g. `http://www.example.com/images/media.png`)",
      optional: true,
    },
  },
  async run({ $ }) {
    const {
      roomId,
      parentId,
      toPersonId,
      toPersonEmail,
      text,
      markdown,
      file,
    } = this;

    const files = file && [
      file,
    ] || undefined;

    const response =
      await this.ciscoWebex.createMessage({
        data: {
          roomId,
          parentId,
          toPersonId,
          toPersonEmail,
          text,
          markdown,
          files,
        },
      });

    $.export("$summary", `Successfully posted message with ID ${response.id}`);

    return response;
  },
};

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
Cisco WebexciscoWebexappThis component uses the Cisco Webex app.
Texttextstring

The message, in plain text. If markdown is specified this parameter may be optionally used to provide alternate text for UI clients that do not support rich text. The maximum message length is 7439 bytes.

Markdownmarkdownstring

The message, in Markdown format. The maximum message length is 7439 bytes.

Person IDtoPersonIdstring

The person ID of the recipient when sending a private 1:1 message.

To Person EmailtoPersonEmailstring

The email address of the recipient when sending a private 1:1 message.

Room IDroomIdstringSelect a value from the drop down menu.
Parent IDparentIdstringSelect a value from the drop down menu.
Filefilestring

The public URL to a binary file to be posted into the room. (E.g. http://www.example.com/images/media.png)

Action Authentication

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

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

spark:allspark-admin:people_readspark-admin:people_write

About Cisco Webex

Video conferencing, online meetings, screen share, and webinars

More Ways to Connect Cisco Webex + HTTP / Webhook

Custom Request with HTTP / Webhook API on New Message (Instant) from Cisco Webex API
Cisco Webex + HTTP / Webhook
 
Try it
GET Request with HTTP / Webhook API on New Message (Instant) from Cisco Webex API
Cisco Webex + HTTP / Webhook
 
Try it
POST Request with HTTP / Webhook API on New Message (Instant) from Cisco Webex API
Cisco Webex + HTTP / Webhook
 
Try it
PUT Request with HTTP / Webhook API on New Message (Instant) from Cisco Webex API
Cisco Webex + HTTP / Webhook
 
Try it
Return HTTP Response with HTTP / Webhook API on New Message (Instant) from Cisco Webex API
Cisco Webex + 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 Message (Instant) from the Cisco Webex API

Emit new event when a message is added. See the docs here

 
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