← HTTP / Webhook + IFTTT integrations

Trigger Event with Values with IFTTT API on New Requests (Payload Only) from HTTP / Webhook API

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

Trigger workflow on
New Requests (Payload Only) from the HTTP / Webhook API
Next, do this
Trigger Event with Values with the IFTTT 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 IFTTT 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 Trigger Event with Values action
    1. Connect your IFTTT account
    2. Configure Webhook Key
    3. Configure Event Name
    4. Optional- Configure Value 1
    5. Optional- Configure Value 2
    6. Optional- Configure Value 3
  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:Trigger Event with 3 JSON values. [See docs](https://help.ifttt.com/hc/en-us/articles/115010230347-Webhooks-service-FAQ)
Version:0.0.2
Key:ifttt-trigger-event-with-values

IFTTT Overview

With the IFTTT API, you can build a wide variety of applications and
integrations. Here are just a few examples:

  • A to-do list app that adds new items to a spreadsheet
  • A weather app that sends you a notification when it's going to rain
  • A social media app that posts updates to a blog
  • An e-commerce app that track your order status and sends you shipping updates
  • A fitness app that logs your workout data and shares your progress with
    friends

Action Code

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

export default {
  name: "Trigger Event with Values",
  description: "Trigger Event with 3 JSON values. [See docs](https://help.ifttt.com/hc/en-us/articles/115010230347-Webhooks-service-FAQ)",
  key: "ifttt-trigger-event-with-values",
  version: "0.0.2",
  type: "action",
  props: {
    ifttt,
    webhookKey: {
      propDefinition: [
        ifttt,
        "webhookKey",
      ],
    },
    eventName: {
      propDefinition: [
        ifttt,
        "eventName",
      ],
    },
    value1: {
      propDefinition: [
        ifttt,
        "value",
      ],
      label: "Value 1",
    },
    value2: {
      propDefinition: [
        ifttt,
        "value",
      ],
      label: "Value 2",
    },
    value3: {
      propDefinition: [
        ifttt,
        "value",
      ],
      label: "Value 3",
    },
  },
  async run({ $ }) {
    const response = await this.ifttt.callWebhookWithValues({
      $,
      webhookKey: this.webhookKey,
      eventName: this.eventName,
      data: {
        value1: this.value1,
        value2: this.value2,
        value3: this.value3,
      },
    });
    $.export("$summary", `Triggered webhook ${this.eventName}`);
    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
IFTTTiftttappThis component uses the IFTTT app.
Webhook KeywebhookKeystring

The webhook key obtained in Webhook Settings

Event NameeventNamestring

The event name associated with your applet

Value 1value1any

The value to pass to the webhook trigger

Value 2value2any

The value to pass to the webhook trigger

Value 3value3any

The value to pass to the webhook trigger

Action Authentication

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

A request that includes an IFTTT-Service-Key header containing your service key, found in the API tab of the IFTTT Platform under the Service Key heading.

About IFTTT

Every thing works better together

More Ways to Connect IFTTT + HTTP / Webhook

Trigger Event with JSON with IFTTT API on New Requests (Payload Only) from HTTP / Webhook API
HTTP / Webhook + IFTTT
 
Try it
Trigger Event with JSON with IFTTT API on New Requests from HTTP / Webhook API
HTTP / Webhook + IFTTT
 
Try it
Trigger Event with Values with IFTTT API on New Requests from HTTP / Webhook API
HTTP / Webhook + IFTTT
 
Try it
Trigger Event with JSON with IFTTT API on New event when the content of the URL changes. from HTTP / Webhook API
HTTP / Webhook + IFTTT
 
Try it
Trigger Event with Values with IFTTT API on New event when the content of the URL changes. from HTTP / Webhook API
HTTP / Webhook + IFTTT
 
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
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