List Tickets with Trengo API on New Requests from HTTP / Webhook API

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

Trigger workflow on

New Requests from the HTTP / Webhook API

Next, do this

List Tickets with the Trengo 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 Trengo 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 Tickets action
1. Connect your Trengo account
2. Optional- Select a Status
3. Optional- Select one or more User IDs
4. Optional- Select one or more Channel IDs
5. Optional- Select a Last Message Type
6. Optional- Select a Sort Direction
7. Optional- Configure Max Results
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 Tickets on Trengo

Description:List tickets according to the specified criteria. [See the documentation](https://developers.trengo.com/reference/list-all-tickets)

Version:0.0.2

Key:trengo-list-tickets

View on GitHub

Trengo Overview#

The Trengo API provides programmatic access to Trengo's multi-channel communication platform, allowing for the streamlining of customer interactions across various channels such as email, SMS, social media, and chat. By leveraging the Trengo API on Pipedream, you can automate customer support workflows, sync communication data with CRM systems, and trigger alerts or actions based on specific customer queries or events.

Action Code#

import utils from "../../common/utils.mjs";
import app from "../../trengo.app.mjs";

export default {
  key: "trengo-list-tickets",
  name: "List Tickets",
  description: "List tickets according to the specified criteria. [See the documentation](https://developers.trengo.com/reference/list-all-tickets)",
  version: "0.0.2",
  annotations: {
    destructiveHint: false,
    openWorldHint: true,
    readOnlyHint: true,
  },
  type: "action",
  props: {
    app,
    status: {
      type: "string",
      label: "Status",
      description: "The ticket's status",
      optional: true,
      options: [
        "OPEN",
        "ASSIGNED",
        "CLOSED",
        "INVALID",
      ],
    },
    userIds: {
      propDefinition: [
        app,
        "toUserId",
      ],
      type: "integer[]",
      label: "User IDs",
      description: "Filter by one or more user IDs",
      optional: true,
    },
    channelIds: {
      propDefinition: [
        app,
        "channelId",
      ],
      type: "integer[]",
      label: "Channel IDs",
      description: "Filter by one or more channel IDs",
      optional: true,
    },
    lastMessageType: {
      type: "string",
      label: "Last Message Type",
      description: "Filter by the type of the last message",
      optional: true,
      options: [
        "INBOUND",
        "OUTBOUND",
      ],
    },
    sortDirection: {
      type: "string",
      label: "Sort Direction",
      description: "Sort ascending or descending by last message date",
      optional: true,
      options: [
        "ASC",
        "DESC",
      ],
      default: "DESC",
    },
    maxResults: {
      type: "integer",
      label: "Max Results",
      description: "Maximum number of tickets to return (if not specified, all results will be returned)",
      optional: true,
    },
  },
  async run({ $ }) {
    const tickets = [];
    const resourcesStream = utils.getResourcesStream({
      resourceFn: this.app.getTickets,
      resourceFnArgs: {
        params: {
          status: this.status,
          users: this.userIds,
          channels: this.channelIds,
          last_message_type: this.lastMessageType,
          sort: this.sortDirection === "ASC"
            ? "date"
            : "-date",
        },
      },
    });
    for await (const item of resourcesStream) {
      tickets.push(item);
      if (this.maxResults && tickets.length >= this.maxResults) {
        break;
      }
    }
    const length = tickets.length;
    $.export("$summary", `Successfully retrieved ${length} ticket${length === 1
      ? ""
      : "s"}`);
    return tickets;
  },
};

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
Trengo	`app`	`app`	This component uses the Trengo app.
Status	`status`	`string`	Select a value from the drop down menu:`OPENASSIGNEDCLOSEDINVALID`
User IDs	`userIds`	`integer[]`	Select a value from the drop down menu.
Channel IDs	`channelIds`	`integer[]`	Select a value from the drop down menu.
Last Message Type	`lastMessageType`	`string`	Select a value from the drop down menu:`INBOUNDOUTBOUND`
Sort Direction	`sortDirection`	`string`	Select a value from the drop down menu:`ASCDESC`
Max Results	`maxResults`	`integer`	Maximum number of tickets to return (if not specified, all results will be returned)

Action Authentication#

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

You need a personal access token to access the API and to perform actions on your behalf. Your personal access token needs to be send trough an Authorization Bearer request. See docs

About Trengo#

Customer service software

More Ways to Connect Trengo + HTTP / Webhook#

Other Popular Integrations#

Create Contact with Trengo API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Trengo