List Messages with Svix API on New Requests from HTTP / Webhook API

Pipedream makes it easy to connect APIs for Svix, HTTP / Webhook and 2,900+ other apps remarkably fast.

Trigger workflow on

New Requests from the HTTP / Webhook API

Next, do this

List Messages with the Svix API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

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

Developers ♥ Pipedream

Getting Started#

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

Select this integration
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
Configure the List Messages action
1. Connect your Svix account
2. Select a Application ID
3. Optional- Select a Event Type
4. Optional- Configure Limit
5. Optional- Configure Before
6. Optional- Configure After
Deploy the workflow
Send a test event to validate your setup
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#

New Requests on HTTP / Webhook

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

View on GitHub

HTTP / Webhook Overview#

Build, test, and send HTTP requests without code using your Pipedream workflows. The HTTP / Webhook action is a tool to build HTTP requests with a Postman-like graphical interface.

Point and click HTTP requests

Define the target URL, HTTP verb, headers, query parameters, and payload body without writing custom code.

$A screenshot of Pipedream's HTTP Request Configuration interface with a GET request type selected. The request URL is set to 'https://api.openai.com/v1/models'. The 'Auth' tab is highlighted, indicating that authentication is required for this request. In the headers section, there are two headers configured: 'User-Agent' is set to 'pipedream/1', and 'Authorization' is set to 'Bearer {{openai_api_key}}', showing how the OpenAI account's API key is dynamically inserted into the headers to handle authentication automatically.$

Here's an example workflow that uses the HTTP / Webhook action to send an authenticated API request to OpenAI.

Focus on integrating, not authenticating

This action can also use your connected accounts with third-party APIs. Selecting an integrated app will automatically update the request’s headers to authenticate with the app properly, and even inject your token dynamically.

Pipedream integrates with thousands of APIs, but if you can’t find a Pipedream integration simply use Environment Variables in your request headers to authenticate with.

Compatible with no code actions or Node.js and Python

The HTTP/Webhook action exports HTTP response data for use in subsequent workflow steps, enabling easy data transformation, further API calls, database storage, and more.

Response data is available for both coded (Node.js, Python) and no-code steps within your workflow.

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.

Label	Prop	Type	Description
N/A	`httpInterface`	`$.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.
Body Only	`emitBodyOnly`	`boolean`	This source emits an event representing the full HTTP request by default. Select `true` to emit the body only.
Response Status Code	`resStatusCode`	`string`	The status code to return in the HTTP response
Response Content-Type	`resContentType`	`string`	The `Content-Type` of the body returned in the HTTP response
Response Body	`resBody`	`string`	The body to return in the HTTP response
HTTP / Webhook	`http`	`app`	This 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#

List Messages on Svix

Description:List all of the application's messages. [See the docs here](https://api.svix.com/docs#tag/Message/operation/list_messages_api_v1_app__app_id__msg__get)

Version:0.0.2

Key:svix-list-messages

View on GitHub

Svix Overview#

The Svix API enables developers to manage and automate webhooks with ease. By integrating with Pipedream, you can leverage serverless workflows to react to incoming webhooks, manage webhook endpoints, and send out messages to subscribed endpoints. Whether you're seeking to enhance your application's notifications system or streamline event-driven integrations, Svix's API, when combined with Pipedream's capabilities, provides a robust platform for automating and scaling your webhook infrastructure.

Action Code#

import svix from "../../svix.app.mjs";
import { ConfigurationError } from "@pipedream/platform";

export default {
  key: "svix-list-messages",
  name: "List Messages",
  description: "List all of the application's messages. [See the docs here](https://api.svix.com/docs#tag/Message/operation/list_messages_api_v1_app__app_id__msg__get)",
  version: "0.0.2",
  annotations: {
    destructiveHint: false,
    openWorldHint: true,
    readOnlyHint: true,
  },
  type: "action",
  props: {
    svix,
    appId: {
      propDefinition: [
        svix,
        "appId",
      ],
    },
    eventType: {
      propDefinition: [
        svix,
        "eventTypes",
      ],
      type: "string",
      label: "Event Type",
      description: "The event type to retrieve",
      optional: true,
    },
    limit: {
      type: "integer",
      label: "Limit",
      description: "The maximum number of messages to retreive",
      optional: true,
      default: 50,
    },
    before: {
      type: "string",
      label: "Before",
      description: "List only messages before this timestamp. Note: `before` and `after` cannot be used simultaneously.",
      optional: true,
    },
    after: {
      type: "string",
      label: "After",
      description: "List only messages after this timestamp. Note: `before` and `after` cannot be used simultaneously.",
      optional: true,
    },
  },
  async run({ $ }) {
    const {
      appId,
      eventType,
      limit,
      before,
      after,
    } = this;

    if (before && after) {
      throw new ConfigurationError("Only one of `before` or `after` may be used");
    }

    const params = {
      event_types: eventType,
      before,
      after,
    };

    const messages = [];
    while (true) {
      const {
        data, iterator, done,
      } = await this.svix.listMessages(appId, {
        params,
        $,
      });
      messages.push(...data);
      if (done || messages.length >= limit) {
        break;
      }
      params.iterator = iterator;
    }
    if (messages.length > limit) {
      messages.length = limit;
    }

    $.export("$summary", `Found ${messages.length} message(s)`);

    return messages;
  },
};

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.

Label	Prop	Type	Description
Svix	`svix`	`app`	This component uses the Svix app.
Application ID	`appId`	`string`	Select a value from the drop down menu.
Event Type	`eventType`	`string`	Select a value from the drop down menu.
Limit	`limit`	`integer`	The maximum number of messages to retreive
Before	`before`	`string`	List only messages before this timestamp. Note: `before` and `after` cannot be used simultaneously.
After	`after`	`string`	List only messages after this timestamp. Note: `before` and `after` cannot be used simultaneously.

Action Authentication#

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

About Svix#

The enterprise ready webhooks service

More Ways to Connect Svix + HTTP / Webhook#

Other Popular Integrations#

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

HTTP / Webhook + Svix

Try it

Create Message with Svix API on New Requests from HTTP / Webhook API

HTTP / Webhook + Svix

Try it

Delete Message with Svix API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Svix

Try it

Delete Message with Svix API on New Requests from HTTP / Webhook API

HTTP / Webhook + Svix

Try it

List Messages with Svix API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Svix

Try it

Popular Triggers#

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 Event Received (Instant) from the Svix API

Emit new event when an event is received for an application

Try it