Create Automation Run with Testmo API on New Requests (Payload Only) from HTTP / Webhook API

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

Trigger workflow on

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

Next, do this

Create Automation Run with the Testmo 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 Testmo 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 Create Automation Run action
1. Connect your Testmo account
2. Select a Project Id
3. Configure Name
4. Select a Source
5. Optional- Configure Config
6. Optional- Configure Config Id
7. Optional- Configure Milestone
8. Optional- Select a Milestone Id
9. Optional- Configure Tags
10. Optional- Configure Artifacts
11. Optional- Configure Fields
12. Optional- Configure Links
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#

Create Automation Run on Testmo

Description:Creates a new automation run in a target project in preparation for adding threads and test results. [See the documentation](https://docs.testmo.com/api/reference/automation-runs#post-projects-project_id-automation-runs)

Version:0.0.2

Key:testmo-create-automation-run

View on GitHub

Testmo Overview#

The Testmo API enables automation and integration of your testing workflows into the broader CI/CD pipeline. With Pipedream, you can use this API to trigger tests, update test cases, log results, and sync status with other project management tools. By creating custom serverless workflows on Pipedream, you can connect Testmo to various apps, manage test lifecycles, and respond to events from other services in real-time.

Action Code#

import { parseArray } from "../../common/utils.mjs";
import testmo from "../../testmo.app.mjs";

export default {
  key: "testmo-create-automation-run",
  name: "Create Automation Run",
  version: "0.0.2",
  description: "Creates a new automation run in a target project in preparation for adding threads and test results. [See the documentation](https://docs.testmo.com/api/reference/automation-runs#post-projects-project_id-automation-runs)",
  type: "action",
  props: {
    testmo,
    projectId: {
      propDefinition: [
        testmo,
        "projectId",
      ],
    },
    name: {
      type: "string",
      label: "Name",
      description: "Name of the new automation run.",
    },
    source: {
      propDefinition: [
        testmo,
        "source",
        ({ projectId }) => ({
          projectId,
        }),
      ],
    },
    config: {
      type: "string",
      label: "Config",
      description: "Name of the configuration for the new automation run.",
      optional: true,
    },
    configId: {
      type: "string",
      label: "Config Id",
      description: "ID of the configuration for the new automation run. If both config and `configId` are specified, `configId` is given precedence.",
      optional: true,
    },
    milestone: {
      type: "string",
      label: "Milestone",
      description: "Name of the milestone for the new automation run.",
      optional: true,
    },
    milestoneId: {
      propDefinition: [
        testmo,
        "milestoneId",
        ({ projectId }) => ({
          projectId,
        }),
      ],
      optional: true,
    },
    tags: {
      type: "string[]",
      label: "Tags",
      description: "List of tags for the new automation run. If a milestone in the same project has one or more matching automation tags, the new automation run is automatically linked to that milestone (unless `milestone` or `milestoneId` is also specified).",
      optional: true,
    },
    artifacts: {
      type: "string[]",
      label: "Artifacts",
      description: "List of externally stored test artifacts to link to the new automation run (such as log files, screenshots or test data). [See de documentation for details](https://docs.testmo.com/api/reference/automation-runs#post-projects-project_id-automation-runs)",
      optional: true,
    },
    fields: {
      type: "string[]",
      label: "Fields",
      description: "List of fields to attach to the new automation run (such as environment variables, errors or terminal output). [See de documentation for details](https://docs.testmo.com/api/reference/automation-runs#post-projects-project_id-automation-runs)",
      optional: true,
    },
    links: {
      type: "string[]",
      label: "Links",
      description: "List of links to attach to the new automation run (such as a link back to the build in the CI tool that triggered the tests). [See de documentation for details](https://docs.testmo.com/api/reference/automation-runs#post-projects-project_id-automation-runs)",
      optional: true,
    },
  },
  async run({ $ }) {
    const {
      testmo,
      projectId,
      configId,
      milestoneId,
      artifacts,
      fields,
      links,
      ...data
    } = this;

    const response = await testmo.createAutomationRun({
      $,
      projectId,
      data: {
        config_id: configId,
        milestone_id: milestoneId,
        artifacts: parseArray(artifacts),
        fields: parseArray(fields),
        links: parseArray(links),
        ...data,
      },
    });

    $.export("$summary", `A new automation run with Id: ${response.id} was successfully created!`);
    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.

Label	Prop	Type	Description
Testmo	`testmo`	`app`	This component uses the Testmo app.
Project Id	`projectId`	`string`	Select a value from the drop down menu.
Name	`name`	`string`	Name of the new automation run.
Source	`source`	`string`	Select a value from the drop down menu.
Config	`config`	`string`	Name of the configuration for the new automation run.
Config Id	`configId`	`string`	ID of the configuration for the new automation run. If both config and `configId` are specified, `configId` is given precedence.
Milestone	`milestone`	`string`	Name of the milestone for the new automation run.
Milestone Id	`milestoneId`	`string`	Select a value from the drop down menu.
Tags	`tags`	`string[]`	List of tags for the new automation run. If a milestone in the same project has one or more matching automation tags, the new automation run is automatically linked to that milestone (unless `milestone` or `milestoneId` is also specified).
Artifacts	`artifacts`	`string[]`	List of externally stored test artifacts to link to the new automation run (such as log files, screenshots or test data). See de documentation for details
Fields	`fields`	`string[]`	List of fields to attach to the new automation run (such as environment variables, errors or terminal output). See de documentation for details
Links	`links`	`string[]`	List of links to attach to the new automation run (such as a link back to the build in the CI tool that triggered the tests). See de documentation for details

Action Authentication#

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

To retrieve your API Key,

Navigate to your Testmo account and sign in
Click the dropdown on the top right
Go to “My profile & settings” > “API access”

About Testmo#

The #1 unified test management tool. All your manual, exploratory & automated tests in one powerful platform. Full integration with Jira, GitHub, GitLab & more.

More Ways to Connect Testmo + HTTP / Webhook#

Other Popular Integrations#

Create Automation Run with Testmo API on New Requests from HTTP / Webhook API

HTTP / Webhook + Testmo

Try it

List Automation Runs with Testmo API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Testmo

Try it

List Automation Runs with Testmo API on New Requests from HTTP / Webhook API

HTTP / Webhook + Testmo

Try it

Create Automation Run with Testmo API on New event when the content of the URL changes. from HTTP / Webhook API

HTTP / Webhook + Testmo

Try it

List Automation Runs with Testmo API on New event when the content of the URL changes. from HTTP / Webhook API

HTTP / Webhook + Testmo

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