Create Requirement with PractiTest API on New Recording from Twilio API

Pipedream makes it easy to connect APIs for PractiTest, Twilio and 2,200+ other apps remarkably fast.

Trigger workflow on

New Recording from the Twilio API

Next, do this

Create Requirement with the PractiTest 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 Twilio trigger and PractiTest action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Recording trigger
1. Connect your Twilio account
2. Configure Polling schedule
Configure the Create Requirement action
1. Connect your PractiTest account
2. Select a Project
3. Configure Name
4. Select a Author
5. Optional- Configure Description
6. Optional- Select a Assigned To
7. Optional- Configure Version
8. Optional- Configure Priority
9. Optional- Configure Custom Fields
10. Optional- Configure Parent ID
11. Optional- Configure Test IDs
12. Optional- Configure Tags
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 Recording on Twilio

Description:Emit new event when a new call recording is created

Version:0.1.5

Key:twilio-new-recording

View on GitHub

Twilio Overview#

Twilio's API on Pipedream opens up a multitude of communication capabilities, allowing you to build robust, scalable, and automated workflows. With Twilio, you can send and receive SMS and MMS messages, make voice calls, and perform other communication functions programmatically. Leveraging Pipedream's seamless integration, you can connect these communications features with hundreds of other services to automate notifications, streamline customer interactions, and enhance operational efficiency.

Trigger Code#

import common from "../common/common-polling.mjs";

export default {
  ...common,
  key: "twilio-new-recording",
  name: "New Recording",
  description: "Emit new event when a new call recording is created",
  version: "0.1.5",
  type: "source",
  dedupe: "unique",
  methods: {
    ...common.methods,
    async listResults(...args) {
      return await this.twilio.listRecordings(...args);
    },
    generateMeta(recording) {
      const {
        sid: id,
        dateCreated,
      } = recording;
      return {
        id,
        summary: `New recording ${id}`,
        ts: Date.parse(dateCreated),
      };
    },
  },
};

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
Twilio	`twilio`	`app`	This component uses the Twilio app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Polling schedule	`timer`	`$.interface.timer`	Pipedream polls Twilio for events on this schedule.

Trigger Authentication#

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

To connect your Twilio account to Pipedream,

API Key and API Key SID

First, create an API key in Twilio.

There are three types of keys: Main, Standard, and Restricted. You'll need a Main key to interact with certain API endpoints, like /Accounts.
If you don't need to interact with those endpoints, you can use a Standard or Restricted key.

After creating your key, you'll see fields for Sid and Secret. Enter those in the fields below.

Account SID and Auth Token

Visit your Twilio Dashboard. You'll see your Account SID and Auth Token under Account info.

About Twilio#

Twilio is a cloud communications platform for building SMS, Voice & Messaging applications on an API built for global scale.

Action#

Create Requirement on PractiTest

Description:Create a requirement [See docs here](https://www.practitest.com/api-v2/#create-a-requirement)

Version:0.0.1

Key:practitest-create-requirement

View on GitHub

PractiTest Overview#

PractiTest is a test management tool that facilitates the organization, tracking, and planning of software testing processes by integrating with Pipedream's automation capabilities. With the PractiTest API, you're able to manipulate test cases, sets, runs, and report on results programmatically. This powerful combination opens the door to automated workflows that enhance testing processes, improve bug tracking, and provide real-time feedback to your team.

Action Code#

import practitest from "../../app/practitest.app.mjs";
import { defineAction } from "@pipedream/types";
import { DOCS } from "../../common/constants.mjs";
export default defineAction({
    name: "Create Requirement",
    description: `Create a requirement [See docs here](${DOCS.createRequirement})`,
    key: "practitest-create-requirement",
    version: "0.0.1",
    type: "action",
    props: {
        practitest,
        projectId: {
            propDefinition: [
                practitest,
                "project",
            ],
        },
        name: {
            type: "string",
            label: "Name",
            description: "Name of the requirement",
        },
        authorId: {
            propDefinition: [
                practitest,
                "user",
            ],
            label: "Author",
        },
        description: {
            type: "string",
            label: "Description",
            description: "Description of the requirement",
            optional: true,
        },
        assignedToId: {
            propDefinition: [
                practitest,
                "user",
            ],
            label: "Assigned To",
            optional: true,
        },
        version: {
            propDefinition: [
                practitest,
                "version",
            ],
            description: "String of the requirement's version",
        },
        priority: {
            type: "string",
            label: "Priority",
            description: "String of the requirement's priority",
            optional: true,
        },
        customFields: {
            propDefinition: [
                practitest,
                "customFields",
            ],
        },
        parentId: {
            type: "string",
            label: "Parent ID",
            description: "A parent's requirement ID",
            optional: true,
        },
        testIds: {
            type: "integer[]",
            label: "Test IDs",
            description: "An array of test-ids to add to the traceability of the new requirement",
            optional: true,
        },
        tags: {
            type: "string[]",
            label: "Tags",
            description: "An array of tags for the requirement",
            optional: true,
        },
    },
    async run({ $ }) {
        const { projectId, name, authorId, description, assignedToId, version, priority, customFields, parentId, testIds, tags, } = this;
        const params = {
            $,
            projectId,
            attributes: {
                name,
                "author-id": authorId,
                description,
                "assigned-to-id": assignedToId,
                version,
                priority,
                "custom-fields": customFields,
                "parent-id": parentId,
                tags,
            },
        };
        if (testIds) {
            params.traceability = {
                "test-ids": testIds,
            };
        }
        const response = await this.practitest.createRequirement(params);
        $.export("$summary", `Successfully created requirement (id ${response.data.id})`);
        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
PractiTest	`practitest`	`app`	This component uses the PractiTest app.
Project	`projectId`	`string`	Select a value from the drop down menu.
Name	`name`	`string`	Name of the requirement
Author	`authorId`	`string`	Select a value from the drop down menu.
Description	`description`	`string`	Description of the requirement
Assigned To	`assignedToId`	`string`	Select a value from the drop down menu.
Version	`version`	`string`	String of the requirement's version
Priority	`priority`	`string`	String of the requirement's priority
Custom Fields	`customFields`	`object`	A hash of custom-fields with their value
Parent ID	`parentId`	`string`	A parent's requirement ID
Test IDs	`testIds`	`integer[]`	An array of test-ids to add to the traceability of the new requirement
Tags	`tags`	`string[]`	An array of tags for the requirement

Action Authentication#

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

PractiTest uses API tokens for authentication. You can create a new API token by going to the Account Settings - “API Tokens”, or going to your personal settings for Personal Tokens. Please visit API tokens for more information.

About PractiTest#

Empower organizations to create, deploy and run software with confidence.

More Ways to Connect PractiTest + Twilio#

Other Popular Integrations#

Create Requirement with PractiTest API on New Call (Instant) from Twilio API

Twilio + PractiTest