Trigger a command with TRIGGERcmd API on New Requests (Payload Only) from HTTP / Webhook API

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

Trigger workflow on

New Requests (Payload Only) from the HTTP / Webhook API

Next, do this

Trigger a command with the TRIGGERcmd 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 TRIGGERcmd 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 (Payload Only) trigger
1. Connect your HTTP / Webhook account
Configure the Trigger a command action
1. Connect your TRIGGERcmd account
2. Configure Computer Name
3. Configure Trigger Name
4. Optional- Configure Command parameters
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 (Payload Only) on HTTP / Webhook

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

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
// 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.

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.
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#

Trigger a command on TRIGGERcmd

Description:Runs a command on a computer. Refer to the [TRIGGERcmd Forum](https://triggercmd.com/forum) to learn more.

Version:0.0.1

Key:triggercmd-trigger-command

View on GitHub

TRIGGERcmd Overview#

TRIGGERcmd is a cloud service that allows you to execute commands on your computers remotely through a REST API or via voice command with smart home integrators. With Pipedream's integration capabilities, you can create custom workflows to automate tasks across various apps and services. For instance, you could set up a serverless workflow to trigger scripts on your computer when specific events occur in other apps, such as receiving an email, a new GitHub commit, or a scheduled timer.

Action Code#

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

export default {
  name: "Trigger a command",
  version: "0.0.1",
  key: "triggercmd-trigger-command",
  description: "Runs a command on a computer. Refer to the [TRIGGERcmd Forum](https://triggercmd.com/forum) to learn more.",
  type: "action",
  props: {
    triggercmd,
    computer: {
      type: "string",
      label: "Computer Name",
      description: "The name of the computer",
    },
    trigger: {
      type: "string",
      label: "Trigger Name",
      description: "The name of the command trigger",
    },
    params: {
      type: "string",
      label: "Command parameters",
      description: "Parameters for your command",
      optional: true,
    },
  },
  async run({ $ }) {
    const message = await this.triggercmd.trigger(this.computer, this.trigger, this.params, $);

    $.export("$summary", "Successfully triggered comand");

    return message;
  },

};

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
TRIGGERcmd	`triggercmd`	`app`	This component uses the TRIGGERcmd app.
Computer Name	`computer`	`string`	The name of the computer
Trigger Name	`trigger`	`string`	The name of the command trigger
Command parameters	`params`	`string`	Parameters for your command

Action Authentication#

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

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

About TRIGGERcmd#

TRIGGERcmd is a cloud service that allows you to securely and remotely run commands on your computers. Your commands could install updates, open your garage, run a script, or anything else you decide.

More Ways to Connect TRIGGERcmd + HTTP / Webhook#

Other Popular Integrations#

Trigger a command with TRIGGERcmd API on New Requests from HTTP / Webhook API

HTTP / Webhook + TRIGGERcmd

Try it

Trigger a command with TRIGGERcmd API on New event when the content of the URL changes. from HTTP / Webhook API

HTTP / Webhook + TRIGGERcmd

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