← HTTP / Webhook + Trello integrations

Add Attachment to Card via URL with Trello API on New Requests from HTTP / Webhook API

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

Trigger workflow on
New Requests from the HTTP / Webhook API
Next, do this
Add Attachment to Card via URL with the Trello API
No credit card required
Into to Pipedream
Watch us build a workflow
Watch us build a workflow
7 min
Watch now ➜
Trusted by 250,000+ developers from startups to Fortune 500 companies:
Trusted by 250,000+ developers from startups to Fortune 500 companies

Developers Pipedream

Getting Started

This integration creates a workflow with a HTTP / Webhook trigger and Trello 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 Add Attachment to Card via URL action
    1. Connect your Trello account
    2. Select a Board
    3. Select a Card
    4. Optional- Configure Name
    5. Configure File Attachment URL
    6. Optional- Select a File Attachment Type
    7. Configure Set Cover?
  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: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:Adds a file attachment on a card by referencing a public URL. [See the docs here](https://developer.atlassian.com/cloud/trello/rest/api-group-cards/#api-cards-id-attachments-post)
Version:0.0.1
Key:trello-add-attachment-to-card-via-url

Action Code

import common from "../common.js";

export default {
  ...common,
  key: "trello-add-attachment-to-card-via-url",
  name: "Add Attachment to Card via URL",
  description: "Adds a file attachment on a card by referencing a public URL. [See the docs here](https://developer.atlassian.com/cloud/trello/rest/api-group-cards/#api-cards-id-attachments-post)",
  version: "0.0.1",
  type: "action",
  props: {
    ...common.props,
    board: {
      propDefinition: [
        common.props.trello,
        "board",
      ],
    },
    idCard: {
      propDefinition: [
        common.props.trello,
        "cards",
        (c) => ({
          board: c.board,
        }),
      ],
      type: "string",
      label: "Card",
      description: "The ID of the Card to add the Attachment to",
      optional: false,
    },
    name: {
      propDefinition: [
        common.props.trello,
        "name",
      ],
    },
    url: {
      propDefinition: [
        common.props.trello,
        "url",
      ],
    },
    mimeType: {
      propDefinition: [
        common.props.trello,
        "mimeType",
      ],
    },
    setCover: {
      type: "boolean",
      label: "Set Cover?",
      description: "Determines whether to use the new attachment as a cover for the Card",
      default: false,
    },
  },
  async run({ $ }) {
    const {
      idCard,
      name,
      url,
      mimeType,
      setCover,
    } = this;
    const res = await this.trello.addAttachmentToCardViaUrl(idCard, {
      name,
      url,
      mimeType,
      setCover,
    }, $);
    $.export("$summary", `Successfully added attachement to card ${idCard}`);
    return res;
  },
};

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
TrellotrelloappThis component uses the Trello app.
BoardboardstringSelect a value from the drop down menu.
CardidCardstringSelect a value from the drop down menu.
Namenamestring

The name of the attachment

File Attachment URLurlstring

URL must start with http:// or https://

File Attachment TypemimeTypestringSelect a value from the drop down menu.
Set Cover?setCoverboolean

Determines whether to use the new attachment as a cover for the Card

Action Authentication

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

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

readwrite

About Trello

Trello keeps track of everything, from the big picture to the minute details

More Ways to Connect Trello + HTTP / Webhook

Add a Member to a Card with Trello API on New Requests from HTTP / Webhook API
HTTP / Webhook + Trello
 
Try it
Add Attachment to Card via URL with Trello API on New Requests from HTTP / Webhook API
HTTP / Webhook + Trello
 
Try it
Add Existing Label to Card with Trello API on New Requests from HTTP / Webhook API
HTTP / Webhook + Trello
 
Try it
Add Existing Label to Card with Trello API on New Requests from HTTP / Webhook API
HTTP / Webhook + Trello
 
Try it
Archive Card with Trello API on New Requests from HTTP / Webhook API
HTTP / Webhook + Trello
 
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
Card Moved (Instant) from the Trello API

Emit new event each time a card is moved to a list.

 
Try it
New Card (Instant) from the Trello API

Emit new event for each new Trello card on a board.

 
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